Research mining more than 20,000 real strategic plans found that 84.5% of strategic projects never actually reach completion — only 12.5% ever get finished, and just 5.7% of organizations complete 75% or more of what they set out to do in a given year.

The reason isn’t that businesses are bad at planning. It’s that the traditional annual planning process is built for a pace of change that no longer exists. A typical enterprise annual plan takes five to six months to build — gathering data, building presentations, getting budget approval — which means by the time the plan actually takes effect, several months of the year it’s supposed to guide are already gone, based on market conditions that existed half a year earlier.

The Shift Already Underway

The response isn’t “stop planning.” It’s a move toward treating the plan as a living document instead of a locked-in yearly commitment — quarterly strategy sprints that revisit and adjust the annual goals based on what’s actually happened, rather than a single planning event followed by eleven months of hoping reality cooperates. Some of this shift is being driven by how fast markets are genuinely moving now — new competitors, new tools, entire new categories of capability appearing within a single quarter, not a single year.

None of this means strategic thinking has become less important. What’s changed is the format: less annual ritual, more continuous adjustment against a clear direction.

Brandon’s Take

I’ve built the big, formal version of this plenty of times — 20, 30, 50-plus page documents outlining every piece of the business, both here and in corporate roles before this. It never really worked for me. What works instead is breaking things into segments and planning at a smaller scale: quarterly for big projects, monthly for the lighter work and the specific tasks that feed into those larger quarterly items. Yearly planning, for me, isn’t a massive document — it’s really three questions: what’s working and how do we sustain and grow it, what needs growing that isn’t getting enough attention yet, and what isn’t working and should be sunset.

This year broke that pattern a little. Building a full end-to-end software platform — the Intelligence Layers running underneath everything, and the individual platform agents that can eventually run parts of a business on their own — genuinely required a much bigger plan than usual. I managed it the same way I manage everything else, just at a larger scale: broken into my six software platforms and four consulting segments, with smaller project plans inside each one that get reviewed monthly. The big plan never sits still. It gets updated constantly with what’s working, what isn’t, and where something needs to pivot.

Every feature and platform decision runs through the same basic filter. First, a real cost analysis — not just what it costs to build and what it might generate, but the actual time value: is this something that eats a significant amount of time to build for a relatively small return? Second, brand trust — does this genuinely improve how much people trust the business, independent of direct revenue. That combination has been a solid formula for deciding what actually gets prioritized.

STELLA is the clearest example of where the plan genuinely changed mid-year. I believe in what STELLA’s database management and custom reporting does — every business could use it. But it’s a hard sell, because most business owners don’t know the first thing about custom reporting and don’t come looking for it. STELLA Ledger came directly out of that realization. The original plan had STELLA integrating with QuickBooks and other existing expense software through their APIs. Working through those integrations turned out to be broad, complicated, and honestly not worth the effort compared to just building expense tracking natively into STELLA myself. The plan changed because the market reality changed my understanding of it partway through, not because the original plan was wrong on paper.

If someone’s starting from zero with no formal planning process at all, my advice is simple: start small. Look at your business, your actual work, and pick the areas where you genuinely want to see growth. Build a monthly plan around what needs to happen to start moving those specific goals. Once that rhythm feels comfortable, extend the horizon and start planning quarterly for the bigger items. Don’t start with the fifty-page document. Start with the next month.

Frequently Asked Questions

Is any annual planning still worth doing for a small business?

Yes, but as a lighter, higher-level exercise — what to sustain, what to grow, what to sunset — not a heavy, all-encompassing document that takes months to produce and goes stale just as fast.

How often should a small business revisit its plan?

Monthly for smaller, immediate work; quarterly for larger projects. The exact cadence matters less than actually revisiting it regularly rather than writing it once a year and setting it aside.

What’s a sign a business has outgrown informal planning?

When a decision genuinely requires coordinating multiple large workstreams at once — the way building a full software platform did this year — it may be worth a larger, more structured plan, broken into manageable segments rather than one massive document.