Why your strategic plan is bad and you should feel bad because you're dumb
Strategic planning season arrives the same way every year. Someone books a full-day offsite. Someone else orders lunch. A facilitator draws a two-by-two on a whiteboard. By three o'clock, you have a document with a vision statement, four strategic pillars, and a list of priorities that looks almost identical to last year's list of priorities, except two things got renamed.
Then the budget process happens in a completely separate room, run by completely different people, following a completely different calendar. And whatever connection existed between the strategy and the money gets lost somewhere between the catering invoice and the year-end audit.
This is not a failure of effort. Organizations spend real time on these processes. It is a failure of design, and specifically a failure to ask one question during the strategy process: how does this actually get paid for?
The answer, when it finally arrives, is usually "we'll figure it out in the budget." Which means the strategy never gets figured out at all. It gets filed.
The data on this is not subtle. A McKinsey survey of over 600 executives and managers found that only about half of companies effectively align their budgets with their corporate strategies. Just 53% say their organizations are in the habit of fully funding the priorities they have identified. Read that again. Nearly half of all organizations go through a strategy process and then decline to fund what came out of it. The document becomes theater. The budget becomes inertia.
I have sat in the room when a finance director opens the budget template in October and says, "okay, so what's actually changing this year?" And the honest answer is: not much. Program staff submit their numbers based on what they spent last year, plus inflation, plus whatever new thing they are hoping to get funded. The finance team consolidates it. Leadership approves it with minor adjustments. The result is institutionalized incrementalism dressed up as strategic intent. McKinsey's research confirms the pattern bluntly: at many companies, the previous year's budget simply drives decisions for the following year.
Nobody chose this. It happened because strategy and finance are treated as separate disciplines that meet once a year at a document handoff that neither side owns. According to Gartner, 67% of key functions are not aligned with business unit and corporate strategies. In nonprofits this gap is wider still, because the finance team is often under-resourced, the strategy process is often board-led, and the two conversations happen months apart with different people in the room holding different assumptions about what is actually possible.
The other thing that gets lost is specificity. Strategic plans are full of commitments to "expand access," "deepen impact," and "grow partnerships." These are not goals. They are aspirations with no address. A goal has a number, a date, and someone whose name is attached to it. An aspiration has none of those things, which is why it survives the annual planning process unscathed and unchanged. Only 2% of leaders are confident they will achieve 80 to 100% of their strategic objectives. That number is not a mystery. It is the predictable outcome of processes that produce vague commitments and then call them strategy.
The disconnect runs deeper than the executive suite. Research from Harvard Business Review found that just 5% of employees understand their company's strategy, and 71% cannot even recognize it in a multiple-choice question. So the plan gets approved in September, filed in November, and by January nobody in the building could tell you what it said. This is not a communication problem. It is a specificity problem. When strategy is abstract enough to mean anything, it ends up meaning nothing to the people who have to do the actual work.
The organizations that actually move are not the ones with the best vision statements. They are the ones that translated the vision into a sequence of decisions. A McKinsey survey found that 70% of executives did not like their company's strategy process, and 70% of board members did not trust the results. A common complaint: strategic plans don't work out or guide actual operations. What these executives are describing is the gap between what planning produces and what the organization actually needs. They want something they can use. Instead they get something they can display.
The resource problem is just as serious. According to research from Quantive, 79% of executives are concerned their organization does not allocate sufficient resources to implement their strategy. Nearly four in five. Which means the planning process is generating commitments the organization has no real intention of resourcing. At that point, the strategic plan is not a guide. It is a list of things that were aspirationally important enough to write down but not actually important enough to fund.
Saying yes to everything in a planning process feels inclusive. It also means nothing gets resourced well enough to work. Research cited in Harvard Business Review found that when everything is a priority, nothing gets the attention needed to succeed. Goals without named owners are wishes, not commitments. The strategy document with twelve priorities functions the same way as no strategy at all. Everything continues as before, just with a longer appendix.
Here is what actually helps. Research from Palladium found that 64% of successful companies build their budgets based on their strategy rather than on past behaviors, and those companies substantially outperform the ones that do not. The mechanism is not complicated. When the people who build the budget are working from the same document as the people who set strategy, the money goes where the goals are. When they work separately, the money goes where the money went last year.
A roadmap that connects strategic goals to financial capacity, by year, in enough detail that someone can look at it in March and know whether you are on track. Not a narrative. Not a Gantt chart with no money attached to it. A document that says: in year one, we need X to happen, which costs approximately Y, which we plan to fund through Z. In year two, if X worked, we build on it by doing A, which requires B. What programs are we expanding, what does that cost, who is funding it, and what do we stop doing to make room.
That last part is the one most organizations skip. Stopping something is hard. It feels like failure rather than strategy. But McKinsey is unambiguous on this point: to create a real strategy, actions and policies must remain coherent and aligned, rather than nullified by pursuing too many different initiatives or conflicting purposes. A roadmap forces this. When you have to write down what year two looks like financially, you have to decide what is not in year two. That decision is the strategy. Everything else is decoration.
If your strategy and your budget could be written by two completely different teams with no coordination and no one would notice, they probably were. A roadmap is how you fix that, and it is the only planning artifact that actually earns its place on the shelf.
What the roadmap looks like: an example
The following example is built around a fictional youth employment nonprofit. The structure is the template. Each year answers the same three questions: what do we need to accomplish, what does it cost, and where is the money coming from. Year 2 is conditional on Year 1 holding, which forces the organization to define what "holding" actually means before they spend the money.
Strategic Roadmap Example
Every item on that list is probably something someone in the building genuinely wants to do. Naming what is out of scope is how you protect what is in scope from being quietly diluted over the next eighteen months.
The gap between strategy and budget does not close on its own
It closes when someone decides that the plan has to carry the money, and the money has to carry the plan, and someone with an outside vantage point helps you see exactly where those two things are drifting apart.
Big Left works with leaders who are past the early stage and into the phase where decisions compound. If what you read here describes something real in your organization, a Strategic Working Session is the right place to start. It is a private, focused conversation, not a pitch. You bring the situation as it actually exists. We look at it without the internal gravity.
