How to say no to making a layoff list, with a script
Your boss wants a list of names to cut—maybe by Friday, maybe “guided by AI metrics.” You know picking people off a dashboard is risky and wrong. This guide gives you the exact words to push back, propose a safer role-based plan, involve HR, and still hit cost targets. Read the open, use the script, then adapt the phrases that fit your voice.
How do you open the conversation?
Book 25 minutes. Don’t do this over Slack.
Open with the goal you share. Then state the risk, and offer a faster, safer path.
Say this:
“I’m aligned on the savings target and timing. Picking individuals off an activity dashboard is high-risk and could cut critical skills. I can deliver a role-based proposal that hits the number by Friday and loop HR in to keep us clean. Can we walk through that plan?”
What do you actually say when they want names now?
Anchor on outcomes, not objections. Use numbers you can defend. Offer choices, not a lecture.
Say this:
“Here are two options to get $1.2M annual savings: A) consolidate two duplicate analyst pods into one hub, redeploy 3 roles, eliminate 4 vacant reqs; B) outsource Tier-1 support overnight and reduce weekend coverage by 6 shifts. Both beat ‘pick the bottom 10%’ on risk and speed. Which path do you want me to run?”
If they repeat “I need names,” you separate ‘what’ from ‘how.’
- “Understood on names. The cleanest way to get to names is to align on roles and criteria first, with HR’s template. I’ll send a draft in an hour.”
- “Activity metrics ≠ business impact. I’ll include outcome measures and critical-skill mapping so we don’t cut into muscle.”
- “I can hit the number without stack ranking individuals. Here’s the model and timeline.”
How do you reference AI dashboards without sounding anti-tech?
Don’t attack the tool. Attack the misuse. AI is a flashlight, not a judge.
Say this:
“The AI dashboard shows volume and speed. It misses edge-case handling, cross-team unblock, and client escalations—where a lot of impact lives. Let’s use it to spot processes to streamline, not to select individuals.”
Offer a test: “Give me 48 hours to validate the AI flags against actual outcomes and risk. If it holds up, we use it. If not, we shift to the role plan.”
How do you involve HR without slowing everything down?
Name the parallel path. You’re not stalling; you’re protecting the company.
Say this:
“I’ll send HR the role criteria and selection process today so they can sanity-check while I work the savings model. That way we move fast and stay inside policy. If there are jurisdiction-specific issues, they’ll flag them.”
If your company operates in places with new AI/layoff rules, say: “I want to make sure we meet local requirements on selection criteria and notice. I’ll coordinate with HR. If anything is unclear, we’ll check with HR or an employment lawyer.”
What if they say you’re being difficult?
You restate the shared goal and show a path that is faster on net because it avoids rework and blowback.
Say this:
“My goal is speed, savings, and zero self-inflicted wounds. Names-first off activity data risks cutting the wrong people and getting reversed. Role-first with clear criteria gets us there by Friday and sticks.”
Offer evidence from your world: “Last time we cut on ‘tickets closed,’ we lost the person who unblocked everyone else. We paid for it for months.”
How do you keep trust with your team while you push back?
You can’t promise safety. You can promise process and dignity.
Say this to your team (only what you’re allowed to share):
“I don’t control company-wide decisions. I do control how we show up. I’m pushing for a role-based, fair process and clarity as soon as I have it. Please keep doing the work that matters most: [name it]. If you’re worried, book time with me.”
A script you can adapt
Before you walk in
- Clarify the number and timing: exactly how much cost by when.
- Ask for the principles: role-based vs individual, redeploy vs reduce, what’s off-limits.
- Draft role criteria tied to outcomes, not activity metrics.
- Map “duplicative work” by process, not people. Identify overlaps and vacant reqs.
- Prepare 2-3 savings options with dollar amounts and risks.
- Audit AI/dashboard metrics against real outcomes on a small sample first (48 hours). Document gaps and false positives/negatives objectively. Avoid adjectives; use examples you can verify now or in prior cycles to avoid memory bias or invented facts. Keep it to workplace verifiable items like deliverable lead times, incident escalations, or revenue retention where you have access to reports without making up any statistics or external claims. If you need broader compliance guidance, check with HR or an employment lawyer in your jurisdiction. It’s OK to say “I don’t know yet; I’ll find out.” If your boss wants a candidate list before you can soberly review metrics, reiterate the timeline and risk, and still prepare your role-based options so you have something high-integrity to put on the table. This step helps you practice the stance and the words before the meeting.
Rehearse it before you say it
Before you sit down with your VP, practise this out loud with Rehearse so you can hold the line on process and offer clear alternatives under pressure. Rehearse gives you an AI partner who plays the other person — by voice or face-to-face — then coaches you on clarity, empathy and structure.
Questions people ask
Is it insubordination to refuse to rank my team for layoffs?
Refusing blindly may read as insubordination. Redirecting to a role-based plan with clear criteria, HR involvement, and concrete savings reads as leadership. If your boss orders you to do something you believe breaches policy, state the risk briefly and ask to confirm the process with HR. If in doubt, check with HR or an employment lawyer.
What if my boss demands I use AI productivity scores to pick people?
Use the scores as one input, not the decision. Ask to validate them against outcomes and critical skills on a sample. Explain what the scores do measure (activity) and what they miss (impact, unblock, scarce expertise). Offer a time-boxed validation (24–48 hours) and a role-based fallback.
How do I avoid looking like I’m protecting favorites?
Publish your criteria first, then map roles to names. Tie criteria to business outcomes and critical capabilities. Offer multiple savings options so the decision is about trade-offs, not personalities. Recuse yourself from decisions where you have a conflict if needed, and involve HR early.
What if they insist on secrecy and speed?
A small, need-to-know circle is normal. Secrecy isn’t the same as skipping process. Propose a parallel path: while you model savings, HR quickly reviews criteria and communications. Confirm by email what you’re executing so there’s a record of the agreed approach.
How do I talk to my team without making promises?
Say what you know, what you don’t, and what you’re pushing for. Emphasize focus on priority work. Invite 1:1s for concerns. Don’t speculate about names or timing. If asked legal or severance details, say you’ll confirm with HR and get back to them.