Handing Over
the best-case scenario
- You have decided to leave a project that you founded or currently lead
- The project is continuing after your departure
- You have time to prepare a graceful transition
Before
- Be sure you mean it
- Letting go will be hard on you but not letting go will be even harder on your successors
- So be sure you actually mean it
- Do it when others think it's time
- You will often be the last person to realize that you ought to be moving on
- So ask people and pay attention to what they say
- Which means you need to know people who will tell you the truth
- Explain what, when, and why
- Tell people you're leaving as soon as you're sure
- Prevents rumors, gossip, and speculation
- Don't pick a successor by yourself
- You will probably have strong opinions about who should succeed you
- But you are not objective
- And what the project needs now is probably different from what it used to need
- Involving others in the planning also builds community
During
- Write a succession plan
- Final state: what is your successor actually responsible for?
- Transition: what are you handing over to them when?
- First draft on your own, final draft with your successor
- Hand over gradually if you can
- Start sharing tasks with your successor a few weeks before you leave
- They will get to see how things actually work
- You'll discover things you would otherwise forget to tell them
- Go on holiday for a week and leave your successor temporarily in charge
- Have some fun before you go
- People remember beginnings and endings more than middles
- So don't just slog your way to the end and turn out the lights
- Instead, pick a small project you never quite got around to and do one final sprint
After
- When you leave, leave
- Tempting to continue to have a role in the organization
- But that is confusing because people are used to looking to you for answers
- Leave for something
- People who start things usually aren't good with idleness, and idleness tends not to be good for them
- So have your next project lined up, even if it's small
- Reflect on what you learned
- Write down what you learned and what you could have done differently
- Helps you move on
- Helps with the next thing you do
- Helps your successor and other people
- Celebrate the good things
- Many people only reflect on could-have-beens
- Write down what you accomplished as well
- It's just as important for your successors and the community as it is for you
The word "mistake" means "an action or judgment that was wrong". English doesn't have a single word that means "an action or judgment that was right", which says something about human nature in general or English speakers in particular.
Exercises
Before
- Who should be involved in picking your successor?
- Write a draft of the message you will send to your community and/or post on your project website announcing your departure, and review it with others in a small group.
During
- What have you done in the last week that your successor will be responsible for? Which of these are easiest for your successor to start with?
- What have you done in the last year that only needs to be done occasionally? Which of these can be practiced now, and which can only be done when the time comes?
- What is the most satisfying small thing you could do before you step away?
After
- Write down (at least) three things you think you accomplished while leading your project.
- Write down (at most) three things that you think you could have done better.
- What are three things you would like to do after you leave your project?