What is a leadership legacy statement?
Your legacy isn’t what you say at your leaving do; it’s what your calendar said every week before it.
Jay Sampat, Chief Mirror Holder · Drafted with AI · coach review pending · Updated · 9 min read
The short answer
A leadership legacy statement is a short paragraph, in your own plain words, about the mark you want to leave: what you built, how people felt working for you, what changed because you were there and what your successor inherits. Its real use is as a test. You hold last week up against it and see where they differ.
At some point in a senior role, someone asks you a version of the question. A board member at dinner. A coach. Your own head at two in the morning. What do you want to be remembered for here?
Most leaders have an answer ready, and it usually sounds good. Grew the business. Built a great team. Left the place better than I found it. The trouble is that almost everyone in your seat would say the same, and none of it tells you what to do on Monday.
A leadership legacy statement is a way to turn that answer into something you can use. This post covers what one is, how to write yours, what a draft looks like, and how to check it against the week you actually had.
What is a leadership legacy statement?
It’s a short paragraph, in your own plain words, about the mark you want to leave as a leader. It covers what you built, how people felt working for you, what changed because you were there, and what the person after you inherits.
Kimberly Wade-Benzoni at Duke, who studies legacy, defines it in a Fuqua Insights podcast as “an enduring impact attached to one’s identity” that lasts after you have left the place where you made it. That last part matters. A legacy isn’t what you achieved while you were in the room. It’s what is still there after you walk out.
So a legacy statement isn’t a list of results. Results get reported, then replaced by next year’s results. A legacy statement is about what outlasts the results: the people you grew, the habits the team kept, the way decisions get made when you’re not there.
Why bother writing one down?
Because thinking about legacy changes how people work, and writing it down makes it specific enough to act on.
In the same podcast, Duke reports that when people reflect on the legacy they want to leave, their work feels “more meaningful”. They are also more satisfied in their jobs and more likely to help others. Wade-Benzoni’s advice to leaders is to be intentional, thinking about the impact you want and “how your current actions align with that vision.”
There is a second reason that matters more at the top. Your successor will live with your choices. Duke research published in the Journal of Experimental Social Psychology, and summarised in a Fuqua Insights article, found that even after a predecessor had acted selfishly, participants prompted to consider their legacy were “more generous toward their successor than those who were not.” Thinking about what you leave behind makes you kinder to whoever picks it up.
Writing it down adds one more thing: honesty. A legacy in your head can stay vague and flattering forever. A paragraph on a page can be checked.
What goes into a good leadership legacy statement?
Four parts, each one a sentence or two. Together they cover the main things people remember about a leader after the leader has gone.
- What you built. Not the revenue line. The thing that would still work if you left tomorrow: a team, a way of working, a capability the company didn’t have before.
- How people felt working for you. This is the part people remember longest. Trusted? Stretched? Safe to disagree? Pick the feeling you’d want a former direct report to describe to a friend.
- What you changed. The thing that is different because you were there. A habit you broke, a standard you raised, a problem that stopped coming back.
- What your successor inherits. The team, the decisions, the open problems. Would they thank you for it, or spend their first year cleaning up?
Then there is a fifth line, which isn’t part of the statement itself but is what makes it useful: what last week said instead. If someone had watched only your last five working days, what would they say you were building?
How do you write a leadership legacy statement?
Answer each part in a sentence, as if a person who worked for you were saying it. Then join them up and read it out loud. If it sounds like a corporate values poster, make it more specific.
A few rules help.
Write in the third person, from someone else’s mouth. “She grew leaders” is easier to test than “I want to grow leaders”, because it asks whether anyone would actually say it.
Use things you could see. “People felt empowered” is hard to check. “People made calls without waiting for her” is easy to check.
Keep it short. One paragraph. If you need a page, you’re writing a strategy, not a legacy.
Leave the numbers out. Numbers belong in the plan. The legacy is what made the numbers possible, and what keeps making them after you go.
Don’t write the version you’d say at your leaving do. Write the version you’d want to overhear in the kitchen a year after you’ve gone.
What does a draft legacy statement look like?
Here’s a hypothetical example. A chief operating officer at a mid-sized company has been in the role for three years. She answers the four parts like this.
- What I want people to say I built: “A leadership team that runs the place without her in the room.”
- How I want people to have felt working for me: “Trusted with real decisions, and told the truth early.”
- What I want to have changed: “Problems got raised in the week they started, not the quarter they blew up.”
- What I’d want my successor to inherit: “Three people ready to step in, and no decision that only she understood.”
Joined up, her draft reads:
“She built a leadership team that runs the place without her in the room. People who worked for her felt trusted with real decisions and were told the truth early. Because she was there, problems got raised in the week they started, not the quarter they blew up. Whoever comes next inherits three people ready to step in, and no decision that only she understood.”
It’s plain. It’s hers. And every line can be checked.
Then she answers the fifth question: what did last week say instead? She looks back honestly. She chaired four meetings that her team could have run. She made two decisions on the spot that her direct reports had brought her half-formed, rather than sending them back with a question. She heard about a supplier problem in a corridor, three weeks after it started. And she spent no time at all with the two people she thinks could replace her.
None of that is a failure. It was a busy week, and she got a lot done. But if someone wrote a legacy statement based only on that week, it would say: “She was the person who made the decisions.” That is close to the opposite of what she wrote.
That gap is the point of the exercise. The statement isn’t a grade. It’s a mirror held up next to a calendar.
How do you know if your week matches your legacy?
Look at your calendar, not your intentions. Your week is the most honest record of what you’re building, because it shows where your time actually went.
Elisabeth Hayes puts the question simply in Harvard Business Review: “How do you want to be remembered?” Her article is called The Small Actions That Become Your Legacy, and for a senior leader, most of those small actions live in the calendar.
Take each line of your statement and ask what it would look like in an ordinary week.
- If you want to have built a team that runs without you, how many meetings did you chair that someone else could have run?
- If you want people to feel trusted, how many decisions did you take back or redo?
- If you want to have changed how problems surface, how did you hear about the last one, and how late?
- If you want your successor to inherit people ready to step up, how many hours did you spend with them, on their growth rather than their projects?
You don’t need perfect numbers. Rough counts are enough to show whether the week leans towards the statement or away from it. If you want a more structured look at where your hours go, Calendar Audit does exactly that.
What is the one move that makes the statement real?
Open next week’s calendar and change one thing in it so that it matches one line of your statement. Not five things. One.
This is where most legacy exercises die. People write something moving, feel good about it, and file it. The statement only does any work when it changes a specific hour.
For the chief operating officer in the example, the move might be handing the Thursday operations review to one of her direct reports and sitting in the back, saying nothing until the end. That single change touches three lines of her statement at once: it builds the team, it shows trust, and it gives a possible successor a visible stretch.
For you it might be:
- moving a status meeting so you can spend that hour with someone you see as a future successor;
- cancelling a decision meeting and asking the owner to decide and tell you;
- booking a short conversation you’ve been putting off, so a problem gets raised this week rather than next quarter.
Then do the same next week. A legacy is built in Tuesdays, not in farewell speeches.
Is a legacy statement the same as a succession plan?
No, but they are close relatives. A succession plan names who could take over and what they need. A legacy statement says what you want them to take over: the culture, the habits, the unfinished work.
You need both. A succession plan without a legacy statement can hand over a role and nothing else. A legacy statement without a succession plan is a wish. If your statement says your successor will inherit people who are ready, Succession Ready helps you check whether that’s true today. And if you suspect the business still runs mostly through you, the post on how to make your business run without you is a good next read.
Where should you start?
With the five questions, answered honestly, in about five minutes. That’s what The Legacy Question is for.
It asks you the five prompts in this post: what you want people to say you built, how you want people to have felt working for you, what you want to have changed, what you’d want your successor to inherit, and what last week said instead. You type your answers in your own words. It then puts them together into a one-paragraph legacy statement using a fixed template, much like the example above, with last week’s answer set alongside it so you can see the gap.
It’s free, there’s no sign-up, and it takes about 5 minutes. Your words stay in your browser. There’s no AI writing anything for you and nothing is sent anywhere, so what you get back is your own thinking, arranged. It doesn’t score you or tell you whether your legacy is good enough. It gives you one move: take the statement to next week’s calendar and change one thing.
If you want a wider view of the habits behind your legacy, such as whether you hand people work they’re not quite ready for and back them while they learn, try The 42 Test. You’ll find the other tools for leaders at the top on the CXOs page.
Your legacy is being written either way. The only question is whether you write the first draft, or your calendar does.
Write the five sentences, then open next week’s calendar. Tell me which meeting you moved.
Jay
Key takeaways
- A legacy statement is not a speech for your leaving do. It’s a test you can run on any ordinary week.
- Write it in four parts: what you built, how people felt, what changed and what your successor inherits.
- Plain and specific beats grand. If a line could sit on anyone’s LinkedIn profile, it isn’t yours yet.
- The useful part is the gap between the statement and what last week actually said about you.
- Close the gap one calendar entry at a time, starting next week.
Questions people also ask
- What is the difference between a legacy statement and a personal mission statement?
- A mission statement says what you’re trying to do now. A legacy statement looks back from the day you leave and says what stayed behind: the people, the habits and the results that outlast you. The second is easier to check against your week, because it names effects, not intentions.
- How long should a leadership legacy statement be?
- One paragraph, around four or five sentences. Long enough to cover what you built, how people felt, what changed and what you hand on. Short enough to read before you plan your week.
- Should I share my legacy statement with my team?
- You don’t have to, and many leaders keep it private at first. If you do share it, share it as something you’re working towards, and ask people where they see the gap. That turns it into a conversation rather than a claim.
- How often should I rewrite my legacy statement?
- Read it weekly, rewrite it rarely. A change of role, a big change in the business or a successor being named are good reasons to revisit it. If you find yourself rewriting it every month, it may be describing your current priorities rather than your legacy.
- Is it too early to think about legacy if I’m new to the top job?
- No. It’s easier at the start, because your habits aren’t set yet and people are still forming their view of you. Waiting until the last year means writing about a legacy you mostly can’t change.
Sources
Keep reading