You take three days off.
By midmorning on the first day, your phone already has several messages. Someone cannot find the latest file. A supervisor wants to know what to do with an unusual customer request. Another person is waiting for your approval. Someone else asks what you told the client during the meeting last week.
You answer because most of the questions are easy. You know where the file is. You remember the conversation. You can make the decision in thirty seconds. Opening the laptop feels easier than letting someone spend an hour figuring it out.
There is something satisfying about being this useful. People call because you know. They wait because your judgment matters. You can solve in minutes what might take someone else much longer.
People may even tell you that you are indispensable.
That sounds like praise.
It may not be entirely good news.
Some of what makes you indispensable may be genuine expertise. You may hold authority others do not have. You may understand relationships, risks, history, and consequences that took years to learn.
But some of your indispensability may simply be information that never left your head, decisions nobody else was allowed to practice, or responsibilities that kept returning to you because answering was always faster than developing someone else.
Being needed is not the same as leaving something useful behind.
Bring legacy closer
Legacy is usually pushed toward the end of life.
We ask what people will remember about us, what will remain after we retire, whether we built something that will outlive us. Those can be meaningful questions, but their distance makes them easy to admire and easy to postpone.
You probably do not need to decide today what people will say about you forty years from now.
But there is a much closer question you can answer.
What could be more capable thirty days from now because of the way you work today?
Perhaps one employee could make a decision that currently comes back to you. Perhaps the team could run one important meeting without waiting for you to lead it. Perhaps somebody else could protect a customer relationship because enough of its history and judgment has been shared. Perhaps a recurring question could finally disappear from your inbox.
None of these accomplishments will put your name on a building.
They may still say more about the usefulness of your work than a monument ever could.
Ask what should no longer require you
The goal is not to make yourself unnecessary.
Some things should depend on you. A decision may legitimately belong to your role. A complicated problem may require expertise nobody else currently possesses. A customer may need the authority only you can exercise.
Removing yourself from those situations would not be legacy. It might simply be neglect.
The better question is narrower:
What should no longer require your presence?
Finding the correct template probably should not depend on you.
Remembering what the customer already approved probably should not live only in your memory.
A routine judgment that one of your supervisors is capable of learning probably should not return to you forever simply because it is faster for you to answer.
This distinction matters. You should remain important where your contribution is genuinely needed. But if everything continues to depend on your presence, your expertise may be growing while the capability around you remains still.
Look at what comes back
Pay attention to the work that keeps returning whenever you step away.
Not everything that comes back is a problem. But repeated dependence leaves clues.
“Only you know how to do this.”
“We decided to wait until you came back.”
“I wasn’t sure what you would want.”
“Can you just tell me what to do?”
Those sentences can feel flattering because they confirm that your experience matters. Yet they can also reveal places where useful judgment has become trapped.
The issue is not that people need you.
The issue is whether they still need you for something they could reasonably learn to carry.
That is where a thirty-day legacy project can begin.
Choose one thing
Do not build a succession plan for your entire life.
Choose one dependency.
Maybe every unusual customer request reaches you even though most follow a pattern one of your supervisors could learn. Maybe your colleague can prepare the entire proposal but still waits for you to write the recommendation. Maybe the weekly meeting loses direction unless you ask every important question yourself.
Choose something important enough to matter and small enough that you can genuinely change the dependency in thirty days.
Then ask what the next person actually needs.
They may need a decision rule. They may need access they do not yet have. They may need to watch you think through one real situation instead of hearing another explanation. They may need permission to make a decision they have already become capable of making.
Sometimes what they need most is simply to hear:
“You can decide this. You do not need to wait for me.”
That can be a surprisingly difficult sentence for both of you.
Helping can preserve dependence
Suppose someone brings you a problem you have solved dozens of times.
“What should I do?”
You know the answer immediately. Giving it takes ten seconds. The person leaves relieved, the problem moves, and you have been helpful.
There is nothing wrong with that when the situation is urgent, the risk is high, or the person is not yet ready to carry the decision.
But if you make the same move every time, the same question will probably return.
Sometimes the useful response takes longer.
You ask what they think is happening. You ask what options they see. You ask what consequence matters most and what they would choose if you were not available.
Now they hesitate. The conversation becomes slower. They may not give the answer you would have given.
That discomfort is part of why capable people keep rescuing others. Rescue produces immediate relief. Development often produces temporary friction before it creates independence.
If you are trying to leave something useful behind, you may have to tolerate a little less efficiency today so someone else can carry more tomorrow.
Pass judgment, not only answers
In Make Your Work Easy for Others to Build Upon, we looked at the difference between giving someone an answer they can repeat and helping them understand enough of the reasoning to create the next answer.
That distinction becomes especially important when you are trying to reduce dependence.
Suppose your team constantly asks whether they may grant a particular kind of customer exception. You could create a list of approved and prohibited cases. That might remove some questions, and sometimes that is exactly what is needed.
But if the situations vary, eventually the list will fail.
The person does not only need to know what you decided last time. They need to understand what you were trying to protect when you made the decision.
Perhaps your judgment is:
“We can make an exception when it genuinely solves the customer’s problem without creating a promise we could not reasonably repeat for others.”
That sentence cannot replace experience. It cannot transfer every judgment you possess.
But it gives the next person something to think with.
Legacy is not getting people to reproduce your answers forever.
It is helping them develop enough judgment that they will eventually face situations for which you never gave them an answer.
Give them reality
Explanation alone will not do this.
If you want someone to lead the meeting, eventually they have to lead one. If you want a supervisor to handle a difficult customer decision, they need a real decision whose risk is appropriate to what they can currently carry. If you want somebody else to protect an important relationship, they need to enter the relationship, not merely read your notes about it.
Capability develops when judgment meets reality.
This is where the thirty-day frame becomes useful. You are not trying to solve succession for the next decade. You are trying to create enough real repetitions for one piece of work to begin moving differently.
Thirty days from now, something that currently comes back to you should be able to move without your intervention.
That gives you something real to observe.
Their version may look different
Then comes another difficulty.
You teach someone how you handle the work.
They begin handling it.
And they do it differently.
The supervisor asks a different question than you would have asked. The facilitator opens the meeting differently. The colleague uses language with the client that is not your language.
Your instinct may be to reclaim the work.
Sometimes you should intervene. A standard is being weakened. A serious risk is being missed. The person is making a decision whose consequences exceed their current authority or capability.
But sometimes the difference is simply difference.
They are not becoming you.
That was never the point.
If the result is being protected and their judgment is becoming stronger, their own way of carrying the work deserves room to emerge.
A legacy that requires people to keep reproducing you is still centered on you.
A stronger one increases what other people are capable of becoming.
Legacy can be temporary and still matter
We also burden the word legacy by demanding permanence from it.
We imagine that whatever we leave must last.
But useful things change.
The process you improve today may be replaced by better technology in three years. The meeting practice you teach may evolve. The person you coach may forget your exact words and still become a better leader because of what they learned while working with you.
That does not diminish the contribution.
Legacy does not have to last forever to have lasted beyond you.
Something can matter because it carried another person far enough to make their next useful move.
That is enough.
Make thirty days visible
Choose the one dependency you want to change and complete this sentence:
Thirty days from now, ______ should be able to ______ without needing me to ______.
Thirty days from now, Paolo should be able to approve routine customer adjustments without needing me to review every case.
Thirty days from now, the team should be able to run the Monday huddle without needing me to facilitate it.
Thirty days from now, Ana should be able to brief the client without needing me to reconstruct the project’s history for her.
Once the sentence is clear, the work between now and then becomes easier to see.
What access has to be given?
What judgment needs to be exposed?
What real situation can the person handle?
Where should you remain available?
Where should you deliberately stop stepping in?
Then let the next thirty days answer the question.
Perhaps the dependency disappears. Perhaps the person needs more repetitions. Perhaps you discover that the responsibility genuinely belongs with you for now.
The goal is not independence for its own sake.
The goal is to make dependence intentional rather than automatic.
The question has changed
At the beginning of Make Your Work Matter, a full day could feel like evidence.
You were busy. You finished things. People needed you. You carried a great deal.
All of that can be true.
But contribution asks for something more.
Who was better served because you worked?
What moved?
What became easier?
What can another person use now?
What recurring confusion disappeared?
What judgment travelled?
What can someone do today that once required you?
These questions do not make your effort smaller. They reveal what your effort produced.
And by the time we reach this final article, perhaps the question is no longer only whether your work created value while you were doing it.
It is whether some of that value can continue moving after your direct effort withdraws.
A person becomes more capable.
A system becomes easier to use.
A decision becomes clearer.
A standard becomes strong enough for others to protect.
An idea becomes something another person can build upon.
The work travels.
You do not need your name attached to every part of that movement for it to count.
You do not need a monument.
You need a trail.
So do not begin your legacy with the distant question, What will people remember about me someday?
Begin with something much closer.
What moved because I was here?
And then:
What can keep moving without me?
That is enough legacy to work on in the next thirty days.
And it may be one of the clearest proofs that your work mattered.
Continue with Make Your Work Matter to return to the pillar and the larger question of turning effort into contribution.