Stop Extrapolating: How to Plan When Disruption Moves Faster Than Your Roadmap

Here is the quiet lie in planning: that the future looks like the present, only more so. You draw a line from last quarter, stretch it out five years, and call it strategy. That worked when markets moved slow. They do not move slow anymore. The old horizon models assumed disruption crawled in over 36 to 72 months. Now it lands in one. So leaders keep building careful plans for a world that stopped behaving.

The fix is not a better forecast. It is a different set of tools: ways to see the system you sit in, spot change early, and keep adjusting as you go. Here is how to plan past the next quarter without pretending you can see the whole road.

The deep cut

• The future is not the present extended. Geert Claes argues the 3 Horizons model broke because disruption now outruns its 36 to 72 month windows.
• A rigid five-year plan rots in place. Sundar Subramanian warns that linear plans set generic goals and get rarely rethought while the market moves.
• Model the system, then keep adjusting. Leyla Acaroglu's Interconnected Circles Map and Netflix's reinforcing loops both treat strategy as something you tune, not set.

Why the old horizon math stopped working

The 3 Horizons model told you to run today's business, build tomorrow's, and seed the far-off third. Nice idea. The problem is timing. Geert Claes makes the case that the model is dated because disruption now arrives far faster than the windows it was built around. When horizon three shows up in 18 months, planning it as a distant bet means you miss it.

That does not mean throw out horizon thinking entirely. Bill Sharpe's framing still asks good questions: what needs to fade out, what should you nurture for the future you want. Keep the questions. Drop the assumption that the clock ticks slow.

Spot the change before it is obvious

If you cannot extrapolate, you have to watch. Anna Roumiantseva's blend of design and futures thinking leans on fringe-spotting: looking at the edges of your market for the odd signals that hint at where things go next. The weird startup, the behavior that seems niche, the regulation nobody reads yet. Those are your early warnings.

Pair that with a hard look at your own assumptions. Ask which beliefs that hold today will break in ten years. Most teams never write these down, so they never notice when one quietly stops being true. Make the list. Revisit it. Treat a broken assumption as a signal to move, not a surprise to absorb.

Map the system you actually sit in

When a problem feels tangled, you need to see how the pieces connect before you act. Leyla Acaroglu's systems-mapping tools are a hands-on way to do this. Her Interconnected Circles Map pushes you to draw the relationships between parts of your system, then find the leverage points and the gaps nobody is covering.

This is analog and cheap. You and your team, a wall, some markers. The point is to stop arguing about one feature and start seeing the web it lives in. Where does one change ripple? Which relationship are you missing today? A map surfaces the questions a roadmap hides.

Build a flywheel, not a five-year plan

The better model is a loop you keep tuning. Sundar Subramanian describes strategic flywheels: reinforcing feedback loops where each win feeds the next. Netflix ran three of them. Better personalization pulled in more customers, which made more data, which made personalization better again. Same shape as Amazon's napkin diagram, where lower prices and more sellers reinforce each other.

The method is three moves. Sense the market and run cheap experiments with a clear range of possible outcomes. Build loops that pay off more as disruption takes off, and kill the bets that do not. Then scale the few capabilities that make your loop turn. Geoff McGrath's point fits here: data-driven design earns lasting advantage only when it feeds real strategy. The data is the fuel. The loop is the engine.

Three questions for your team

• Which assumptions behind our current roadmap would break if a competitor's "horizon three" bet arrived in 18 months instead of five years? Write them down, then decide which one you move on first.
• Where are the leverage points and the missing relationships in our system? Map it on a wall before the next planning cycle, not after.
• Which of our wins reinforce each other, and where is that loop leaking? Name one flywheel to strengthen this quarter and one bet to kill.