Heroic Firefighter or Poor Planner? The Cost of Chasing Crises

There is a dangerous ego trip inside project management: the addiction to heroism. Everyone loves the project manager who steps into a burning crisis at the eleventh hour, pulls an all-nighter, reroutes resources, and miraculously gets the deliverable over the line. They get the praise, the executive call-out, and the pat on the back.

Let’s stop celebrating firefighters for putting out blazes they should have designed out of the system in the first place.

Constant firefighting isn’t agile leadership. It is the hallmark of an undisciplined process where teams are so busy reacting to unmanaged hazards that planned forward progress grinds to a halt.

The Shop-Floor Reality: The Avoidable Bottleneck

Consider an operational tooling changeover where key supplier components arrive three weeks late, missing critical regulatory tolerances. The project lead rushes around, renegotiates freight at premium emergency rates, and reallocates weekend shifts to compensate. It looks heroic. Yet a quick glance at previous supplier reviews reveals the exact same vendor missed the exact same tolerances on the last two installations. The crisis wasn’t bad luck; it was ignored history.

Actionable Fixes: Engineering Resilience Upfront

  • Separate Local Problems from Systemic Issues: Understand the boundary of your authority. If a glitch can be resolved within existing tolerances, solve it immediately on the shop floor. If an issue represents a realised risk requiring unallocated capital or sponsor intervention, escalate it without delay instead of quietly absorbing the impact.
  • Run Root-Cause Audits (Not Blame Sessions): When unexpected friction stalls progress, deploy standard 5 Whys or fishbone analyses with hands-on problem solvers to pinpoint the process breakdown rather than scolding the individual.
  • Use Historical Variance for Risk Augmentation: Stop treating risk registers as static compliance documents. Analyse past delivery datasets and historical project milestones to predict likely points of failure before you allocate capital.

Put It to the Test

Look at the last major crisis your team had to navigate. Was it truly an unpredictable “black swan”, or was it a predictable failure mode that your system simply chose to ignore? Tell me how much time you spent fixing it versus fixing the process that caused it.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Website Powered by WordPress.com.

Up ↑