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

Why does our case plan fall apart the moment we're surprised?

You and your team built the case carefully — theory, timeline, witnesses, exhibits. Then a witness recants, or opposing counsel produces something you never saw coming, and the whole thing feels like it's built on sand. Everyone starts doubting not just the plan, but each other. Here is what you're missing: the plan was always going to be wrong somewhere. That was true the day you wrote it. You didn't fail by being surprised. You failed only if surprise stops you from choosing the next right action. A pod that treats the plan as sacred will panic when it cracks. A pod that treats judgment as the real asset — the plan just being judgment's current best guess — will absorb the hit and keep moving. That is the whole difference, and it is a choice your team can make before the next surprise arrives.

◆ 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 failure is emotional and behavioral under pressure, not a knowledge gap, so most of the value is in coaching the team's response, not teaching them new facts.
How the two dials adapt to you →
What’s really going on

The plan was never the strategy. The strategy is the judgment behind the plan — and judgment doesn't break when facts change. Only the plan does. When the case surprises you, stop grieving the plan and ask what your judgment says now, together, with the new facts in hand.

🔒 What you’ll build togetherUnlock by starting
A moveBefore the case starts, list the plan's three biggest assumptions out loud as a team — name what has to be true for the plan to hold.
A moveWhen a surprise hits, call a 20-minute stop before anyone reacts. No filing, no calls, until the team has named what's actually true now.
A moveSeparate the shock from the decision. Let one person voice the frustration, then move the conversation to: what can we control in the next 24 hours.
A moveAssign one person per surprise to ask the room: 'Is this a plan problem or a strategy problem?' Most surprises are the former.
A moveAfter every surprise, however small, spend ten minutes as a pod naming what you'd do differently next time — before you're back in the fire.
PractiseAssumption Audit · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team stops treating surprises as emergencies and starts treating them as data
  • Recovery time after a curveball shrinks because you already have a stop-and-reassess habit
  • You can tell the difference between an assumption that broke and a strategy that failed
  • Less blame circulating after setbacks, more shared adjustment
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.