By the second week of April, your annual plan is fiction.
You wrote it in November. Maybe early December. You took two days at an offsite. You used the framework the consultants brought. You boxed in the strategic priorities. You built the OKRs. You presented it to the board. They nodded.
It was honest work. Nothing about it was sloppy. And by April, somewhere between the fifth and seventh inputs the world delivered that nobody at that offsite anticipated — a tariff, a reorg at a major customer, a hire that didn't land, a competitor who priced lower than your entire margin model — the plan was already off. By April you weren't running it. You were rationalizing it.
This isn't a failure of effort.
It's a failure of architecture.
The annual plan is a 1950s artifact. It was built for an era when the economic environment changed slowly, capital cycles were long, and information moved through filtered channels. In that world, sitting down once a year and projecting twelve months out was a reasonable computational task. The variance between forecast and reality was small enough that an annual cadence was sufficient.
Today's environment doesn't operate that way. The signal-to-noise ratio shifted. The information environment is denser, faster, less filtered. Competitive moats decay faster. Buyer behavior recalibrates faster. The macro reorders faster. The probability that any twelve-month forecast survives meaningful contact with reality is approaching zero.
And yet most companies still treat the annual plan as the central organizing artifact. They tighten it. They add more rigor. They run more scenarios at the offsite. They believe the failure was that the plan wasn't good enough — when the actual failure is that the plan is the wrong kind of thing entirely.
The lineage knew this.
Pierre Wack figured it out at Royal Dutch Shell in 1973. He wasn't trying to predict the future. He was trying to build organizational muscle for navigating futures. The scenario planning he installed at Shell didn't try to be more accurate than the annual plan — it tried to make Shell less brittle in the face of what no plan could anticipate. When OPEC happened, Shell wasn't right. They were prepared.
Peter Schwartz extended the discipline through the Global Business Network and The Art of the Long View. Tom Chermack — my doctoral advisor at Colorado State, the most direct living academic descendant of Wack's lineage — has spent his career formalizing the practice for both an academic and corporate audience.
What none of them had, until now, is the technological substrate to make this discipline continuous instead of episodic. Wack ran scenario sessions at Shell quarterly at best. Chermack's clients run them once or twice a year. The work was always limited by how often a senior team could sit in a room together and grind through it.
That constraint is gone.
What's actually changed.
What we have now, that Wack didn't, is real-time signal aggregation across the full information environment. Persistent memory of what we said and what we believed. Pattern recognition across thousands of weak signals that humans would miss. Generation of plausible scenario branches faster than humans can write them. Collaborative working surfaces where senior teams can hold the work continuously instead of episodically.
The technology doesn't replace the discipline. It removes the constraint that made the discipline episodic. That changes everything.
The technology doesn't replace the discipline. It removes the constraint that made the discipline episodic.
What replaces the annual plan.
What replaces it is what I call the Predictive Planning Loop. Four moves, run continuously.
Scan.
What's actually changing in the operating environment? Not the press releases, not the conference talking points — the underlying signals. Tariff policy. Talent flow. Capital costs. Buyer attention. Competitor pricing tells. AI capability frontiers. The Loop's first job is making sure the team is reading the same environment.
Story.
What story are we telling about what those signals mean? Not the consensus story — the plural stories. Multiple scenarios, each internally consistent, each with implications. The discipline of holding three live scenarios at once is what stops the team from getting captured by a single narrative.
Stake.
Where are we placing the company's chips? Given the scenarios, what positions do we hold, what positions do we hedge, what positions do we abandon? Stake is where strategy becomes operational. Stake is where capital allocation, hiring, product roadmap, and partnership decisions get pinned to a scenario logic.
Steer.
What do we change as the signals update? Not what do we do differently in next year's offsite — what do we change this week? Steer is the part most companies miss entirely, because they're running the annual plan ritual, not the Loop.
Run these four moves once a year and you have an annual plan. Run them every two weeks and you have a Loop.
This isn't easier.
The Loop is harder than the annual plan. It requires senior teams to hold strategic work as a continuous practice instead of an annual event. It requires comfort with uncertainty as a permanent operating condition. It requires actually engaging with disconfirming information rather than tucking it into next quarter's review.
Most companies won't do it. The annual plan persists because it's a ritual, and rituals serve organizational psychology even when they don't serve operational reality. The annual plan lets the team feel aligned, feel directed, feel like they did the strategic work. That feeling is valuable. It just isn't the same as actually being strategic.
The companies that move to the Loop won't all win — there's no algorithm for that — but the companies that don't move are stuck running planning theater while their environment outpaces them. By April. Like clockwork.
Why I'm writing about this.
I run six businesses. Real estate development. Property management. A landscaping company. A short-term rental brand. A creative services firm where I'm Chief Solutions Officer. A holding company. Every single one of them operates in an environment where the annual plan would be useless by April.
What works isn't a tighter plan. It's the Loop. Scan, Story, Stake, Steer. Run continuously. Held by the senior team. Treated as the actual job.
This essay is the first piece in a longer body of work I'm building toward two books and a discipline I'm calling Predictive Planning. The Predictive Planning Institute exists to formalize the practice for executives who have noticed that their annual plan goes stale by April — and are ready to do something about it.
— Tim