Workforce Reduction Strategies That Protect Performance
Organisations often assess the cost of a role more accurately than the cost of losing the person in it. The salary, the pension contribution and the redundancy payment can all be calculated to the pound. What sits outside that calculation is harder to price: who spots problems early, who holds important relationships together, and who knows why a process works the way it does. When those contributions are missing from the decision, the savings can look clearer than they really are.
That does not mean every role should be retained. Sometimes a reduction is the right decision, and pretending otherwise helps neither the business nor the people in it. It does mean that workforce reduction strategies should test three things before any decision is final: what contribution will disappear, who will take it on, and whether they have the time and knowledge to do it well. In fifteen years of working with professionals and organisations, I have found that the quality of those answers often reveals risks that a headcount calculation alone would miss.
What a Job Description Cannot Show
A job description records assigned duties. It describes the role as it was imagined rather than as it is lived. Over the years, people build a layer of contribution on top of their formal duties. They become the person colleagues ring when a client relationship wobbles, the one who notices a supplier problem before it becomes a delivery problem, or the only person who remembers why a workaround was introduced in the first place.
Picture a team leader whose individual workload looks light on paper. Measured by output alone, her role appears to be an obvious saving. What that measure misses is that she settles friction between two departments that do not otherwise talk, brings newer colleagues up to speed far faster than a formal induction would, and raises delivery risks weeks before they reach a report. Remove her post and the organisation removes all of that as well.
One thing I have noticed working with organisations is that this informal contribution is rarely hidden on purpose. It simply goes unrecorded because nobody has ever asked anyone to describe it. The people doing it often undervalue it themselves, because it feels like ordinary good practice rather than a distinct piece of work.
Seeing It From the Other Side
I have spent years sitting with professionals after redundancy, helping them make sense of what happened and what comes next. Then it happened to me. I worked for nearly three years in advice and guidance on a funded employability project, and when the project was not continued into another year, the whole team was made redundant together.
The process itself was straightforward. It was honest about where things stood, and I never felt that anyone was pretending the decision was something other than what it was. That honesty mattered more than I expected. It meant the difficulty was about the loss itself, rather than suspicion, confusion or a sense of having been treated unfairly.
What I missed most was not the role on paper. It was the people and the familiarity of the work. That is easy to dismiss as sentiment, but it points to something organisations routinely underestimate. Familiarity can remove a surprising amount of everyday friction from how a team gets things done. It is knowing who to ask, how a colleague prefers to work, and which problems can be settled with a wee five-minute conversation rather than a formal process. None of that appears on a structure chart, and all of it disappears when the team does.
The value did not vanish, of course. It left with each of us. I spent the following two months building my own business and then took on a new part-time role, and the knowledge and judgement I had built over those three years went with me. When a funded project ends, that loss may be unavoidable. When a business is choosing whom to release, it is worth asking whether the organisation truly intends to hand that value to someone else.
Why Visibility Gets Mistaken for Value
During a reduction, there is a risk that visibility becomes confused with value. Work that is easy to describe, regularly presented upwards or closely connected to senior decision-makers is easier to recognise. Contribution that happens quietly, remotely or through specialist knowledge can be much harder to see unless the organisation actively looks for it.
In my experience, this can become a significant blind spot in restructuring. A strengths-led view asks a different question from a structural one. Instead of asking which roles the organisation can do without, it asks where the strengths that will drive the next phase actually sit, and how exposed they would be if one or two people left. The answer rarely matches the organisation chart, and it echoes a point I have made before about how managers in small teams mistake visibility for potential.
This is also where fair process earns its place. Selection should rest on consistent, role-relevant criteria, tested against evidence of outcomes and future requirements rather than impressions. It should be documented and informed by appropriate HR and legal advice, particularly where collective consultation applies. Informal judgements about who seems indispensable are exactly how quiet value gets overlooked.
Testing Workforce Reduction Strategies Before the Decision Is Final
A better starting point is the work itself, before discussing any names. Every activity falls broadly into one of three groups: work that must continue at the same standard, work that could be redesigned, and work that should stop altogether. Only once that picture is clear does it make sense to ask what capacity and experience the remaining work genuinely requires.
From there, the three tests can be applied to each role under consideration. What contribution, formal and informal, will disappear with this post? Who will realistically take it on, and has anyone asked them? Do they have the time and the knowledge to do it well, or is the organisation quietly assuming both? Where the honest answer to that last question is no, the saving is not yet a saving. It is a cost that has been moved somewhere harder to see.
What often surprises leaders is how quickly these questions expose risk. They might reveal one person holding knowledge nobody else has, or a high performer carrying work well outside their role. None of these findings is a reason to delay every decision. They are reasons to make the decision with better judgement.
A Workload Transfer Is Not a Saving
Some work can genuinely be consolidated after a reduction, and that is a legitimate efficiency. When the remaining team is simply expected to absorb the same volume of work with nothing else changing, it is more accurately described as a workload transfer. That tends to surface later as missed deadlines, slipping quality, exhaustion and further resignations. The principle I return to with leaders is to do less by design, not by exhaustion.
A credible redesign makes real choices. It removes lower-value work, clarifies who owns what and cuts unnecessary hand-offs between teams. I have written before about what happens when organisations assume one person can simply absorb more, and a reduction is where that assumption does its greatest damage.
Managers need genuine authority during this period. If they are told to protect performance but cannot stop work, change priorities or push back on unrealistic demands, they become messengers of pressure rather than leaders of the transition. Clear decision rights, and a route to raise capacity concerns early, are what separate the two.
The People Who Remain Are Watching
Every reduction is observed closely by those who stay. They notice how colleagues were told, whether the criteria seemed fair and whether leaders were straight about what they knew. Those observations shape whether they commit to the organisation's next phase or begin quietly looking elsewhere.
Research published in the Academy of Management Journal by Charlie Trevor and Anthony Nyberg, drawing on organisation-level data from around 200 companies, found that downsizing predicted higher voluntary turnover among the employees who stayed. For an average company, their model predicted a 31% increase in voluntary turnover rates after reducing the workforce by just one per cent. Where the organisation also had weak practices around procedural fairness and keeping employees connected to their work, the predicted increase rose to 112% (Trevor and Nyberg, 2008).
Those figures are model-based predictions from a 2008 study rather than current UK workforce data, so I treat them as a signal rather than a forecast. What matters more is the direction of the finding, which suggests the way a reduction is handled can shape how many people it ultimately costs. My own experience of a straightforward, honest process sits at the better end of that spectrum. It did not make the loss easier, but I did not walk away feeling misled, and for the people who remain, that sense of fairness appears to matter a great deal.
Honest communication does not require leaders to have every answer. It requires them to say what is known, what is still being considered and how decisions will be made. Where confidentiality or consultation rules prevent them sharing detail, saying so directly is far better than leaving a gap for speculation to fill. Managers delivering the news also need preparation and space to absorb the change themselves.
The people who remain can experience a complicated mix of relief, guilt, uncertainty and increased pressure. Some may question the fairness of what happened, while others may take on too much because they are concerned about appearing unhelpful or vulnerable themselves. A team cannot rebuild confidence from a general instruction to be resilient. It needs specific conversations about new priorities, realistic expectations and where each person's strengths can make the biggest difference now, which is also where the argument I have made about stagnation as the real retention risk becomes very real.
Counting the Real Cost Afterwards
A reduction is not complete on the day people leave. The real test comes over the following months, once the people who held informal knowledge are no longer there to fill the gaps. A dashboard can show output holding steady while the people producing it are running at a pace they cannot sustain.
One practical safeguard I would build into any redesign is a review of the assumptions made before people left, held at 30, 60 and 90 days. It should look at customer outcomes, service quality, delivery, absence, voluntary turnover, manager workload, unfinished work and any gaps in knowledge. If a process is failing, or a gap has opened where someone's informal contribution used to sit, it is far cheaper to address it early than after a key person resigns or a client quietly moves elsewhere. Leaders whose workforce reduction strategies hold up over time are rarely the ones who move fastest. They are the ones willing to keep looking after the decision has been made.
The Question Underneath the Saving
If your organisation is facing a reduction, the salary line is the easiest part of the picture to see. A headcount saving is only a genuine saving if the organisation understands what work, knowledge, relationships and capacity leave with it, and has decided what happens to each of them afterwards. If the quietest, most reliable person in your team left next month, would you know exactly what went with them, and who would pick it up on Monday morning? If that answer comes slowly, the saving on paper may be telling you less than you think.
For smaller organisations or teams reviewing how work and strengths are currently distributed, my Workforce Potential Review offers a structured way to look beneath job titles at where contribution, strengths and dependency actually sit. It is not a redundancy-selection exercise. It is a way of getting a clearer picture of your people before structural decisions are made.
By Paula Donnan
Strength at Work | Better judgement. Stronger leadership. Higher performance.
If this is affecting you, book in for a free 30-minute initial briefing to discuss the way forward.
Comments