The handover problem: keeping context when people change roles
The handover problem: when people change roles, the reasons behind their work leave too. Here is what gets lost, a checklist, and how to fix it.
The handover problem is what happens when someone changes roles or leaves and the reasons behind their work leave with them. You fix it by capturing context continuously, not in a rushed handover doc in their last week: the decisions they made, why they made them, who they worked with, and the workflows they relied on.
Most handovers transfer tasks well enough. What gets lost is the "why." This post covers what goes missing, a handover checklist that works, and how to stop each handover from being an emergency.
What actually gets lost in a handover
When someone moves on, the open tickets and file access usually get handed over. The harder things to transfer are:
Decisions and their reasons. "We don't offer this customer monthly billing" is easy to pass on. "Because they churned twice on monthly and we agreed annual-only with their CFO" is not.
Relationships. Who to call at the customer, who in finance approves exceptions, which engineer knows the billing code.
Unwritten rules. The things everyone on the team "just knows," like never shipping on Fridays before a holiday.
Open loops. Promises made in calls or DMs that never reached a ticket.
Working methods. The saved prompts, templates and checklists that made this person effective, often sitting in a personal AI chat history.
The new owner gets the tasks without the context. So they either re-ask everything, re-decide things that were already settled, or make a call that contradicts an earlier agreement.
Why handover docs fail
The standard fix is a handover document written in the last week or two. It rarely works well, for predictable reasons:
It's written under time pressure. The person leaving is also finishing their own work.
People don't know what they know. Experts skip the context that feels obvious to them.
It's a snapshot. It's out of date the first time something changes.
Nobody reads it at the right moment. The new owner needs the reasoning three months later, when a question comes up, not on day one.
Atlassian reports that 25% of the workweek is spent searching for information. A bad handover makes that worse for the person who takes over, because the information they need may not exist anywhere.
The AI version of the handover problem
AI tools add a new layer. Many people now do part of their thinking in AI chats: drafting the pricing rationale, testing positioning, working through a customer issue. That reasoning stays in their personal chat history.
When they leave, the new owner can see the final doc but not the thinking behind it. If the person refined a prompt over months for a key workflow, that goes too, unless someone turned it into a shared skill.
A handover checklist that works
Use this when someone changes roles. It's better still as a quarterly habit.
Area | What to capture | Where it should live |
|---|---|---|
Decisions | What was decided, why, who agreed, date | Decision log |
Open commitments | Promises to customers or teams, with deadlines | Ticketing or project tool |
Relationships | Key contacts, what each one cares about | Account notes or CRM |
Unwritten rules | Team norms and exceptions | Team handbook page |
Workflows | Prompts, templates, checklists, how-tos | Shared skills or playbooks |
Known risks | Things likely to go wrong and early signs | Handover note, linked to the above |
Run a "why" interview
Thirty minutes, recorded or with notes. Go through the person's main areas and ask, for each one: what's the most important decision you made here, and why? What would you tell your replacement not to change? What would you change if you stayed?
Pair, then reverse
For a role change inside the company, have the new owner shadow for a week, then lead for a week with the previous owner watching. Questions come up naturally, and the answers can go straight into the right place.
Stop handovers from being emergencies
The real fix is to stop treating context capture as a leaving task. A few habits make handovers boring:
Log decisions when they're made. A short entry with the reason takes two minutes. See how to keep a decision log your team will actually use.
Write in shared places. Default to team channels and shared docs over DMs and personal notes for work decisions.
Share AI workflows early. If a prompt is critical to a role, it should be a team asset before anyone thinks about leaving.
Review ownership quarterly. For each important area, ask: if this person were out for a month, could someone else pick it up?
These habits also make onboarding new hires faster, because the context a new hire needs and the context a leaver takes with them are mostly the same.
A concrete example
A product manager who owns pricing moves to a new team. Without good habits, the new PM gets a doc listing current plans and prices. Two months later, sales asks for a discount for a large customer. The new PM approves it, not knowing that the previous PM had turned down the same request twice, on the grounds that it would set a precedent for a whole segment.
With good habits, the decision log has an entry: "No volume discounts for segment X. Reason: precedent risk. Agreed by head of sales and CEO." The new PM sees it, and the conversation starts from the right place.
FAQ
How long before someone leaves should a handover start?
The formal part should start as soon as the change is known. But the useful part, capturing decisions and workflows, should already be happening as normal work. Then the handover is a review, not a rescue.
Who is responsible for the handover?
The person leaving owns capturing what they know. Their manager owns making sure it lands somewhere the new owner and the team can find it later.
Can AI help with handovers?
Yes, for summarizing and organizing. An AI tool can turn meeting notes and docs into a draft handover. It can't recover reasoning that was never written down, so the "why" interview still matters.
What's the most common thing teams forget to hand over?
In my experience, the reasons behind decisions. Facts and tasks get passed on. The "why" is what disappears.
Make it boring
A good handover should feel like nothing happened. That only works if decisions, reasons and workflows are captured as part of normal work, in places the next person can find. Start with a decision log and one "why" interview the next time someone changes roles.
We're building Shane to keep the decisions and context behind a team's work in one place, so they stay with the team when people move on. If that's a problem your team has, you can join the waitlist at tryshane.ai.