Last Two Weeks Handoff

Last Two Weeks Handoff Skill

Your last two weeks are the trailer for how you'll be remembered — and the handoff doc is the only work artifact colleagues will use after forming their final opinion of you. The goal is specific: no one should need to call you in month two, and everyone should slightly resent that you're gone. This skill inventories what actually needs transferring (it's less than it feels, and different than it looks), writes the doc future-someone can actually navigate, and handles the mechanics — access, ownership transfers, goodbyes — that get forgotten until 4pm on the last day.

What This Skill Produces

• The handoff inventory — everything owned, triaged: transfer / finish / document-and-drop
• The transition doc — per item: state, next step, who-now-owns, where-things-live, the landmines
• The KT session plan — 2–4 sessions with agendas, because docs transfer facts and sessions transfer judgment
• The last-day checklist — access, ownership flips, personal-file hygiene, the goodbye message

Required Inputs

Ask for these if not provided:

• Role and the notice window — 2 weeks plans differently than 4
• The ownership list — projects, systems, recurring duties, relationships (internal and external), and the invisible things (the cron job only they know about, the vendor contact only they have)
• Who's inheriting — named successors, an interim manager, or nobody-yet (changes the doc from "handoff to a person" to "message in a bottle" — write for the bottle)
• The exit temperature — a happy exit and a bitter one produce the same professional handoff; only the goodbye note differs

Framework: The Triage Rules

1. Triage before documenting: Transfer (ongoing things a named person continues), Finish (closeable in the window — close them, a done thing beats a documented thing), Document-and-drop (things with no owner: state them, flag the risk, and explicitly don't pretend someone will do them). The undocumented fourth category — things that should die with your tenure — gets listed too, as "recommend discontinuing."
2. Write for month two, not day one: day-one questions get asked in KT sessions; the doc's job is the month-two question at 6pm with you unreachable. Per item: current state, immediate next step + date, the owner now, where everything lives (links, not descriptions), and the landmine — the non-obvious thing that will bite ("the deploy fails if run before the nightly sync; nobody knows why; run it after 9am").
3. Sessions transfer judgment, docs transfer facts: schedule 2–4 KT sessions early in the window (people postpone them; late ones get cancelled). Agenda per session, successor drives the tool while you watch — watching them do it finds the gaps your doc missed.
4. Relationships are handoffs too: every external contact and internal stakeholder gets a warm intro to their new counterpart before you leave — "after I go, Priya owns this; she's cc'd" — because an unintroduced successor starts from cold email.
5. The last day is mechanics, not memories: ownership transfers verified (calendars, on-call, docs, admin rights, recurring meetings re-owned), personal files separated per policy days earlier, expenses filed, equipment logistics, and a short goodbye note — gratitude, contact info, zero speeches.