Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why does our forecast keep breaking when reality moves?

You and your team built this model together, defended it together, and now reality has moved past it. Somewhere in the group there's a quiet argument about whose assumptions failed. That is not a math problem. It is a design problem — you built a forecast to be correct, when you should have built it to be corrected. A model that can never be wrong is not a model. It is a guess wearing a spreadsheet. The work was never to predict the future once and defend it forever. The work is to keep adjusting, together, faster than the world changes. If your pod spends more time protecting last quarter's numbers than updating this quarter's view, you have confused the forecast with your reputation. So stop asking which assumption to trust. Start asking what new information you will act on this week, and who on your team owns bringing it to the table.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The core mistake is a wrong idea of what a forecast is for, but fixing it takes the team practicing new habits together, so guidance carries more weight.
How the two dials adapt to you →
What’s really going on

Your model breaks because you built it to be right once, not useful again and again. A forecast is a tool you pick up, use, and correct — not a monument you defend. Stop arguing about whose assumption failed. Choose what your team will update this week, together.

🔒 What you’ll build togetherUnlock by starting
A moveBefore your next forecast review, each person writes down what evidence would make them drop their own assumption. If no one can name it, you built an idol, not a model.
A moveRotate one teammate each cycle to argue against the forecast. Change the person so no one's ego gets glued to the number.
A moveIn your retro, replace 'were we right' with 'what did we learn in time to use it.' Ask it out loud, every time.
A movePick a fixed, short interval to revise the model, no matter what. Do not wait for it to be proven wrong first.
A moveWhen the forecast misses, name the one update you'll make before the meeting ends. Do not let it dissolve into blame.
PractiseThe Standing Correction · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team argues less about who was right and more about what to do next.
  • Forecasts get revised on a schedule, not just after a visible failure.
  • The pod treats being wrong early as useful, not as something to hide from each other.
  • Decisions move faster because the model is used as a tool, not guarded like a verdict.

Related problems

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.