Breaking loose: Mary Poppendieck's landmark presentation

Actually, you'd be perfectly alright just abandoning this post right here(mostly ranting anyway) and using your time more wisely with the presentation by Mary Poppendieck.

--

In theory, plans are supposed to make things better. They promise clarity, direction, and control, taming the chaos of uncertainty with neat timelines and tidy assumptions. But in practice, they often deliver the opposite. Plans, especially in dynamic environments, become fragile artifacts, undermined by the very complexity they seek to manage.

It wouldn't be wildly inaccurate to ascribe obsessive detailed plans to leadership's utter failure to regulate their anxiety.

Mary Poppendieck’s presentation The Tyranny of the Plan is a masterclass in dismantling this illusion. Drawing from her experiences in manufacturing and software development, she illustrates how rigid plans can become liabilities, trapping teams in cycles of inefficiency and chaos.

When Plans Go Wrong

Poppendieck recounts her time working with Material Requirements Planning (MRP) systems in manufacturing during the 1980s. These systems, hailed as breakthroughs at the time, revealed a glaring flaw: "nervousness." When reality diverged even slightly from the plan, the system would very quickly spiral into instability, requiring frequent and disruptive re-planning. The result was a workflow riddled with inefficiencies, where the plan became a source of chaos rather than order. More anxiety in fact, originally the plan was supposed to be a bandaid on anxiety.

She contrasts this with pull systems like Kanban, which align closely with actual conditions. These systems thrive on flexibility, responding to variability rather than resisting it. By prioritizing adaptability over rigidity, teams using pull systems saw dramatic improvements in reliability and efficiency.

This is all pretty par-for-the-course stuff today. It should be at least, but we know the adoption goes hardly beyond symbols in most places.

A Construction Marvel

The most striking example in the presentation is the construction of the Empire State Building, completed in 1931. The building took an incredible eight months, and the project was 18% under budget. Despite lacking modern computerized planning tools, the project was finished on time and under budget. How? Through adaptive planning and efficient workflows. The builders didn’t rely on static, long-term plans. Instead, they embraced the realities of the moment, collaborating and adjusting as needed. It’s a testament to the power of flexibility in the face of complexity.

Lessons for Software Teams

There's a lot of wisdom for us in the software world. Rigid sprint goals and fixed roadmaps may look reassuring, but they often lead teams astray, locking them into commitments that no longer reflect reality.

Poppendieck points to the construction industry’s Last Planner System as a model for short-term, collaborative planning. This approach emphasizes aligning the work with current conditions rather than a distant, often irrelevant plan. In software, this could mean focusing on iterative development, embracing variability, and building systems that adapt rather than break under change.

The Virtue of Deep Understanding

For any of the magic to become possible, one needs to get really down in the operations. There is a profound virtue in carefully studying and understanding operations: the behaviors, the friction points between various functions, and the patterns that emerge over time.

This can be exciting work, and it’s essential. By observing how teams interact with systems and identifying sources of friction and pileups, we can establish baseline metrics. These metrics become the foundation of continuous improvement: an iterative process of cranking the dial to see what works, what breaks, and what can be made better.

Rather than imposing plans from above, this approach empowers teams to align their actions with real-world conditions. It’s not about forcing a system to conform to a plan but about finding ways to adapt the system to reality, ensuring it becomes stronger, faster, and more resilient.

A Shift in Mindset

At its core, Poppendieck’s argument isn’t just about better processes; it’s about a fundamental shift in mindset. The problem with plans is not that they exist, but that we place too much faith in them. A plan is, at best, a hypothesis. To treat it as a guarantee is to invite failure.

Much more profitable to place your faith in your teams. Provided, that is, that you've done a good job of hiring smart, motivated people. Show them the direction, give them the constraints, and tell them to go have fun with the metrics.

Go from a rigid Plan to Planning as a dynamic process. A living, breathing practice of continuous learning and adaptation. A culture. It’s about setting direction without dictating steps, creating systems that respond to feedback, and building teams that thrive in uncertainty rather than fear it.

Beyond the Tyranny

In the natural world, adaptation is survival. Evolution doesn’t follow a plan; it experiments, iterates, and responds to change. The most successful species aren’t those with the most elaborate blueprints but those with the ability to pivot.

Whether building skyscrapers or software, we exist in ecosystems of shifting variables. To succeed, we must move beyond the tyranny of the plan, designing for adaptability, embracing uncertainty, and cultivating resilience.

In the end, Poppendieck’s insights remind us that plans are not sacred. They are useful, but not infallible. To cling to them too tightly is to miss the point entirely. Because real progress happens not in the execution of a plan, but in the ability to respond when the plan falls apart.

A rant in closing

The tyranny of the plan persists because it’s easier than thinking. Plans give the illusion of progress, even when we’re marching straight off a cliff. But real progress comes from admitting we don’t have all the answers. It means adapting, learning, and yes, sometimes throwing out the plan altogether.

Let’s stop pretending that plans are sacred. They’re tools. Use them, but don’t worship them. And for the love of everything sensible, don’t let them control you. Because when the plan becomes the goal, we’ve already lost.

Next time you see a Gantt chart, become very very suspicious. And take action.