What Dies First: The Five-Year Plan, the Org Chart, the Quarterly Review

Run a test this week. Find your five-year plan, open it to the section on AI, and ask whether the version written twelve months ago would tell you anything useful about where you are today. For most of us the answer is no — and that’s the whole problem with static planning. The artifact didn’t fail because it was badly made. It failed because the thing it predicts moves faster than the cadence on which you refresh it.

That’s the claim worth taking seriously: when capability compounds on a monthly clock, the five-year plan, the budget locked in October, and the quarterly review as a decision unit stop earning their keep — not because planning is bad, but because freezing its output into a year-long commitment is now a way of being reliably wrong.

This piece was sparked by The New Era of Jobs: Organizational Singularity with Peter Diamandis and Salim Ismail, where Ismail put it flatly: “the five-year plan dies completely. In fact, any static planning dies.” Worth checking what actually dies, what survives, and where it overshoots.

The mechanism: your feedback loop has to be shorter than your decision horizon #

A plan is a bet on a forecast, and a forecast is only as good as the half-life of its assumptions. When the system changes slowly, a five-year horizon on an annual refresh is fine. When it changes fast, the gap between updates is the gap between your map and the territory. This is a control-systems fact, not an ideological one.

Bridget McCormack, president of the American Arbitration Association and former Chief Justice of the Michigan Supreme Court, gave the AI-specific version to the 2024 NYSBA Annual Meeting: “You have to throw your own long-term strategic plan out the door. You no longer have the ability to plan five years from now” (NYSBA). The state of a given AI capability at year-end tells you almost nothing about where it lands twelve months later — the forecast has no persistence, so a plan built on it has no shelf life.

The same principle has quietly reshaped finance for two decades. A fixed annual budget bakes in October assumptions that barely relate to reality by March; the standard fix is a rolling 12–18 month forecast refreshed monthly, so the plan tracks the world instead of diverging from it (80/20 Consulting). (There’s a behavioral failure mode often cited alongside fixed budgets too — teams burning remaining allocation late in the year to protect next year’s number — but treat that as a widely reported pattern, not something the linked source documents.) The broader shift toward continuous planning now has its own literature, with practitioners arguing static planning simply stopped working in volatile markets (Apliqo). Beyond Budgeting has made this case since the early 2000s; AI velocity just turns a finance-team nicety into a whole-org survival requirement.

The clearest proxy: how often you tell people how they’re doing #

For a measurable read on whether static cadences are dying, watch the performance review — the most entrenched annual ritual a company has. Only 14% of employees strongly agree that annual reviews inspire them to improve; people who get weekly feedback show 2.7x higher engagement than those on annual cycles; and companies that moved to continuous feedback saw 14.9% lower turnover (Happily.ai). Same mechanism as the strategy case: the feedback loop has to be shorter than the decision horizon, or the signal arrives too late to change anything.

The same pressure reaches the quarterly business review, the last periodic ritual standing. Some large operators — Amazon, Microsoft, Google among them — have leaned into more frequent, real-time feedback practices alongside or in place of the rigid quarterly cadence (EvaluationsHub). Here it’s easy to overstate, so be precise: that same source’s FAQ says QBRs are evolving, not dead. The review isn’t vanishing as a moment to step back — what’s dying is the review as the unit of decision, the idea that a market shifting monthly should wait ninety days for a verdict.

Where the practitioner literature is landing #

This isn’t only operators talking their book. A February 2026 California Management Review article by Jonathan Hughes — a practitioner analysis drawing on roughly 80 strategy engagements over 25 years, not a peer-reviewed academic paper — argues that “multi-year strategic plans create false predictability and organizational resistance to adaptation,” prescribing circular, continuously updated, bottom-up planning over episodic top-down cycles (California Management Review).

