They asked for "a quick chat," and now you're sitting across from the person who holds your team together while they tell you they're leaving. Somewhere in the back of your head a list is already forming: the client who only talks to them, the release they were leading, the two junior people they've been quietly coaching. And underneath it, the question you can't ask out loud — is this the start of everyone leaving?
The takeaway up front: the first week after a top performer resigns is not about replacing them — it's about protecting the people who stayed. The work will get covered, badly at first and properly later. What you can't recover from is a week of panic, silence, and visible favouritism aimed at the person walking out the door. Your team is about to learn what you're like under pressure, and that lesson sticks long after the leaver's laptop goes back to IT.
Day one: the conversation in the room
What you say in the next ninety seconds sets the tone for the whole notice period.
Say thank you, and mean it. "Thank you for telling me directly — I know that's not an easy conversation to open." Someone who feels respected on the way out gives you the honest version of what's fragile in their work. Someone who feels punished gives you the polite version.
Don't negotiate in the first meeting. The instinct to fix it immediately — more money, a promotion, "let me see what I can do" — is strong and almost always wrong. You don't yet know why they're leaving, and an offer made in the first five minutes reads as panic rather than value. Say instead: "I don't want to react on the spot. Can we talk properly tomorrow?"
Don't take it personally out loud. Going cold, or saying "well, I wasn't expecting that", turns a resignation into a rupture, and the team hears about it by lunchtime.
Ask two questions before they go. "Is your mind made up, or is there a version of this where you stay?" and "What would you want me to know?" Then be quiet. Most managers fill that silence with reassurance and lose the most useful information they'll get all month.
Day one or two: the counteroffer question, answered properly
Somebody will tell you to counteroffer. Before you do, understand why counteroffers so often fail.
People rarely leave over one thing. They leave over an accumulation — being stuck, being overlooked, a manager relationship gone flat, work that stopped being interesting — and then a number arrives that gives them permission to act. A counteroffer addresses the number and leaves the accumulation where it was. Three months later the same frustrations are there, plus a new one: it took a resignation letter to get taken seriously.
The second cost is easier to miss. Counteroffers are never really private, and once your team works out that the reliable way to get a raise is to interview elsewhere, you've taught them a process. That's an expensive lesson to fund.
So when is a counteroffer defensible? Narrowly: when the reason for leaving is a structural thing you should have fixed anyway — a title that no longer matches the work, a pay band that drifted below the market — and when you'd make the same correction for anyone in that position, offer or no offer. If you'd only do it for this person under this pressure, it isn't a correction; it's a hostage payment. And if they really are underpaid, fix the band for everyone in it.
Days two to three: tell the team before the rumour does
Agree with the leaver what will be said and when — then say it yourself, once, to everyone at the same time. Not one-to-one over three days, which guarantees the last person to hear feels like an afterthought. Keep it short, warm, and free of speculation about why.
Then answer the question they're actually asking, which is never "why did they leave?" It's "what does this mean for me?" People are calculating how much extra work is landing on them, and whether they should be updating their own CV. You almost certainly don't have the coverage plan yet, so say so with a date attached — "I'll come back to you all on Thursday" — and then come back on Thursday, even if the answer is partial.
One thing to avoid: over-praising the leaver in front of the people staying. A warm acknowledgement is right; a eulogy tells everyone still in the room where they rank.
Days two to four: find out why — while they'll still tell you
You have a narrow window. The person has already decided, so they have little left to protect and are more candid than they've been in months. After the last day, that window closes for good.
Ask this yourself, separately from any formal HR exit interview, and frame it as wanting to learn rather than wanting to change their mind — the moment it feels like a retention pitch, the honest answers stop:
- What made you start looking in the first place? (This is the real cause. What they say when they hand in notice is usually the trigger, not the cause.)
- What would have had to be different six months ago?
- What's the thing about working here you'd change if you could change one thing?
- Is there anyone else on the team you think I should be paying more attention to?
That last question is uncomfortable and frequently the most valuable. Good people know who else is unhappy long before their manager does.
Then do the thing most managers skip: write the answers down and read them next to the last few departures. One resignation is an event. Three in a year with the same theme running through them is a system telling you something — usually no visible path forward, a workload that never resets, or a manager who stopped noticing.
Days three to five: protect the people staying
This is the week's real work, and it gets postponed because it feels less urgent than coverage. It isn't. A respected person leaving destabilises everyone around them, in two directions. Some get anxious: if the best person here is leaving, what do they know that I don't? Others get opportunistic in a good way: does this mean there's room for me now? Neither question answers itself.
So book short one-to-ones with everyone inside that first week — individual, not a group reassurance session, because nobody says the true thing in a group. Ask "How are you feeling about this?" and "Is there anything about your own role you want to talk about while we're rethinking things?" You're inviting the quiet flight risks to speak up while you can still act on it.
Two rules for those conversations. Don't make promises you can't fund — "you'll definitely get their projects" is a trap if you don't control that decision. And don't quietly hand the leaver's hardest work to your second-best performer as a compliment. That's how one resignation becomes two. If someone's taking on more, say what's coming off their plate, or say plainly that it's temporary and name the date you'll revisit it. Handled deliberately, the reshuffle helps you: a departure frees up scope, and scope is what ambitious people are usually short of.
End of the first week: stabilise the work, don't rebuild it yet
You don't need a full handover plan by Friday. You need to know what would actually break, which is a much shorter list. Spend an hour with the leaver on risk rather than tasks: what's time-critical in the next four weeks, what do they hold that nobody else can access (a vendor portal, an admin account, a scheduled job running under their login, a relationship where they're the only known contact), and what's mid-flight and expensive to drop.
Cover that list, and only that list, this week. The full inventory-and-transfer process — what moves, what stops, what waits, and who owns each piece by name — belongs in the remaining notice period; there's a step-by-step version in our guide to running a handover when someone leaves your team.
And resist writing the job ad on day four. The role you're tempted to post is the role as this person grew it, shaped around their strengths and the things they quietly absorbed over years — and hiring for that exact silhouette is how you end up disappointed in a perfectly good new joiner. Use the notice period to work out what the team needs now, which is often a different shape entirely.
What not to do in week one
- Don't go quiet. Silence from a manager after a resignation is read as bad news, every time.
- Don't panic-restructure. Reorganisations announced in week one are reactions, not decisions, and you'll be undoing them by month two.
- Don't skip your own reset. Losing a strong performer stings, especially if you're new to managing. Feeling it doesn't mean you did it wrong.
FAQ
What should I say when my best employee resigns?
Thank them for telling you directly, ask whether their mind is fully made up, and ask what they'd want you to know — then stop talking. Don't negotiate, argue, or react emotionally in that first meeting; you don't yet have enough information for any of it to be useful, and a calm response is what makes an honest conversation possible a day later.
Should I make a counteroffer to keep a top performer?
Only when the reason for leaving is a structural thing you can fix and would fix for anyone in the same position — an out-of-date pay band, a title that no longer matches the work. Money alone rarely holds someone whose real reasons accumulated over months, and a counteroffer the team hears about teaches them that resigning is the reliable route to a raise.
How do I stop other people from leaving after a key resignation?
Talk to each person individually within the first week and listen for the quiet ones. Be explicit about what extra work is landing where and for how long, rather than letting it accumulate silently. Where the departure frees up real scope, offer it deliberately to someone who's been asking for more.
When and how should I tell the team someone is leaving?
Agree the message and timing with the leaver first, then tell everyone at once, yourself, before the rumour arrives. Keep it brief and free of speculation about why. Address the question people actually have — what happens to the work — and if you don't have that answer yet, commit to a specific day when you will.
Is it my fault that my best performer quit?
Sometimes partly, often not, and the useful question is different: what can you learn while they'll still tell you? People leave for reasons that have nothing to do with their manager. But if the honest answers point at something you controlled — no visible path forward, a workload that never reset — that's worth knowing before it costs you a second person.
Next step
You can't undo the resignation, and the first week isn't for trying. Respond well in the room, ask why while they'll still tell you honestly, tell the team before the rumour does, and spend real time with the people staying — then cover only what would genuinely break, and leave the full handover and the hiring decision for the weeks you still have. When you reach the coverage and hiring stage, follow the how-to-manage-a-small-team playbook and compare the HR and project-management tools that keep "who owns this now?" answerable at a glance.
