Strategic Planning = Organizational Design Problem
Strategy development is hard, uncomfortable, and easy to unintentionally undermine. It's also one of the highest-leverage opportunities available to a leadership team — a chance to get out of operational mode, surface real disagreement, and build the structural conditions for meaningful change.
Intentional upfront investment dramatically improves both the process and the outcome. Most strategic planning failures are not failures of vision. They're failures of setup.
This piece covers three setup decisions that determine whether a strategic plan works: how you define the problem, who you involve and when, and how you design the process itself.
A preliminary note on timing
If your organization operates in a genuinely dynamic environment — volatile funding, shifting partners, unstable operating conditions — a multi-year strategic plan may not be the right tool. Rigid long-range plans frequently collapse under external pressure, and the investment is wasted. If significant instability is likely, conserve resources. Do major planning when you have a reasonable expectation of stability to build from. Shorter planning horizons or more adaptive frameworks may serve you better than a traditional strategic plan.
On problem definition
Clarity on the specific problem you're solving is ideal. It's also not always possible at the outset — it can emerge through the early stages of the process. What matters is that it gets resolved before you bring in a broader audience.
What you do need to be clear on from the start is the type of work the plan is meant to accomplish. There are three distinct approaches, and they are not interchangeable:
Resolve root causes. Address the underlying structural conditions driving your organization's challenges.
Position for the future. Set direction and build capacity for where the organization needs to go, independent of current problems.
Manage symptoms. Address pain points without tackling what caused them — because root causes aren't currently addressable.
The third approach is more tactical than strategic in nature. That's not disqualifying, but it needs to be named accurately. Misrepresenting tactical work as strategic planning creates a participation problem: people show up expecting one kind of process and encounter another. That gap erodes trust before the work has begun.
On participation
Without intentional participation design, most organizations default to one of two patterns — and both underperform.
The first: senior leaders define a vision and open it to broad organizational input. Participation feels inclusive. In practice, the input is largely reactive, constrained by a vision that's already set. If that process surfaces a significant gap between leadership direction and team perspective, the problem hasn't been solved — it's been exposed without a mechanism to address it, compounding whatever morale issues already exist.
The second: vision developed through consensus. This typically produces plans that lack strategic coherence or are disconnected from operational reality, and tends to reinforce the senior leadership instinct to control the process next time.
Breaking this cycle requires a deliberate participation plan built around capability, not hierarchy.
Ask: Who are the genuinely creative thinkers in your organization? Who understands the major facets of the challenges you're navigating? Who will surface dissent without shutting down the room? Who defaults to agreement regardless of their actual view?
People who default to agreement may have a real role in plan implementation. They are often not the right participants in plan creation. Being transparent about who is involved in which phase — and why — is not exclusionary. It's structurally honest, and skills-based logic is harder to argue with than positional logic.
Once your participation plan is drafted, audit it. Check for overlooked perspectives and overrepresented ones. Assess seniority mix. If there are ways of working you want to shift, the strategic planning process is an opportunity to model the behavioral norms you're trying to establish.
This is significant upfront work. It also has direct utility in talent reviews and performance assessments — the investment creates returns beyond the plan itself.
On process
There is no perfect process. The goal is a process that is well-matched to your organization, your timeline, and the actual importance of the outcome right now.
Before designing it, be honest about two things:
First, how much this plan actually matters at this moment. Strategy is not always the priority. If it isn't, set proportionate expectations around time and effort — for yourself and for participants.
Second, how you've approached strategy development before — and whether doing it differently might produce better results. The familiar process has familiar failure modes. Consider what a genuinely different approach would look like, what it would make possible, and what it would cost.
Once you've made those calls, communicate what to expect and when. Uncertainty about process generates anxiety even when the underlying content is uncontroversial. Get ahead of it.
Good strategic planning is nonlinear. It involves productive disagreement, iterated assumptions, and compromise that improves the original vision rather than diluting it. Build the conditions for that. Then let the process work.