It’s planning season. Your plan is already obsolete.
Right now, in most companies, someone is copying last year's spreadsheet forward and calling it next year's plan. It will be presented with confidence, approved before the holidays, and missed by April. Not because the people building it are careless. Because the world it describes keeps moving after the file is saved.
What has moved while the plan was being built.
Most planning cycles open the first week of September. These are the signals a 2027 plan leans on, measured from that week to the latest reading. Updated daily from the Federal Reserve’s FRED database. No forecast, just the record.
What it tests: Housing demand and how much room household budgets have.
What it tests: The cost of moving anything physical.
What it tests: What it costs a solid company to borrow.
What it tests: How calm a year you assumed.
What it tests: Your hiring plan and your demand forecast.
What it tests: How much the market is charging for corporate risk.
What it tests: Your view of where rates and growth go next.
What it tests: Energy, freight and input-cost lines.
What it tests: How long it takes the people laid off to be rehired, and what that does to spending.
What it tests: The price of money under every financing line in the plan.
Source: FRED, Federal Reserve Bank of St. Louis · window opens Sep 1 or the earliest reading on file · latest Oct 20 · bp = basis points
Some of those moves are small. That is the point. An annual plan doesn’t break in one dramatic week. It drifts, line by line, while nobody is assigned to notice. By the time the variance shows up in a quarterly review, the decision it should have changed is three months old.
The annual plan isn't wrong. It's late.
The yearly plan made sense when gathering the evidence and running the scenarios took a team six weeks. You did it once because you could only afford to do it once. AI collapsed that cost. A scenario that used to take a quarter now takes an afternoon, and the organizations that notice are quietly replacing the event with a discipline.
That discipline is predictive planning: a standing loop that Scans for signals, turns them into a small set of Stories about how the year could go, Stakes the bets each story would justify, and Steers by re-arguing the plan when the evidence moves. Scan, Story, Stake, Steer. It runs every week, not every September.
You don’t have to cancel this year’s planning cycle to start. You have to stop treating its output as finished. Three moves, all of them doable before the plan is approved:
Three moves for this planning season.
Run a Cycle Audit before the off-site.
Put two numbers side by side: how long your planning cycle takes, and how often the things it depends on move. If the plan takes ten weeks to build and the inputs above move every week, you are planning against a picture that is already gone. The Maturity Read gives you the honest version in six minutes.
Give every assumption an expiry date.
Write down the five assumptions the 2027 plan can’t survive without: rates, demand, input costs, hiring, financing. Next to each, name the signal that would tell you it broke, and the date it has to be argued again. That is the 18-Month Sunset applied to a budget. An assumption nobody owns is the first to rot.
Book the Steer meeting now, not in April.
Put a monthly Convergence Review on the calendar before the plan is approved: one hour where you check whether separate signals are starting to point at the same future. The annual plan isn’t wrong. It’s late. A standing review is how it catches up. The whole cycle is laid out in Woodring’s Loop.
Get the read on everything that moved between September and December.
When planning season closes, we’ll send one email: every signal above, start to finish, and the assumptions a plan locked in September would already be carrying wrong. You’ll also get the essays on the discipline, roughly weekly. Unsubscribe in one click.
The full discipline, in one book.
Predictive Planning: How AI and Scenario Planning Make Strategy Continuous lays out the whole method: why the annual cycle broke, what AI actually changed, and how to install Woodring’s Loop in an organization that still runs on a yearly budget. Foreword by Thomas J. Chermack, who wrote the standard text on scenario planning.