Talk it through with Aurelius
LibraryAureliusThe problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can I plan but fall apart when reality disagrees?

You built a plan. It was clean, logical, and it satisfied you. Then a customer said no, a number came in wrong, a partner backed out — and you call this 'reality hitting,' as if you were ambushed. You were not ambushed. This was always going to happen. A plan is a guess about tomorrow, made with today's incomplete knowledge. That it needs changing is not the emergency. It is the schedule. The real trouble is not the changed facts. It is that somewhere along the way, you and your team stopped treating the plan as a tool and started treating it as an identity. To change it now feels like losing an argument, or admitting the group was foolish. So you defend it a week too long, and reality punishes the delay. You cannot control the market, the customer, or the timing. You can control how quickly your team names what has changed, and how little shame you attach to changing course. That is the whole skill. Practice it like a muscle, not a crisis.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The core insight is simple to state, so most of the value is in building the team habits that make revision routine rather than painful.
How the two dials adapt to you →
What’s really going on

The plan never failed. Reality did what reality always does. What defeats you is treating the plan as a fact rather than a guess you agreed to test. Choose to revise on schedule, not on ego. Your team's job is not to be right — it is to notice fast and change together.

🔒 What you’ll build togetherUnlock by starting
A moveSet a weekly meeting with one agenda item only: what did reality tell us that the plan did not predict.
A moveEach week, assign one person the job of arguing against the current plan, out loud, in front of the group.
A moveWrite down the plan's assumptions separately from the plan itself. When an assumption is proven false, change the plan that day — not when it's convenient.
A moveWhen anyone resists a needed change, ask them directly what they are actually protecting — the business, or their own certainty.
A moveAfter every revision, say plainly what you got wrong and move on. Do not apologize for it. A plan that never changes was never tested.
PractiseAssumption Autopsy · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team notices contradicting evidence in days, not months.
  • Changing the plan stops feeling like failure and starts feeling like maintenance.
  • Fewer arguments about whose fault the wrong assumption was.
  • The group moves as one when the plan shifts, instead of splitting into who was right.
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.