Using the MindReader q tag

From ActivityOwnerWiki
Jump to: navigation, search

A key "Getting Things Done" rule is that you should separate your work into five phases:

  1. Collect
  2. Process
  3. Organize
  4. Review
  5. Do

The MindReader q tag disregards that rule and helps you get the 1st three items done automatically in one step.

  • First it leverages GyroQ to let you quickly capture a thought or action item (even if MindManager is not running).
  • Second it helps you pre-process your tasks by automatically recognizing keywords in your text to set attributes of the task. See Using the MindReader m tag for an overview of what it understands and what it does.
  • Third it uses destination keywords to give you the option of sending tasks to specific locations in specific maps rather than having them all pile up in a general "Daily Capture Map". You will still have some more organizing to do for some tasks, but having them in a specific project map or "Area of Focus" map will often make that less overwhelming.

If a task ends up in a different map than you want, you can address that by Using the MindReader s tag.

The Goal

The goal of the MindReader q tag is to use an artificial intelligence approach and to "read your mind" to enable you to quickly enter and mark up a task as it comes to your mind. Users keep entering tasks via the q tag in GyroQ which in turn stores them in a queue. When the user is ready the tasks in the queue are sent through the user's Map Central to become marked up tasks or information on an appropriate map.

Q Tag vs M Tag

Users enter items through the q Tag according to the same set of principles that have been descibed in the Using the MindReader m tag. The m Tag marks up a branch in-situ while the q Tag send the task or information to a queue file. The q tag is the ideal way to enter tasks and information as they come to mind while the m tag can efficiently mark up information and tasks when you want add or change information.


Information sent between [ ] or ( )is processed but text is not included in the resulting task or information branch. For example "q Call Fred about new car [today @office P1]".


Users can reduce typing by creating Aliases in the MindReaderconfig.mmap. For example, "iadmin" could be defined as [isinfo administration] and administration could be defined in "links" to point to the administration.mmap. This would result in the information being placed as a branch on the Administration map.It would not contain a blob and therefore would not be considered a task.

Entering a Series of Tasks

You can use >> or << to enter a series of tasks in one step. See the Begin with the end in mind blog post for background].