It's all in the pause
Working with clients on project management, as I do, I see a familiar theme come up over and over again. People have a difficult time separating the creation of an idea from starting to work on that idea.
Why does this matter? It's the classic vicious cycle for projects: Get an idea. Start doing something about it. Realize you are missing some pieces. Go retrieve the missing elements. Start going again. Get stuck again. Start again. Stop. Start. Stop. Start.
And of course, while you are "stuck," you don't just sit there. You pick up one of those other great ideas and start marching along until it gets stuck. And again. And again.
Before too long, you have ten projects running and none of them are making progress. This applies whether we are talking about personal projects or projects that require coordination amongst many people and organizations.
Try things another way. Step back and put together a plan of attack. Do you know what success looks like for this project? What is the overall sequence of work? (I like to work backwards from the goal of the project.) What might cause the project to get stuck (and can you do anything to prevent that)? Do you have the people, money, resources available to do this?
Once you've thought through elements like this, pause. Decide when you want to activate this project. Maybe it doesn't make sense to start now because of the answers to those questions. Maybe there are just too many other things going on right now and this new project will throw current projects into chaos. If you must start now, consider what current activities should be shelved to create the space for this new one.
[Photo: "Pause - השהיה" by Eran Finkle]
Previous entry: Expert to Novice and back again
Next entry: Epiphanized