AntiPatterns

MANAGEMENT · DEATH BY PLANNING

Death by Planning

CATALOG ENTRY
Also known as: Glass Case Plan, Detailitis Plan.

In many organizations, detailed planning is assumed to be free of downside. That assumption holds for manufacturing. It does not hold for software, where the work is full of unknowns that a plan can't see coming. Death by Planning happens when a plan for a software project gets taken more seriously than the software itself.

"Hooray, we've got a PLAN!"
"Hooray, we've got a PLAN!"
"We can't get started until we have a complete program plan." "The plan is the only thing that will ensure our success." "As long as we follow the plan and don't diverge from it we will be successful." "We have a plan, we just need to follow it!"

Projects fail from over-planning as often as under-planning. Either way, the plan becomes the deliverable people actually manage to, while the software itself drifts.

Refactored Solution

Rational Planning: replan from facts as the project produces them, rather than defending a document written before anyone knew what the real problems were. A plan is a forecast, not a commitment device, and it should update as often as the facts do.

Specification
Also Known As
Glass Case Plan, Detailitis Plan
Most Frequent Scale
Enterprise
Root Causes
Avarice, Ignorance, Haste
Unbalanced Forces
Management of Complexity
Refactored Solution
Rational Planning
© Copyright 2017–2026 William Brown, Raphael Malveau, Hays McCormick, Thomas Mowbray, and Scott W. Thomas. All rights reserved.
For problems or questions regarding this web contact [Web Master].
Last updated: September 12, 2026
View the 1999 site — Nostalgia ↗