Reprioritize after layoffs with your manager, with a script
Headcount just went down and your backlog didn’t. Here’s exactly how to open the conversation with your manager, show the capacity math without sounding negative, handle “just make it happen,” and leave with clear priorities you can deliver. If you only have five minutes, copy the opener in the next section and book 30 minutes today.
What do you actually say?
Use this opener in your next 1:1:
“We lost X FTEs and still have A, B, C, D. Based on current capacity, we can deliver two of these well this quarter. I’ve mapped rough effort and risks. Can we choose what moves to Q1 and what we drop? I’ll own delivery on the agreed set.”
Then shut up. Bring three options: what to keep, what to delay, what to cut. Keep names out of it; talk outcomes and time. If they push for “all of it,” use: “I can show what slips when we add one more.” You’re not refusing; you’re putting trade-offs on the table.
How do you open the conversation?
Book 30 minutes with an agenda line they can’t ignore: “Reprioritize post-reduction: options and delivery plan.” Start with facts, not feelings: what changed, what’s currently committed, and the gap. Then propose choices.
Say this:
“Here’s the change: we’re down two engineers. Here’s our current slate, by effort. At this pace we can do Feature X and Market Launch Y well, or we can split across four and risk slipping both. I’d like your call on what we commit to now versus delay or drop.”
That framing signals ownership, gives them control on scope, and avoids a vibe of “I won’t.”
How do you show capacity without sounding negative?
Translate hours and people into choices. Use round numbers and ranges. Don’t bury them in spreadsheets.
Try:
“Rough math: we have 4 engineers at ~30 focused hours/week after meetings and support = ~120 hours. Feature X is ~200–240 hours, Launch Y is ~160–180. Both together push us into overtime or spill to next quarter. Which one matters more this quarter?”
If they question estimates, invite collaboration: “Happy to adjust if we think X is lighter. Which piece would you drop to hit this quarter?”
- Bring: list of active projects with rough hours, key dependencies, and risks.
- Note non-negotiables (compliance, legal) separately.
- Show one slide or one page, not a 15-tab workbook.
What if your manager says “just make it happen”?
You need to stay calm, agree on the goal, and bring it back to choices.
Use:
“Agreed on the goal. To make it happen, we can a) de-scope X to essentials, b) move Y to next quarter, or c) add temporary help. Which path would you like?”
If they say others are doing more with less: “Understood. Here’s our current load and blockers. If we pick A and B, I’ll own delivery and weekly check-ins. If we add C and D too, here’s what will slip first. Which trade-off do you prefer?”
How do you agree on what slips and what stays?
Bucket work into three piles: Must-keep, Delay, Drop. Name dates for the first two and write down the Drop list so it doesn’t sneak back by default.
Say:
“To lock this: Must-keep this quarter is X and Y. Delay to Q1: Z. Drop for now: W. I’ll circulate a one-pager so partners see the change. Sound right?”
Then set a cadence: “I’ll send a Friday update with green/yellow/red, risks, and any scope creep we should reject in real time.”
- Must-keep: moves the company metric this quarter, or legally required.
- Delay: valuable, but safe to push with minimal rework later.
- Drop: nice-to-have or dependent on people you no longer have.
What do you send after the meeting? (email template)
Subject: Updated priorities and delivery plan (Q4)
Thanks for aligning today. As agreed:
- Must-keep (Q4): Feature X (MVP by Nov 15), Market Launch Y (US only).
- Delay to Q1: Feature Z (design continues, build starts Jan). I’ll confirm a date once we size final scope with Design and Data. - Drop for now: Workflow W. We’ll archive tickets and note rationale to revisit mid-year if capacity changes. Capacity: 4 eng x ~30 focused hrs/week = ~120 hrs. Risks: dependency on Data API for Feature X; support load spikes on Mondays. Mitigations in doc. I’ll send weekly status (Fri) and raise trade-offs immediately if scope expands. Reply-all if I missed anything.”
A script you can adapt
Before you walk in
- List every active project and who it serves. Add rough hours, not story points only.
- Calculate true focused hours/week per person after meetings and support.
- Mark non-negotiables (compliance, contractual) in a separate box.
- Draft three options: keep/delay/drop with dates and risks.
- Collect 1-2 data points on past slip patterns to show consequence of overloading.
- Book a 30-min slot with an agenda that says “Reprioritize: options + plan.” Attach one-page summary, not a deck.
Rehearse it before you say it
Before you have this talk, practise the exact opener and pushback responses out loud with Rehearse so you’re steady when it’s real. 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
How do I estimate effort when everything’s still fuzzy?
Use ranges and assumptions. Say “Based on prior work, X is ~200–240 hours assuming API Y is ready.” Invite your manager to adjust numbers, then ask which scope to change. You’re not proving a theorem—you’re sizing to enable a decision.
Should I bring up burnout or stick to delivery risk?
Lead with delivery risk because it’s the business lever. If you see sustained overwork, tie it to execution: quality drops, attrition risk, on-call failures. You’re spotlighting outcomes, not feelings.
What if my manager says priorities are set above them?
Ask for the decision-makers and offer to bring the options. “Can you loop in Ops/GM for a 15-minute call? I’ll present the three paths and you can make the call together.” You’re making it easy to escalate trade-offs, not dumping the problem.
Do I need solutions, or is surfacing the problem enough?
Bring at least two viable options with dates and risks. It shows ownership and speeds a decision. If both options are bad, name the least-bad and the trigger that would switch paths.
How often should we revisit priorities after cuts?
Set a weekly 10-minute checkpoint for scope creep and a monthly replan. Short cycles prevent silent over-commitment and keep stakeholders aligned when reality changes.