Passing work to someone else.
WHEN THEY ARE NEEDED
Leaving a role Going on leave Transferring a project Ending an engagement
WHAT THEY SHOULD CONTAIN
What the work is Its current state What is in progress What is blocked, and on whom Commitments made, and to whom Who the relevant people are Where everything lives What is likely to go wrong
WHY COMMITMENTS MATTER MOST
Broken promises nobody knew about damage most.
WHAT TO INCLUDE ABOUT ACCESS
What systems are involved, and how access is obtained.
WHY NOT CREDENTIALS
They should be issued, not transferred.
WHAT TO INCLUDE ABOUT PEOPLE
Who to ask about what.
WHY
It is the information that is never written and always needed.
WHAT TO INCLUDE ABOUT HISTORY
Decisions taken and why, particularly unusual ones.
WHY
The successor will otherwise reverse them, and rediscover why.
WHAT TO WRITE BEFORE LEAVE
A shorter version: what is running, what may need attention, who to contact.
WHAT TO DO AFTER WRITING IT
Walk someone through it.
WHY
It exposes what you assumed.
WHAT TO AVOID
Writing it on the last day Assuming the obvious is obvious
WHAT TO LEAVE BEHIND
Something someone else can actually use.
