The Definition Vortex

Defining a problem is important; I don't deny it. If you haven't framed the problem you have no chance to solve it.

And yet, I've seen so many people hide behind the camouflage of defining a problem. "Let's have a meeting and define the problem" turns into weeks of discussion and debate. In the meantime, the problem is getting worse, having children, planting roots -- pick your metaphor -- and we're still talking about how to talk about it.

Long ago a boss told me that if a meeting was rescheduled more than 3 times, it probably was a meeting that didn't need to happen. I propose a corollary:

It the topic of "defining a problem" requires more than 2 meetings, it's very likely you have bitten off too much to chew.

Break it down, pick a part of you CAN define and begin to work to solution. If you are creating flowcharts and Gantt charts that start with the big bang, it might be time to re-frame and simplify.

A wise woman recently told me: "If two things are a mystery, choose one." This is great advice, and this direction could kick many project teams out of the "definition vortex"!