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.
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 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.