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

How Do We Actually Build a Legacy, Not Just Think About One?

You and your team bring up legacy sometimes. Maybe after a big win. Maybe late at night, when the work feels small. Then the talk fades. Nothing changes. This is not a lack of ambition. It is a lack of a next step. Legacy is not a feeling. It is not a vision statement on a wall. It is the sum of specific choices — what you built, what you taught, what you left stronger than you found it. No one inherits a feeling. They inherit a system, a habit, a finished piece of work. Working with others does not make this harder. It makes it possible. You do not have to carry it alone. Agree on one thing worth leaving behind. Then do it this week — not someday.

◆ 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 confusion is partly conceptual — people don't know what legacy actually is — but the real work is choosing and doing, so guidance leads.
How the two dials adapt to you →
What’s really going on

Legacy is not a feeling you wait for. It is what you and your team leave behind that others can use. Stop asking what you'll be remembered for. Ask what you finished this week that someone else could build on. That is the whole of it.

🔒 What you’ll build togetherUnlock by starting
A movePick one piece of current work. Ask: could someone else pick this up without you? If not, redesign it now.
A moveHold a 30-minute meeting where each person names one thing they want to still matter in five years. Write it down.
A moveChoose one system or habit to hand off this month. Document it well enough that it outlives your involvement.
A moveBan the word 'legacy' from meetings until someone can name the specific action behind it.
A moveOnce a month, review your team's work together: which parts built something lasting, which just filled time?
PractiseThe Inheritance Audit · a Pod of 4 · 30 min

What changes unlock by starting

  • A shared, specific definition of what you're building toward — a thing, not a feeling.
  • At least one piece of work or system documented so others can carry it forward.
  • A team habit of asking 'will this outlast us?' before starting new work.
  • Less talk about legacy, more proof of it in what you actually finish.
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.