A practical guide to running a strategic planning process

Strategic planning has a reputation problem. Organizations that have been through a planning process that produced a binder no one read are understandably skeptical of the next one. The problem is usually not that planning is useless. It is that most planning processes are designed to feel thorough rather than to produce decisions.

What a planning process needs to produce ¶

A useful strategic plan is not a vision statement and a list of goals. It is a set of decisions: what the organization will prioritize, what it will not prioritize, and how it will make choices when those priorities conflict. Those decisions need to be specific enough that a manager three levels down can use them to make a resource allocation decision without escalating.

If the plan cannot do that, it is not a plan. It is a document.

The inputs that actually matter ¶

Most planning processes collect too much data and not enough perspective. Market research, competitive analysis, financial projections. These are useful inputs, but they do not substitute for a direct conversation with the people who understand the organization's actual constraints and capabilities.

The most valuable input to a planning process is usually a structured conversation with the leadership team about what they believe is true, what they are uncertain about, and what they are avoiding. That conversation is harder to facilitate than a SWOT analysis, but it is where the useful information lives.

What a planning process can safely skip ¶

A planning process does not need a two-day offsite, a proprietary framework, or a consultant who charges by the slide. It does not need to involve every level of the organization simultaneously. And it does not need to produce a document that covers every possible contingency.

What it needs is a clear question (what are we trying to decide?), the right people in the room, enough time to work through genuine disagreements, and a written output that is specific enough to be useful.

• A two-day offsite (useful for some things, not required for planning)
• A proprietary framework imposed on every situation
• A document that covers every possible contingency
• Simultaneous involvement of every organizational level

The planning processes that produce the most useful outputs tend to be shorter and more focused than the ones that feel most thorough. If your last planning process produced a document that no one references, it is worth asking what a different approach might look like.