Quote Originally Posted by furashgf
I've got no trouble whacking out the outcome/vision thing, but:
1. I never get to the brainstorming/organize part - . . .
2. It takes forever to do it (I can spend up to 1/2 hour or an hour, coming through materials, etc., fiddling with the outline).
3. I end up with something very "fragile" - constantly needs revisiting.
Others have given you better responses than I can, but I'll throw out my impression from your complaint: I wonder whether you have adequately defined and clarified the project's outcome and purpose (see CosmoGTD post for more). I find that my projects that stall out are usually imbued with a squishy or fuzzy quality. Invariably, when I ramp up the focus and demand from myself a succinct explanation of why I'm doing the thing and what I want from having done it, I find conflicts. On the surface, it may seem eminently worthy, so I have to explore the causes for my reticence. Sometimes it turns out that the justification for the project is there and its outcome well defined, but I really don't want to do it. I may want it done, but I may not want to be the person who does it. Sometimes I discover that I believe that doing the project will ultimately lead to negative consequences of some sort, and I haven't adequately explored or come to terms with those risks. Sometimes I find that, while I am personally assured of the project's merit, underneath it all I am not confident that it has the support and backing of others who will be involved in it. I'm often loathe to confront that reality and see what the others feel because I'm so sold on the project myself. Ego, ack! Sometimes I realize I haven't properly scoped out the costs of the project, in time and funds and other resources, and am hesitating because instinct tells me that ultimately, it's not going to be feasible. There are plenty of other dynamics that can stymie a project, but those are the biggies in my world.

I believe that if you are on track and other things are working well, stalling or hesitation in moving a project forward is an indicator that work needs to be done on the justification for the project itself. I've found that when I finally get down to brass tacks and pinpoint the problem and resolve it, the ambiguities and conflicts evaporate and it's clear sailing. Until the next block.

Which brings me to another point. Complex projects that involve major resources and require work over a long period of time are the most subject to changes in direction and circumstance, and their logical underpinnings may need review and reevaluation throughout the execution of the project. Momentum is wonderful when you need it, but it can be a monster when you'd be best served by abandoning or redirecting an ongoing effort.

Lastly, 30 minutes doesn't seem excessive for this kind of work. Half an hour spent focusing on the real issues can save you goodwill and funds, not to mention days, weeks, or more in time and labor. The positive effect of true clarity of purpose can generate enormous energy to accomplish the work itself. Or, as I think of it, out of ferklempt comes butter.

Arduinna