When a Plan Comes Together

The most common mistake I see in strategic planning is treating a plan as a prediction. The team produces a document that describes where the business will be in three years, and the document is treated as correct until it is not. When reality diverges (and it always does), the response is either to revise the plan frantically or to explain why the divergence does not count. Neither is useful.

A plan is not a prediction. It is a commitment to think clearly about what matters before the pressure is on. The value of a plan is not in its accuracy. It is in the quality of thinking that produced it, and in the shared understanding that thinking created inside the team.

Most plans fail not because the thinking was wrong, but because the thinking was never really done.

When I work through a planning process with a leadership team, I am watching for a specific thing: do the people in the room actually agree on what the business is trying to do? Not on the language of the slide. On the real thing. What problem are we solving? For whom? With what advantage? What are we willing to trade off, and what are we not? These questions are rarely as settled as they appear. The plan is where those disagreements become visible.

A good plan is one that the team understood well enough to deviate from intelligently. When something unexpected happens, the question is not whether the plan was right. The question is whether the thinking behind the plan was clear enough to reason from. If it was, the team can adapt. If it was not, they are starting from scratch under pressure.