I think the appeal of MindReader is that, for heavy users of the system, it lowers the activation energy/time needed to add clarity to a task by just couple of seconds and (for better or worse) thats just enough to encourage quite a bit more user input.

Ironically the actual time it takes is roughly the same as for alt-e-y method, but the time delay comes after the use has have done their part and shifted your focus elsewhere where as the alt-e-y lag comes before.

Thanks for this honest post. The feedback is valuable as I am sure there are others that have a slightly limping ResultsManager and would like to transform it into a champion racehorse. I use MindReader and other AO resources every day and so understand their value. Thanks for this great resource you are all creating and contributing to.

Please also send feedback and improvement suggestions to Gyronix direct, especially those using it in a team environment as we would love for everyone to have their own champion racehorse.

Kind regards,

Nik

Nik Tipler
Chief Rhino & CEO
Gyronix

I agree that AO's MindReader is exactly the cohesive bond that was needed to bring MindManager, ResultsManager, & GyroQ together. Before GyroQ, the ResultsManagers Project Template helped somewhat but there was still the constant need to interrupt my thought process (or what remains of it) to add tasks into my maps. GyroQ solved the interrupt issue but I now had a new daily task of 'Capture Map has been processed into appropriate project maps'. Now, with MindReader I am doing exactly what GTD professes - I'm getting things done.

AO,
This is a thank you for all your time spent in coding, listening to my ideas & random thoughts, & making your blog one of the few I eagerly wait for the next posting.