Hello, This post is sort of related to Michaels, yet not an explicit attempt to solve the puzzle. Tthe last week or so I have been doing some new-code games for a brief period every day. This was prompted by Carmens hint that fifteen minutes a day may lead to an automatization of the process. That would be nice :-) Anyway, for me I learned how to do new code games the first time more than a decade ago. In Oslo and in Santa Cruz. The process as I remember it was presented slightly different then than in whispering. I used the new code games for a number of personal changes. In more recent years however my success with the games have been variable. However - yesterday I changed one variable; speed! I did the alphabet chart game much faster than previously. In fact I accelerated up to the point where it was going so fast I was making mistakes - then of course I slowed down just slightly, and started over in order to get it right. This produced the familiar and almost forgotten buzz of a high-performance state - and interestingly I just knew at the moment I felt that buzz that this was the state I had been hunting for. As I brought that state with me to the problem context it was also very obvious that things were different. That I was approaching the problems in that context with A LOT more resources than previously, and many small problems and parts of larger problems just went >poof<, bye bye. However I still found myself forgetting what I was doing several times. - As I was standing in my problem-context-circle on the floor I realized that oops, I have been standing here musing without that high-quality state for minutes now! This of course is due to playing the game without coach - and yet learning how to coach myself while doing it. I am very curious about ways others have found helpful to insure reaching a high-performance state while playing new code games, as well as tricks for self monitoring (lika Michaels in the post before this one). All the best Thomas