What Leaders/Managers Can Learn from Finish Big
Devon had led the fulfillment division for six years when a peer's promotion in the same building made his role increasingly unworkable. He accepted an outside offer and told his team he was "chasing new challenges," never naming the real reason he needed out. With two weeks' notice, he named the most senior person on the team as successor, rather than the one who had actually been running cross-functional projects in his absence. He handed over a folder of passwords and vendor contacts, nothing about the informal calls he made weekly to keep two feuding departments cooperating. Four months later, the team was still calling him with questions he'd never documented, and his chosen successor was quietly job-hunting, worn down by a role built on decisions no one had written down.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Getting honest about why you're really leaving the role
Leaders often reach for the safest public reason for a departure, a better offer, a new challenge, even when the real driver is conflict, exhaustion, or being passed over. That safer story can feel kind, but it also prevents you from addressing a pattern that might otherwise follow you into the next job, and it denies your team the honest picture they need to trust the transition.
Leaders who hide the real reason often repeat the same unresolved problem in their next role, arriving with the same blind spot intact.
Before announcing a departure, write down the actual reason in one sentence, and decide separately what version of it you'll share.
Documenting the judgment calls only you make
Most leadership handoffs cover the org chart and the passwords but skip the informal judgment: which vendor gets the benefit of the doubt, how you calm a difficult client, when to escalate a conflict versus absorb it. That tacit knowledge determines whether a team keeps functioning in your first absence, and it takes months to surface well, not the two weeks most notice periods allow.
A leader who only transfers formal responsibilities, not the judgment behind them, leaves a successor set to repeat mistakes the leader already learned from.
Keep a running log for one month of every judgment call you make that isn't written in any policy, and hand it to whoever might succeed you.
Naming a successor for what they'll protect, not who's available
Under notice-period pressure, it's tempting to hand a team to whoever is most senior or most eager, rather than whoever will protect what actually makes the team work: its trust, its standards, its relationships with other departments. Convenience-based succession optimizes for a smooth two weeks and a rough two years.
Choosing a successor by availability alone often installs someone who manages tasks well but has never held the team's harder relationships together.
List the relationships or norms that would quietly collapse under the wrong successor, and weigh candidates against that list before weighing convenience.
Letting go of being the answer
Leaving a leadership role means giving up being the person people default to, and that identity loss is often sharper than expected, especially when the next role hasn't yet replaced the sense of being needed. Planning what fills that gap, a different kind of contribution, a deliberate pause, an honest conversation with whoever you're leaving behind, matters as much as any handoff document, even though none of it will show up on an org chart.
Being honest about a rushed or unhappy reason for leaving can conflict with documenting a thorough handoff, since urgency to leave, or being pushed out, shrinks the time available to prepare your team well. When the two collide, protect whatever preparation time you have for the judgment calls and relationships most likely to break, rather than trying to document everything equally in too little time.
Name one thing, honestly
What would the people you're leaving behind say, honestly, about how ready they were the day you walked out?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
List the relationships or norms that would quietly collapse under the wrong successor, and weigh candidates against that list before weighing convenience.