Why Adding Headcount Rarely Fixes Productivity Problems
If your business feels busy but not efficient, “we need another pair of hands” is an understandable conclusion.
It’s also one of the most expensive ways to avoid the real problem.
Because in most organisations, productivity isn’t being lost due to a lack of people. It’s being lost in the gaps between people: handovers, approvals, version confusion, duplicated admin, unclear ownership, and information scattered across email, drives, SharePoint, and paper.
Headcount can hide those issues for a while. It rarely fixes them.
And the longer you leave it, the more the business quietly builds a dependency on workarounds that don’t scale.
DocR’s mission is simple: make work flow properly for growing businesses, by spotting what’s slowing things down, fixing it in a way people actually adopt, and delivering results worth talking about.
This article will show you:
- Why adding headcount doesn’t fix productivity
- The common “invisible” causes of lost time, especially around documents and approvals
- How to diagnose what’s really happening
- Practical fixes you can make without buying new software or running a big change programme
The uncomfortable truth: headcount masks friction
When you add a new person to “help out”, you usually get short-term relief because emails are answered quicker, chasing happens more consistently, admin gets absorbed, and someone becomes the new glue holding the process together.
That can feel like productivity improved.
What often happened is this: you hired a human workaround.
You didn’t remove the cause of the delays. You staffed them. And again we repeat: Thats why adding headcount doesn’t fix productivity
And that has three predictable outcomes.
1) Costs go up permanently, the problem stays
Salary, NI, onboarding, management time, tools, licences, training, all ongoing. Meanwhile the same bottlenecks remain.
2) Complexity increases
More people means more handovers, more versioning, more “who’s doing what?”, and more need for structure. In fact, this idea is well known in software engineering through Brooks’s Law, which explains that adding people to a struggling project can actually slow it down due to coordination overhead. – Brooks’ Law
3) You create key-person dependency
The new person becomes the one who “knows where everything is” or “chases the approvals” or “fixes the spreadsheets”. If they leave, the business feels pain immediately.
If that sounds familiar, you’re not alone.
The real reasons productivity collapses (and hiring can’t solve them)
Below are the usual culprits I see when a team is flat out, but output isn’t improving.
1) Work is stuck in approvals (and nobody owns the queue)
Approvals rarely fail because people don’t care. They fail because approval requests are buried in inboxes, there’s no standard for what good looks like in a submission, nobody can see what’s waiting and for how long, and the approver is a bottleneck without realising it.
Hiring another admin to chase approvals doesn’t fix the underlying issue: there’s no visible system of record for work in progress.
Quick win: create a single approval lane, even if it’s basic. Put approvals in one place, require key fields so the approver isn’t guessing, set an expectation such as “approved within 48 hours”, and include an escalation rule so it auto-reminds or forwards if no response.
2) Version confusion creates rework
If teams store documents across email threads, shared drives, SharePoint folders, local desktops, and printed copies, version control becomes tribal knowledge.
Symptoms include “Which one is the latest?”, edits being overwritten, duplicated effort, rework after using the wrong template, and audit evidence taking hours instead of minutes.
Hiring more people doesn’t stop rework. It often increases it, because more people are touching the same messy system.
Quick win: set a single source of truth rule. One location per document type, a simple naming standard, explicit ownership per folder or process, and a basic archiving approach so old versions don’t compete with current ones.
3) Information is scattered, so work starts with searching
If a task begins with ten minutes of searching, checking, asking, and re-checking, productivity is already lost before work even starts. Research from Microsoft’s Work Trend Index has shown that employees spend a significant portion of their time simply looking for information across emails, files, and messages. – Microsofts Work Trend Index
This often shows up as repeated questions in Teams or Slack, delays at month end because key info lives with one person, audit panic because evidence is “somewhere” but not findable, and constant “can you resend that?” emails.
You can hire people to search and chase, but it’s a poor use of money.
Quick win: define what must be captured, where it lives, how it’s named, and who owns it. A named role, not “the office”.
4) Manual re-keying is happening in multiple places
This one is painful because it’s invisible. If the same data is typed into a form, an email, a spreadsheet, a system, a PDF, and a client portal, you’re not short on staff. You’re short on flow.
Quick win: pick one high-volume admin process and remove just one repetition. Standardise the input, stop free-text where you need consistency, use a simple capture method, and reduce double entry by changing where the data is first captured.
You don’t need AI to do this. You need discipline and a clean capture point.
5) Processes evolved organically and no longer scale
Most SMEs didn’t design their workflows. They inherited them.
The process “works”, but only because experienced people know the shortcuts, mistakes are quietly corrected, someone chases the missing pieces, and exceptions are handled manually.
As you grow, exceptions multiply and “busy” becomes normal.
Hiring feels like the solution because it’s the most obvious lever. But the real issue is that the process has hit its scaling limit. Thats truly why adding headcount doesn’t fix productivity
How to tell if you have a headcount problem or a process problem
Here are the simplest tests.
Test 1: If you hired two people tomorrow, would the work still be chaotic? If yes, it’s process.
Test 2: Do you rely on specific individuals to keep things moving? If yes, it’s process and risk.
Test 3: Is it hard to answer “what’s stuck, where, and why?” If yes, it’s process and visibility.
Test 4: Do audits, inspections, or month end trigger panic? If yes, it’s usually document control and ownership, not staffing.
Test 5: Is the team doing work about work, such as chasing, searching, reformatting, reconciling, re-keying, and version checking? If yes, that’s operational friction.
What to do instead (a practical approach that doesn’t turn into a big project)
The mistake most businesses make is trying to fix everything. That triggers long meetings, vague improvement plans, software distractions, change fatigue, and then nothing sticks.
A better approach is clarity first, then fix one area properly. Research from McKinsey repeatedly shows that productivity gains usually come from redesigning workflows and removing friction, not simply increasing headcount. – Research from McKinsey
Step 1: Pick one workflow that causes friction
Good candidates include approvals, onboarding, compliance evidence, and document-heavy processes. You want something with volume and pain.
Step 2: Map what actually happens
Not the policy. Not the ideal. Reality.
Where the request starts, who touches it, where it gets stuck, where duplicates happen, where information is missing, and where someone does manual fixing.
You only need a simple map. The value is seeing the handovers.
Step 3: Fix the bottleneck, not the symptom
If approvals stall, create a visible queue and standard submission requirements.
If documents go missing, enforce a single source of truth and naming rule.
If re-keying happens, change the capture point so data is captured once.
If a key person is holding it together, build a lightweight SOP and ownership model.
Step 4: Lock it in with simple governance
Governance doesn’t mean bureaucracy. It means ownership, rules people can follow, a place to work from, and a way to measure if it’s improving.
The middle ground that works for most SMEs
Some businesses keep working around the mess. Others try to bite off a full transformation programme.
The sensible middle ground is to take one area, fix something tangible, then decide if it’s worth going further.
Practical examples: what fixing the flow looks like
Approval turnaround can be halved by introducing a single intake method, a visible approval queue, and automatic reminders.
Audit evidence time can drop dramatically by standardising where records live and removing multiple competing versions.
Project delivery improves by clarifying handover ownership and removing the chasing loop.
Admin time is cut by capturing data once and stopping the retyping into multiple tools.
Risk reduces when key-person dependency is removed and the process becomes simple and adopted.
None of these require big budgets. They require clarity, prioritisation, and someone who can spot the real cause quickly.
A quick self-check (10 minutes)
If you want a fast indicator of whether hiring is your actual issue, answer these honestly.
- Where does work most often get stuck: approvals, handovers, or visibility?
- How many places do you store the same type of document today?
- If a key admin person left tomorrow, what would break first?
- How often do you redo work because the wrong version was used?
- Can leadership see what’s in progress without asking five people?
If those questions make you uneasy, it’s probably not headcount.
It’s flow. Thats why adding headcount doesn’t fix productivity problems.