Why Your Plan Didn’t Survive

This is the first in a four-part series exploring the ideas behind Pattern and Flow's complexity practice. Each post stands alone. Together, they build a foundation for working differently with organizational challenges that resist planning.

Snow and moss on a concrete block

The Gap Between Planning and Living

Think of a time when you made a plan that didn't survive contact with what actually happened.

Not a plan that was poorly conceived. A plan that was thorough, well-resourced, and carefully reasoned — and still fell apart when it met the situation it was designed for.

Most of us have had this experience more than once. And most of us have drawn the same conclusion: we need to plan better. More data. More stakeholder input. More contingency scenarios. A more rigorous process.

But what if the problem isn't the quality of the planning? What if it's something more fundamental — a confusion about what kind of situation we're actually in?

One Model of Reality, Applied Everywhere

We've inherited a particular model of how the world works. It's a mechanistic model — one where everything is knowable, controllable, and predictable if we just analyze enough. This model has been enormously productive. It built bridges, eradicated diseases, and sent people to the moon.

And we've learned to apply it everywhere.

Strategic planning processes, organizational change initiatives, performance management systems — they all share the same underlying assumption: that if we gather enough information and apply enough expertise, we can predict and control the outcome.

For some challenges, this assumption holds. When your car won't start, you don't need innovation. You need a mechanic who can find the known issue. When you're designing a new program, you can research what's worked elsewhere, analyze your context, and adapt accordingly.

But some situations are fundamentally different.

Two Kinds of Challenges

Some challenges have discoverable patterns. Proven practices exist. Expertise helps. Analysis reveals the answer. These are the domains where our inherited planning methods actually work — and they work well.

But some challenges are constituted through relationship. What happens depends on who's engaging and how. The situation responds to your presence. The act of intervening changes what's there.

Building trust in a fractured team. Navigating a merger where two cultures are colliding. Trying to shift an organizational dynamic that everyone can feel but no one can name. These aren't problems with hidden solutions waiting to be discovered. They're living situations — made of connections that shift as you engage them.

You can't stand outside and plan for these situations. You have to be in relationship with them.

The Mismatch

The failure mode of most strategic planning isn't poor execution. It's ontological confusion — a mismatch between the kind of situation we're in and the kind of engagement we're bringing to it.

When we bring mechanistic methods to living systems, predictable things happen. We create plans that can't account for how the system responds to our planning. We measure things that were never stable enough to measure. We optimize in ways that destroy the very vitality we depend on. We mistake coherence — which is alive — for alignment, which is imposed.

This isn't about abandoning rigor. It's about matching your methods to what's actually happening.

A Different Starting Point

What if, before making your next plan, you paused and asked a different question?

Not what's the right strategy? but what kind of situation am I actually in?

Not how do I control this outcome? but what kind of engagement is this situation inviting?

This is the shift from planning as default to sensing as starting point. It doesn't replace planning — it puts planning in its proper place, as one mode of engagement among several, appropriate for some situations and actively harmful in others.

The next post in this series introduces a practical framework for making this distinction — not as an intellectual exercise, but as a sensing practice you can use the next time you're facing something that doesn't respond to planning.

Continue Exploring

Next:Sensing Before Solving: A Different Way to Read the Room — A framework for recognizing what kind of engagement a situation is actually inviting.

Also in this series:

Pattern and Flow works with practitioners and organizations operating at the limits of what planning can accomplish. If this resonates with something you're experiencing, we'd welcome a conversation.

Previous
Previous

Sensing Before Solving