You missed one key step "Review" in your workflow process:
Regarding your issues with Projects, I may be able to help. Like yours my mind was once so analytical that I was suffering from analysis paralysis on a regular basis and I was mentally stressed all the time. It took time and effort to retrain my mind to give up that way of thinking (similar to tuning the wires on a piano). You'll likely undergo the same transformation. At first it will not "feel" right but keep doing it for a month; your mind will start to engage differently with these things.
You don't need all of the details all at once in your system. In many cases you may not know how you're going to achieve that outcome at the onset so keep planning to a minimum, observe your progress carefully (review) and make course corrections by defining appropriate next actions as you go.
Once you have defined a project and put it on your Projects list you only need *the* or *a* physical next action that you can take right now to move that project forward. Think of your next actions as bookmarks for your projects.
For those projects that do require a great deal of planning your first action might be to draft a project plan or map or just brainstorm in general. Perhaps you might talk to a friend or someone that you can use as a sounding board and capture all of that. As you review the data that these actions generate you'll be able to decide the next action that will get you closer to the outcome.
More complex projects may have intermediate outcomes well. Make sure you have the primary project identified and listed. Sub-projects don't have to be listed on your projects list (I usually track these in support materials) but there's not any harm in doing so.
Hope some of that helps. Best of luck to you.
Tags for this Thread