ยท 6 min read
After the cut: the first 30 days of a smaller team.
The cut is the easy part. The first 30 days with the smaller team are where a right-sizing is actually won or lost, because the cut removed people and left the work, the ownership, and the fear exactly where they were. If you spend those 30 days reassuring the survivors instead of rescoping their jobs, the team quietly concludes the cut made things worse, and the people you most wanted to keep are the first to act on it.
What you have probably noticed
The cut went through. It was clean, it was legally sound, the hard conversations are behind you. And then the room goes quiet in a way you did not expect. The people who stayed are not relieved. They are watchful. Output does not drop in week 1, when everyone is still being careful; it drops in week 2, when the real size of the remaining work becomes visible. And somewhere around week 3, someone you were counting on, someone who was never on any list, resigns. The cut is supposed to be the difficult moment. Instead the difficult moment turns out to be the month after it.
The tell is that nobody says what is wrong. There is no revolt and no obvious crisis. There is just a team that is busier, quieter, and harder to read than it was, and a nagging sense that the thing you did to fix the company might be costing you the part of it you wanted to keep.
What it actually means
A cut removes people. It does not remove the work, it does not redistribute ownership, and it does not tell the people who stayed why they are still here. Those three gaps are the whole problem, and none of them close on their own. Survivor guilt is real, but it is not the main risk. The main risk is mechanical: the same volume of work now rests on fewer people, and if nobody has rescoped it, the team experiences the cut as a quiet increase in their own load. That is the version of a right-sizing that fails. Not the headcount, the scope.
The late resignation follows from the same thing. Some people decided to leave the moment the cut was announced; the announcement told them the company was the kind of place that cuts, and they started looking that evening. They simply waited for a calm week to hand in notice. The ones who move first are the ones with the most options, which is usually the exact overlap with the ones you most needed to keep. So a cut aimed at the weakest third of the work can, if the first month is handled badly, cost you a slice of the strongest.
What to do about it
- Rescope on day 1, before you reassure anyone. The strongest signal you can send is not a speech about resilience. It is cancelling or pausing a project in public. Killing work tells the smaller team that the job got smaller too, which is the one thing they need to believe and the one thing a reassuring email cannot say. If the backlog is the same on day 2 as it was the week before the cut, the team has its answer, and it is the wrong one.
- Name every orphaned responsibility in week 1. The people who left took ownership of things that are not on any roadmap: a flaky deploy only one person knew how to unstick, the relationship with a supplier, the on-call knowledge for a service nobody else has touched. List those gaps explicitly and either give each one a named owner or decide out loud to drop it. The gaps you do not name are where the next incident comes from, three weeks on, when it looks like the smaller team failing rather than a handover that never happened.
- Change the rituals on day 1, not when they break. A team of 15 running the standup, the planning cadence, and the on-call rota that were built for 40 will feel understaffed in everything it does, and will come to believe the cut broke it. Redesign the rituals for the size you are now. Fewer people on the rota means a different rotation, not the same one with holes. A smaller planning group can decide faster; let it. The rituals are how the team feels its own size every single day, so they are the fastest way to make a smaller team feel deliberate instead of depleted.
- Have the retention conversation in week 1, not week 4. Go to the three or four people you most need and tell them, specifically, what their job looks like now and why it is a better job than it was. Do this before the recruiters do, because by week 3 the recruiters already have. This is not a raise conversation and it is not a loyalty plea. It is you treating the people who stayed as the plan, out loud, while the plan is still forming.
I have watched a team cut from roughly 40 to around 22 lose two more people in week 3 and read it as proof the cut had failed. It had not. Those two had decided in the announcement meeting and spent a fortnight interviewing; their leaving was priced in the day the decision was made, not caused by the weeks after it. The team that ran the first month well, the one that rescoped on day 1 and rebuilt its rituals immediately, had its delivery cadence back within the quarter. The one that spent the month reassuring everyone and changed nothing about the work was still slower six months later with the same headcount. The difference was entirely in the first 30 days.
When not to reach for more
The first instinct, when output dips in week 2 and someone resigns in week 3, is to do more: a second small cut to "finish the job", or a wave of reassurance and new hires to plug the gaps. Both are usually wrong. A second cut inside the first month tells the team the first one was guesswork and starts the clock on everyone's job search; if the sizing was right, hold your nerve. Backfilling immediately undoes the point of the exercise and often re-creates the exact shape you just cut. And do not promise there will be no more layoffs unless it is true and you can keep it, because a broken promise of that kind costs more than the cut did. If output genuinely has not begun to recover 30 days in, the likeliest explanation is not morale. It is that the cut took delivery capacity rather than optionality: a sorting error, visible in the numbers, and fixable, but only if you name it rather than waiting for a smaller team to quietly absorb it. That diagnosis, and the decision about what the team should actually stop doing, is the work a structured diagnosis is for, and it is the same ground under any honest right-sizing decision. If the shape is still wrong after the first month, that is a restructuring question, answered differently from a one-off cut.
Frequently asked
What do you do in the first 30 days after cutting an engineering team?
Rescope the work before you reassure anyone. The cut removed people but not the backlog, so the first move is to cancel or pause projects in public, not to give a speech about resilience. Then name every responsibility that left with the people who went and either give it a clear owner or drop it out loud. Change the rituals on day 1: a team of 15 running the standup, planning, and on-call rota built for 40 will feel understaffed and start believing the cut broke them. Have the retention conversation with the people you most need in week 1, not week 4, because by week 3 they have already taken the recruiter's call.
Why do people quit a few weeks after a layoff even if they kept their job?
Because some of them decided to leave the day the cut was announced and simply waited for a calm moment to do it. A week-3 resignation is usually not a reaction to how the first weeks went; the decision was made earlier, in the meeting where they learned the company would cut. The second reason is scope. If the same amount of work now sits on fewer people and nobody rescoped it, the team quietly concludes the cut made their own job worse, and the people with the most options, who are usually the ones you most wanted to keep, leave first. Expect a small number of late departures and plan for them rather than reading them as a second failure.
Should you promise there will be no more layoffs after a right-sizing?
Only if it is true and you can keep it. A promise of no more cuts that you break three months later costs more trust than the original cut did, and the team will treat everything else you say as negotiable. If you genuinely believe the organisation is now the right size, say that plainly and show the work: the rescoped backlog, the owners, the plan the smaller team is actually running. If you are not sure, do not fill the silence with a guarantee you cannot stand behind. Calm honesty about what you know and do not know keeps more people than a reassurance that later turns out to be false.
How do you know if a right-sizing worked?
Delivery cadence recovers within a quarter and the people you most wanted to keep are still there. If output has not started to recover 30 days in, the likeliest cause is that the cut took delivery capacity and not just the capacity you were holding against a future that had not arrived. That is a sorting error you can see in a burn plan, and it is fixable, but only if you name it instead of waiting for the team to absorb it. A right-sizing that leaves a smaller team shipping at the old cadence, with its strongest people in place, worked. One that leaves fewer people doing the same volume more slowly did not, whatever the headcount line now reads.
Written from patterns I've seen across engagements. If any of it sounds too specific to be general, that's why.