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

Our numbers are tight. Why do surprises still hit us?

You built the dashboard. Runway, burn, next move — all mapped, all current. Your pod trusts the numbers because the numbers have earned trust. This is real work. Most teams never get this far. But notice what the model cannot see. The customer who goes quiet. The hire who checks out. The vendor who shifts terms without a call. Your spreadsheet updates monthly. The business breaks on a Tuesday. By the time the model catches up, your team has already made three decisions on old information and called it diligence. The fix is not a sharper model. It is a discipline you and your team keep together, on a schedule, whether or not anything looks wrong. Distrust the map before it fails you, not after. Ask who touched reality this week, and what they saw that the numbers haven't shown yet.

◆ 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 team already has the financial skill; what they lack is a shared habit of checking the model against the ground, which is coached behavior more than taught knowledge.
How the two dials adapt to you →
What’s really going on

Your spreadsheet is not the business. It's a map you drew from last month's facts, and the ground has already moved. Your real job isn't refining the model more. It's building a habit — with your team — of checking the model against the floor every week, and acting before the gap becomes a crisis.

🔒 What you’ll build togetherUnlock by starting
A moveRun a weekly 15-minute ground check: each person reports one fact from this week that isn't in the model yet.
A moveBefore you present the burn number, ask the team what has changed since the last update.
A moveName one assumption that, if wrong, breaks the whole runway calculation. Assign someone to test it this week.
A moveWhen the model and the floor disagree, trust the floor. Update the model, not your memory of it.
A moveStop presenting runway as one clean number. Present it as a range, and name what moves it.
PractiseGround Check · a Pod of 5 · 20 min

What changes unlock by starting

  • Your pod catches drift before it becomes a crisis, not after.
  • You stop mistaking a current model for a safe position.
  • Decisions get made on this week's reality, not last month's spreadsheet.
  • Your team builds a shared habit of checking the map against the ground.
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.