Its canonical example is Adobe’s 2011–2015 shift from perpetual licenses to cloud subscriptions. Adobe abandoned multi-year projections built on boxed-software sales and made rolling 12-month subscriber metrics the primary decision variable. Reported revenue fell before it recovered; getting through required quarterly course-correction, not adherence to a plan — and by 2015 it had repriced its market cap dramatically upward. It’s now the textbook case of continuous planning beating static commitment.

That’s the same move Diamandis and Ismail describe: when execution and coordination collapse in cost, the org chart stops being a fixed structure that changes only on an event like an M&A and starts adapting continuously — “the organization itself becomes a protocol.” The five-year plan dies for the same reason a protocol updates every loop and a plan updates once a year.

The honest counter-section: what the slogan gets wrong #

Stop here and you’ll draw the wrong conclusion — that thinking ahead is obsolete. It isn’t, and the strongest objections come from the same evidence.

Planning is essential; the plan is not. McKinsey’s work on agile performance units finds they don’t abandon forward thinking — they still run quarterly planning sessions and maintain “actionable strategic guidance.” The durable formulation, usually traced to Eisenhower: plans are worthless, but planning is everything. The error isn’t thinking five years out; it’s treating that thinking’s output as a binding commitment instead of a current best guess.

Killing the five-year plan can collapse into quarterly myopia. Long-horizon orientation still wins on the numbers: McKinsey’s 2017 analysis found long-term-oriented companies posted 47% higher revenue growth over 2001–2014. Delete the long view without a genuine continuous loop to replace it and you don’t get adaptive — you get earnings-call short-termism, the exact disease long-term planning was invented to cure. “Continuous” has to mean continuously oriented toward a durable purpose, not reacting to this month’s noise.

Adoption lags the rhetoric badly. A recent FP&A Trends poll found only about 1% of companies have fully eliminated the annual budget, and roughly 70% haven’t started. Beyond Budgeting, decades old, still sees only gradual uptake. This is a directional prediction, not how most organizations operate today — anyone claiming the five-year plan is already dead is selling the destination as the current address.

Agile’s edge is “readiness,” not a clean head-to-head win. A joint McKinsey/Harvard Business School study of 25 organizations across seven industries found fully agile business units showed enhanced readiness to confront the repercussions of the COVID-19 disruption — stronger customer satisfaction, employee engagement, and operational efficiency through the shock (Businessmap). Worth stating precisely: that’s readiness under stress, not a controlled experiment proving agile units beat static-planning peers. Directional, not a verdict.

And the plan may persist for reasons unrelated to prediction. Boards and capital allocators require planning artifacts as fiduciary instruments; advisory firms still sell multi-year AI roadmaps in 2026 precisely because the five-year plan does governance work even when it does no predictive work — part of the accountability shell the same conversation elsewhere calls the “fiduciary wedge.” The org chart and the long plan may outlive their usefulness simply because someone has to be accountable to a document. That’s not a refutation. It’s why the old artifacts linger long after they’ve stopped telling you anything true.

What to actually do with this #

The builder’s version isn’t “stop planning.” It’s “shorten the loop until it’s faster than the thing you’re planning around,” and keep the parts that were never about prediction.

• Convert plans into living forecasts. Keep the document; kill the freeze. A rolling 12–18 month forecast refreshed monthly tracks reality instead of diverging from it. The artifact survives; the annual commitment dies.
• Make the feedback loop shorter than the decision horizon. Wherever you’re learning slower than the world moves — annual reviews, quarterly verdicts, October budgets — close the gap. That inequality is the whole thesis.
• Separate the durable purpose from the perishable plan. Hold the long-horizon orientation behind that 47% revenue-growth gap; let the commitments underneath churn. Continuous must not mean myopic.
• Keep the artifacts that do governance work, and be honest that’s their job — an accountability instrument for the board, not a prediction you defend out of habit.

“Any static planning dies” is the right direction and the wrong tense. Planning isn’t dying — static planning is, and slowly. The winners won’t be the companies that threw away the plan, but the ones who turned it from a yearly statue into something that updates every loop, while everyone else defends a forecast that went stale in Q1.