How to make the case to keep someone on your team

You’ve got a great person at risk — a budget cut, a reorg, a manager who hasn’t noticed what they do. You get one shot to change minds. This is a step-by-step way to build that case, grounded in the research on what actually persuades a decision-maker (and skipping the stuff that doesn’t).

Step 1 — Lead with the cost of losing them

Open with the number, not the praise. Replacing someone runs roughly 0.5–2× their salary (Gallup), and about two-thirds of that is hidden — lost knowledge, coverage, and a 6–12 month ramp at partial output. Put a role-appropriate range on it and you’ve reframed the whole conversation: keeping them is the cheap option. See how to estimate it.

Step 2 — Frame it as a loss, not an upgrade

Anchor on the status quo: they’re in the seat today, and here’s exactly what breaks if they leave. Decision science (prospect theory) is clear that the same facts framed as a loss move people more than framed as a gain. "We lose the only person who understands billing, plus six months" beats "they’d be a great addition." More in argue the loss, not the upside.

Step 3 — Prove current impact with specifics

Now the receipts — but documented and concrete, not adjectives. Real numbers, named projects, dated incidents, a specific quote from a colleague about something this person did. Vague praise is forgettable; "shipped the migration that cut support tickets 30%" is not.

Step 4 — Make the forward case

Strong performers still get cut when the pitch is all backward-looking. SHRM’s own guidance weighs trajectory and strategic fit over raw past output. Show the trend, tie them to a priority that isn’t going away, and name what stalls without them. See past results aren’t enough.

Step 5 — Cut the filler

Drop the things that don’t move the needle: generic "everyone loves them" social proof, credential lists, shaky stats. They dilute the strong points. (We explain why in the myths piece.) Lead with cost and loss; everything else supports.

A structure that works

1. The stakes: what the org loses if they go (cost + concrete losses).
2. The evidence: documented impact, with numbers.
3. The future: trajectory and strategic relevance.
4. The ask: keep them — and what that takes (a raise, a reassignment, a stay of the decision).

That’s exactly the shape needs-to-stay builds for you: a clean, branded one-pager that argues for itself. But the structure works on a doc or in a meeting too — the evidence is what matters.