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

Why does our plan fall apart once things change?

You started well. Everyone agreed on the plan, the roles, the steps. Then something shifted — a person left, a deadline moved, a client changed their mind — and no one knew whose job it was to say so out loud. This is not confusion. It is the absence of a practice. Starting a plan and keeping a plan alive are two different skills, and most teams only ever train the first one. You wrote the plan once and expected it to run itself. With others involved, this gets worse, not better. Each person assumes someone else is watching for change. No one is. Fix the practice, not the plan, and the confusion goes away.

◆ 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 insight — that starting and sustaining are different skills — needs to be taught once, but the fix is almost entirely a matter of building and repeating a review habit with the team.
How the two dials adapt to you →
What’s really going on

The plan did not fail — your habit of tending it did. Starting takes one decision; staying with it takes many small ones. Choose a fixed day to look at it again, name who owns each change, and treat updates as part of the work, not proof it broke.

🔒 What you’ll build togetherUnlock by starting
A movePut a recurring review date on the calendar right now, before you need it.
A moveName one person who owns updates — not 'the team,' one name.
A moveDecide in advance what would count as a sign the plan needs to change.
A moveWhen something shifts, write one line: what changed, and why.
A moveReview the plan out loud together on schedule, not only when it breaks.
PractiseThe Update Meeting · a Pod of 4 · 30 min

What changes unlock by starting

  • Change stops feeling like failure and starts feeling like maintenance.
  • Someone always knows who is responsible for updating what.
  • Meetings about the plan get shorter, because drift gets caught early.
  • Your team can point to the moment things changed instead of guessing.
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.