The strategic planning process has a reputation problem. Ask most senior leaders about the last one they went through and you will hear a version of the same story: a lot of meetings, a lot of slides, a document that was referenced once and then quietly shelved. That reputation is earned. But it is not inevitable. The difference between a planning process that produces a living strategy and one that produces a filing cabinet entry comes down to a small number of decisions made at the very beginning.
Start with the diagnostic, not the framework ¶
The most common mistake in strategic planning is arriving with a framework before you have understood the business. Frameworks are useful, but they are tools for organising thinking, not substitutes for it. Before any planning session, spend at least a week doing diagnostic interviews with the leadership team individually, reviewing the last two years of financial and operational data, and asking the question that most planning processes skip: what decisions has this organisation been avoiding, and why? The answers to that question will shape everything that follows.
Separate the diagnosis from the planning ¶
One of the structural errors in many planning processes is conflating the diagnostic phase with the planning phase. When a leadership team is simultaneously trying to understand what is true about their business and decide what to do about it, the diagnosis gets contaminated by the planning. People stop being honest about problems because they are already defending their preferred solutions. Run the diagnostic first, share the findings with the team before any planning begins, and give people time to sit with uncomfortable data before they are asked to respond to it.
Make the trade-offs explicit ¶
A strategy that does not say no to anything is not a strategy. It is a wish list. The most important work in any planning process is the moment when the leadership team has to choose between two things they both want and cannot have simultaneously. That conversation is uncomfortable. It is also the conversation that produces a real strategy. If your planning process does not include at least one genuinely difficult trade-off discussion, the resulting document will be too vague to guide real decisions.
Write the strategy for the people who have to execute it ¶
The audience for a strategy document is not the board or the investors. It is the people who have to make daily decisions in line with it. That means writing it in plain language, being specific about priorities and timelines, and including enough context that someone who was not in the planning sessions can understand why the choices were made. A strategy document that requires a briefing to interpret is a strategy document that will not be used.
Build in a review cadence before you finish ¶
The planning process is not finished when the document is written. It is finished when the organisation has agreed on how and when it will review progress against the strategy. That means a specific review date, a specific set of questions to ask at that review, and a named person responsible for convening it. Without that, even a well-written strategy will drift. The review cadence is not an afterthought. It is the mechanism that keeps the strategy alive.
A strategic planning process done well is one of the most useful things a leadership team can go through together. Done badly, it wastes time and produces cynicism. The difference is almost always in the preparation and the willingness to have the difficult conversations early. If you are planning a strategy process for the coming months, the articles section has more on the specific questions worth asking.