http://www.activityowner.com/2009/02/07/mindreader-20/

http://www.activityowner.com/2008/03/27/gtd-and-mindreader-qa/

for some ideas.

We're told that if something will take more than say, two minutes, stick it in the system. I assume this leads to documenting every step that will take more than two minutes? But it can't, or we would document going to the grocery store as 200 steps, obviously making the process more laborious than is beneficial. So how do you know how to break projects down? Is it entirely arbitrary? The system is very keen on next steps, but what about all of the 'other' steps? So, I'm going to build a house myself, and the Next Step is to draw blueprints. But I know that to draw blueprints I need to buy big paper, and when I have them I'll need to go to the copy store and make copies, and I'll need to look in the yellow pages for contractors, and I'll need to make a list of contractors to call, and I'll need to call each one, and, and, and… By breaking this into discrete components (especially if I'm going to take the time to enter them into an electronic system), I would seem to exponentially increase the time it will take to get the project actually done. Maybe I'm missing the bigger picture, and I admit, I'm on the very outside edge crawling towards the center of all of this…

Next question: Just want to make sure I understand something about the technology. I understand that MindReader requires MindManager/MindJet and Gyroq, but does it REQUIRE ResultsManager? (I have all of these tools, just trying to wrap my head around what does what). If I understand correctly, RM is really just a reporting tool (maybe an important one, but still a reporting tool). Is this correct?

Thanks in advance for any advice and comments!

A few versions ago I added some code to detect and remove duplicate entries in MindReader.mmap as people sometimes put in the same item twice by mistake and it can cause some funny mark-up.

Of course, because I don't use the mindreader.mmap starter template map, I didn't think to run the code on it and discover that..whoops.. it had the two duplicates you found from the get go!

I just uploaded a cleaned up copy in ao-pack. You should be fine with your as the code has fixed the problem.

I would have thought this was a result of reinstalling or merging, but I deleted my mindreader.mmap file before reinstalling.

Don't know if this is a one-time thing, a non-issue, a bug… just wanted to let you know!

-Ed

The "I owe" task lives on is a project map with a central topic that is either implicitly or explicitly owned by you as the project manager. All tasks underneath are "owed to you". The "I owe" task has the other person's name first, so ResultsManager sees that person as responsible/accountable for completing the task for you, even though they have delegated it to another person. That other person just happens to be you.

They way to avoid this is to create a project branch or dedicated project map that is owned by "somebody else" and placed "I owe" tasks underneath that.

Note that "io" is one of the default Gyronix GyroQ tags rather than a MindReader tag.

I installed your ao pack last week and now have odd io behavior. When I use the i owe tag in mindreader it puts the persons name first and then my name second in the owner's field. After I export the queue, when I run results manager, I end up with a waiting for (other person) and an i owe (other person) entry in the relationship central. The automatic delegation flag is checked in results manager dashboard settings. I am new enough to these products that I'm not sure exactly what to do, but this behavior is confusing to me.

-Ed