A leadership team I worked with finished its annual plan in late October. Eleven sessions, three offsites, a budget that finance had rebuilt twice. In the second week of November the company's largest competitor announced an acquisition that changed the pricing floor in two of the plan's three growth segments. The plan was five months in the making and eleven days old when it became a document about a market that no longer existed.
Nobody in that room had done anything wrong. They had done what the calendar asked. The problem is the calendar.
The cost of the long cycle is not the time
It is what the length forces you to assume. A five-month process needs its inputs frozen early, so the assumptions about competitors, pricing and demand are set in month one and defended for the next four. By the time the board sees the plan, the team is emotionally invested in assumptions that are already a season old. The longer the cycle, the harder it is to say "that changed" without it sounding like "we failed."
What compressing it actually buys
Not just speed. When the strategy takes eight to twelve weeks instead of five months, the assumptions are weeks old, not a season old, when the first market move lands. And because the work is built as a model — assumptions, choices, numbers, projects, in one language — a competitor move is a scenario you run against it, not a reason to start again. AI does the re-analysis in days. The leadership team decides what changes. The plan survives contact with November.
Monday
Take the current plan and mark the date each of its top five assumptions was last tested against live market data. If most of the dates are from the start of the planning cycle, the plan was old before it was approved. The fix is not a faster offsite. It is a strategy built to take a scenario.
