Once upon a time, I believed that if I built a solid project plan, executed it flawlessly, and avoided delays, everything would work out.
That’s not reality.
The plan is the easy part. The hard part is managing sponsors, stakeholders, and teams—each with competing priorities and opinions. The hard part is navigating the chaos when things inevitably go sideways.
And the hardest part? Staying calm when your “perfect” plan starts unraveling.
A colleague of mine used to keep a tinfoil helmet in his office. When things got tough, he’d put it on. It was a joke—but also a reminder: you need a way to stay grounded when the noise gets loud.
Over time, I’ve found a simple approach that works.
First, acknowledge—and embrace—the problem.
Not everything is broken. In most cases, about 80% of the project is still working as expected. The real issue is usually concentrated in a much smaller slice—often just a few critical factors causing the majority of disruption.
Next, plan a resolution.
Once you’ve identified the root issue, focus on a practical, targeted response. Don’t try to fix everything—fix what matters most.
Then, act.
Execute the plan. Progress beats overthinking.
After that, check and revise.
Monitor outcomes and adjust based on what you learn in real time.
Finally, standardize what works.
Incorporate the lessons back into your process so the next challenge is easier to handle.
If this feels familiar, it should—it’s a variation of the Plan–Do–Check–Act cycle. The difference is that in real projects, you’re not operating in a controlled loop. You’re doing it in the middle of uncertainty, pressure, and competing voices.
The plan may be the easy part.
But how you respond when it breaks—that’s the real work.
Comments are closed.