5 takeaways
- Key-person dependency becomes a business risk when important work, decisions or customer relationships cannot continue without one individual.
- We should document the knowledge that affects customers, cashflow, payroll, pricing, systems and delivery first.
- Knowledge sharing should strengthen a valuable employee’s role, not make them feel that we are preparing to replace them.
- Cross-training carries a cost, but emergency cover, delayed work, lost customers and rushed recruitment can cost considerably more.
- Our goal is not to make talented people less important. It is to build a stronger business around their expertise.
Summary
When one employee holds critical business knowledge, an SME becomes vulnerable to disruption, delayed decisions and avoidable cost. We can reduce that risk by identifying essential knowledge, documenting practical processes, cross-training colleagues and building shared capability. The aim is stronger continuity, clearer accountability and measurable Business Progress without undermining valuable people.
Introduction
Key employees often become central to growing SMEs because they understand customers, systems, workarounds and decisions better than anyone else. That experience is valuable. The risk appears when the business cannot operate properly without them. We need to protect continuity carefully while respecting the expertise that helped build the business.
What should we do when one key employee holds too much of our business knowledge?
We should start by identifying exactly what would stop, slow down or become uncertain if that employee were unavailable tomorrow.
Then we can protect the highest-risk knowledge through simple documentation, cross-training, clearer ownership and sensible succession planning.
This is not about reducing somebody’s value.
It is about reducing unnecessary fragility around them.
A key employee may know how our biggest customer likes to work, why a pricing decision was made, how a specialist system is configured or what needs checking before a monthly process is completed. That knowledge has commercial value.
The problem starts when the business has no reliable way of accessing or using it without that individual.
Why is key-person dependency risky for a growing SME?
Key-person dependency creates risk because one absence can quickly become an operational problem.
The employee does not have to leave permanently. Holiday, illness, parental leave, a promotion or an unexpected personal situation can expose the same weakness.
How do we know one person has become a single point of failure?
A useful test is to look at what happens when they are not available.
Warning signs include:
- Important customer queries wait for them.
- Only they can complete a monthly process.
- Pricing decisions depend on their memory.
- Nobody else understands certain supplier arrangements.
- They hold key system knowledge.
- Colleagues regularly say, “We need to ask them.”
- They are contacted repeatedly while on leave.
- Owners or managers cannot confidently step in.
If several of these are happening, we have a business capability issue rather than simply a very experienced employee.
Our article on how role confusion can cost us payroll looks at the related problem of unclear ownership, duplicated work and decisions repeatedly returning to one person.
Why is this a systems problem rather than an employee problem?
Strong employees often accumulate knowledge because a growing business naturally relies on people who get things done.
That is understandable.
The weakness appears when we never convert enough of their experience into processes, training, records and wider team capability.
We should value expertise without designing the business around permanent access to one person.
What knowledge should we document before it becomes urgent?
We do not need to document everything.
We need to identify the knowledge where loss or delay could affect money, customers, compliance or delivery.
Start with questions such as:
- What could stop us serving a customer?
- What could delay an invoice?
- What could disrupt payroll?
- What could cause us to price work incorrectly?
- What could stop another employee completing an essential task?
- What knowledge would be difficult to reconstruct quickly?
Which customer and commercial knowledge matters most?
Important customer knowledge might include:
- Key contacts and decision-makers
- Pricing arrangements
- Renewal or contract dates
- Unusual service commitments
- Customer preferences
- Previous disputes or recurring issues
- Agreed processes that are not obvious from the contract
If this information exists only in one employee’s inbox or memory, our wider team cannot use it reliably.
Which operational and financial processes should we capture first?
We should prioritise processes connected to:
- Quoting and pricing
- Sales-to-delivery handovers
- Purchasing
- Supplier management
- Invoicing
- Credit control
- Payroll inputs and approvals
- VAT and finance information
- Quality checks
- Customer complaints
We do not need a 30-page procedure for every task. A practical checklist, short screen recording, process note or workflow can be enough.
The standard is simple: could another capable person understand what happens, why it
happens and what to do next?
How does key-person dependency affect day-to-day operations?
The first cost often shows up through time.
Work waits. Questions accumulate. Decisions are postponed. Other employees become hesitant because they know somebody else normally has the answer.
That pressure eventually reaches customers and cashflow.
Where do bottlenecks usually appear first?
Common areas include:
| Dependency area | What can happen | Commercial impact | First practical step |
| Major customer relationship | Nobody knows the history | Poor service or lost revenue | Record contacts, commitments and key decisions |
| Pricing | Quotes wait for one person | Delayed sales or weak margins | Document pricing rules and approval limits |
| Finance process | Invoices or reporting stall | Cashflow pressure | Create a checklist and backup owner |
| System administration | Access problems cannot be resolved | Operational downtime | Define authorised backup access |
| Technical delivery | Work cannot progress | Delays and rework | Cross-train another employee |
| Supplier relationship | Orders or issues wait | Delivery disruption | Record terms, contacts and escalation routes |
This is where the real cost shows up.
A missed answer might appear small, but if it delays delivery and invoicing, cash can reach the bank later while wages, PAYE, VAT and supplier commitments still have their normal payment deadlines.
How can dependency weaken onboarding?
New employees struggle when the real process exists only in somebody else’s head.
They learn by interruption rather than through structure.
Our guide to building a practical 90-day onboarding plan for a growing SME explains why clear expectations, processes, ownership and training should begin from the start.
Good onboarding should spread capability.
It should not simply create another employee who depends on the same key person.
What is the financial cost of relying too heavily on one employee?
The financial impact is wider than the cost of replacing them.
We may face:
- Recruitment fees
- Temporary or interim cover
- Overtime
- Training time
- Management time
- Reduced productivity during handover
- Delayed customer work
- Late invoices
- Rework
- Customer credits
- Lost revenue
There is also the cost of carrying additional payroll while a replacement learns the role.
For the 2026/27 tax year, employers generally pay Class 1 secondary National Insurance at 15% on earnings above the £5,000 annual Secondary Threshold. Different zero-rate thresholds can apply to certain employees, including qualifying under-21s, apprentices under 25, veterans and eligible employees in Freeports or Investment Zones. HMRC’s 2026/27 employer rates and thresholds set out the detail.
That means we should look beyond salary when estimating the full employment cost of additional cover or recruitment.
Pension contributions where applicable, equipment, software, training and management time may add further cost.
How can key-person dependency damage our margins?
Imagine one experienced employee normally resolves an issue in 20 minutes.
Without them, three colleagues spend two hours finding old emails, checking previous work and agreeing what to do.
The job has not changed.
Our labour cost has.
That additional time can quietly erode margin without appearing as a separate line in the accounts.
Before hiring another person because everybody feels busy, it is worth checking whether the real problem is capacity or structure.
How can we reduce dependency without making the employee feel threatened?
We should be clear about why we are making the change.
Saying, “We need other people to know everything you know,” can easily sound like replacement planning.
A better conversation focuses on resilience, development and reducing pressure.
We can explain that nobody should have to remain permanently available because only they understand an essential part of the business.
How can we make the key employee part of the solution?
We can ask them to help us:
- Identify the knowledge that carries the greatest risk.
- Improve processes that currently rely on memory.
- Train a suitable colleague.
- Create practical checklists or guidance.
- Define when issues should be escalated.
- Identify weaknesses that management cannot currently see.
This recognises their expertise.
It also gives us an opportunity to develop them towards mentoring, leadership, improvement or higher-value responsibilities.
Their contribution becomes bigger because they are strengthening capability across the business.
What if responsibilities need to change?
Cross-training does not automatically mean changing somebody’s employment contract.
However, if we materially change contractual duties or other terms, we need to handle that properly.
GOV.UK guidance on changing an employment contract states that employers must get an employee’s agreement if they want to make changes to their contract. Employers should consult or negotiate, explain the reasons for the proposed changes and listen to alternative ideas.
For sensitive or significant employment changes, specialist HR or employment-law expertise may be appropriate.
How do we turn key-person risk into a stronger long-term business?
We need to move from emergency cover to measurable capability.
A practical 90-day approach works well.
What should we do during the first 30 days?
Identify the five dependencies that would cause the greatest disruption.
Do not start with every process.
Start with risk.
What should we do during days 31 to 60?
Document the critical processes and identify backup ownership.
That might mean a second employee shadowing customer calls, learning a finance process or completing a task under supervision.
What should we test during days 61 to 90?
Let the backup person complete the process.
Then ask:
- Did they need repeated help?
- Was information missing?
- Were decisions clear?
- Did the customer experience remain consistent?
- Could the process continue without owner intervention?
That gives us evidence rather than assumption.
Our wider article on why sustainable growth needs structure before speed connects directly to this. Growth puts more pressure on systems, people, cashflow and margins, so dependency that feels manageable today can become much more expensive as volume increases.
Business Progress should be measurable. If another capable person can now complete an essential task, customers receive consistent service and fewer decisions queue behind one employee, we have evidence that capability is strengthening.
When should we bring in outside specialist expertise?
We do not need external expertise every time knowledge needs sharing.
Sometimes a manager and employee can resolve the issue with a checklist and sensible cross-training.
We should consider specialist expertise when the dependency involves areas such as:
- Employment law
- HR
- Cyber security
- Finance
- Tax
- Compliance
- Complex systems
- Business continuity
Our guide on what business problems SME owners should not handle alone provides a practical way to decide when an issue has moved beyond the capability or risk appetite of the existing team.
Within CH4B’s Business Progress Ecosystem, our Expert Partner Network connects members with trusted specialist expertise when an identified business priority requires implementation support beyond the existing team.
The principle remains the same.
We identify what the business needs next, then coordinate the right expertise around that priority.
What should we do first this week?
Start with one question:
If one person could not work tomorrow, where would our business feel it first?
Choose the highest-risk answer and take five practical steps:
- Name the dependency clearly.
- Estimate the commercial impact.
- Discuss it openly with the employee.
- Document the essential knowledge.
- Create and test one backup.
Then move to the next priority.
That is more useful than launching a company-wide documentation project that becomes another unfinished task.
Conclusion
A key employee should be an asset, not an unintentional single point of failure.
We do not solve that by making people feel less important.
We solve it by turning individual expertise into stronger business capability.
That means clearer processes, better cross-training, stronger ownership and a practical understanding of where risk affects customers, payroll, margins and cashflow.
Over time, the result should be a business where employees can take leave, develop into bigger roles or eventually move on without operations falling apart.
That is resilience.
It also creates greater clarity, stronger capability and measurable Business Progress.
If we are unsure where our biggest dependencies sit or which business priority needs attention first, we can speak with a Strategic Business Partner about the next practical step.
Is it always a problem if only one employee understands a specialist task?
No. Specialist expertise is valuable. The risk appears when an essential activity cannot continue, be recovered or be transferred within a reasonable period if that person becomes unavailable. We should distinguish valuable specialism from avoidable dependency.
Should we document every process in the business?
No. We should start with processes that affect customers, money, compliance and essential delivery. Documentation should create clarity and resilience rather than unnecessary administration.
How often should we review key-person dependency?
We should review it whenever we recruit, restructure, introduce new systems, win major customers or change responsibilities. A practical quarterly review of our highest-risk dependencies can also help us identify developing problems early. That is our practical management recommendation, rather than a statutory requirement.
What should we do if an employee resists sharing their knowledge?
We should first understand the concern.
They may fear losing status, control or job security. We need to explain the commercial reason clearly, recognise their contribution and involve them in deciding how knowledge is shared.
Sensitive situations may require specialist HR expertise.
Can software remove key-person dependency for us?
Not by itself. Software can store information, standardise workflows and improve visibility, but it cannot replace clear responsibilities, training, judgement and accountability. We need capable people and usable systems working together. The technology should support Business Progress rather than become another place where important knowledge disappears.
