One Simple Question That Keeps Projects from Going off the Rails
It’s unusual for projects to come in on target, on time, and on budget. Ask one simple question that gets teams solving problems before they happen.
12 reasons good projects go bad:
- Unrealistic planning.
- Poorly defined goals and milestones.
- Disorganized leaders.
- Lack of motivation.
- Frantic schedules.
- Communication breakdowns. Misunderstanding slows progress. Crossed wires create conflict.
- Ineffective resource allocation.
- Failure to adapt to evolving market demands that change project requirements.
- Software bugs.
- Hardware failures.
- Economic upheaval.
- Legal issues.
One simple question that keeps projects on track:
“Imagine this project is over and it’s a catastrophic failure. What did we fail to do that contributed to the failure?”
Before you mess with the language of this question, consider why it’s worded this way.
Set the stage:
Get teams in problem-solving mode by asking about imagined failure. It’s normal to worry about projects. It means you care. Tap into problem-solving power before problems happen.
Declare intent so you won’t give offense.
Team members might take offense when you say, “Imagine this project is a catastrophic failure.” They could think you don’t trust them. Or something worse.
First say, “I’m asking this question because I want to tap into your problem-solving skills before problems happen.” Now say, “Imagine this project is over and it’s a catastrophic failure. What did we fail to do that contributed to the failure?”
“Fail to do,” is designed to extract specific actions. If you ask, “What went wrong?” the conversation will go off the rails. They’ll think of things outside their control. Maybe they’ll bring up a lousy economy.
Include a time factor for long-term projects. When projects are months from completion, say, “What did we fail to do this month….” Or “This quarter.” Short timelines require timely action.
What makes this question useful?
How would you modify the language of this question?