Tools for Thought

When we’re undecided on whether or not to commit to a project, one option is to shelve the project on a Someday/Maybe list. But sometimes indecision stems from insufficient information. We need to get enough data to make sure that deciding not to do something is a proactive choice, made from reason or informed intuition, not intellectual laziness.

If you don’t have enough information to commit to a project, make getting the information the project.

You want to start a speech consulting business, but keep putting it off due to a tacit uncertainty that there’s enough of a market for it. Before embarking on a project called “Start a speech consulting business,” the first project that needs to be completed is resolving the uncertainty: “Assess market for speech consulting services.”

Then determine the next action or subproject. An example would be “Set up Google Adwords campaign for multivariate test.” Since this is not something most people have the knowledge to do in one step, it would probably best go on the Project list. Then we need a solid next action to move the project forward — maybe “Read introductory pages on adwords.google.com”.

We’re basically processing an potential project to see if it’s worth doing. It’s a feasibility study. Processing a project is a project in itself — a “look into” or process project.

“R&D” is a common shorthand for process projects on a Project list, as in “R&D: Getting a financial advisor.” You might prefer others:

• Assess
• Look into
• Research
• Determine
• Evaluate
• Compare
• Test
• Draft
• Brainstorm

Notice that the latter two phrases involve getting information from yourself rather than outside resources. Sometimes you just need to know if you know enough to move a project forward. Think twice about reflexively consuming more information instead of thinking proactively. If you draw a blank, the information resources will still be there.

Process projects are not open-ended information buffets. The object is to determine either whether to proceed with the target project, or how to proceed with it. For action we need sufficient information, not complete information.

If the target project is affirmative, put it on the Project list along with any subprojects that might be involved (any multiaction task is referred to technically as a “project,” so subprojects also go on the Project list). If it’s determined that the project is not worth pursuing at this time, but possibly later, put in on the Someday/Maybe list. If it’s determined that it’s not worth doing now or later, dump it out of the system.