An owner takes three weeks of leave and comes back to a queue of decisions nobody else was willing or able to make. Quotes waited. A key customer only wanted to speak to the owner. A supplier issue was parked. The usual reading is that the business needs its owner. That is true, but it is not a compliment. It describes how the business is built.
Key-person dependence means that significant parts of a business’s revenue, delivery, decisions or relationships rely on one named individual. It is usually treated as a continuity risk: what if they get sick, leave or retire? That framing covers the dramatic event and misses the larger, continuous cost. Dependence slows decisions, limits growth, holds back other people’s development and lowers what the business is worth, every day, while everyone is still there.
This article explains why key-person dependence is a value question as much as a risk question, where dependence actually sits, what it costs before anyone leaves, and practical ways to reduce it without producing a pile of documents that change nothing.
Why it is a value question
Anyone who looks closely at a business from outside, such as a buyer, a lender or an insurer, looks for dependence on individuals. Which revenue depends on a named person? Which approvals only clear when one person signs? Which customers would reconsider the relationship if that person left? A buyer will typically respond by paying less, deferring part of the price until performance is proven, or requiring the person to stay on for a period. A lender may ask more questions or set tighter terms.
A useful distinction is between an asset, something that produces a return whether or not a particular person turns up, and an arrangement, which produces a return only while that person is present. Most owner-run businesses are partly arrangements. The question is how much, and whether the owner has chosen that or simply drifted into it.
What dependence costs before anyone leaves
The quiet costs of dependence are continuous:
- Delay: work queues at one person’s desk, and the queue lengthens as the business grows.
- A growth ceiling: the business can grow only as fast as its indispensable people can review, approve and fix things.
- The owner’s time: hours spent on routine decisions are hours not spent on direction, major customers, investment or improvement.
- Weaker capability: a team that never makes decisions does not learn to make them, so dependence deepens year by year.
- Distorted decision-making: an indispensable person can acquire an informal veto, and disagreements get avoided rather than resolved.
Dependence also tends to grow with success. The people most relied on are usually genuinely excellent, which is why their indispensability looks like strength rather than risk.
Common misreadings
- It is an insurance problem. Key-person insurance and a named deputy can soften the financial impact of a sudden departure. They do nothing about the continuous costs above. Talk to an adviser about insurance, but do not mistake it for a solution.
- It is a knowledge problem, solved by documentation. Some dependence is knowledge that can be written down. Much of it is judgement on unusual cases and relationships held in one person’s name, which documents do not transfer.
- It reflects loyalty and commitment. Dependence is often created by the business itself. If being indispensable earns status, capable people will make themselves indispensable.
- It is someone else’s issue. The most significant dependence often sits with the owner or the most senior person, who is the least likely to see it.
Five kinds of dependence
Dependence takes different forms, and each needs a different remedy. Treating them as one problem is why many attempts stall.
| Kind | What it looks like | What reduces it |
|---|---|---|
| Relationships | Customers, suppliers, lenders or regulators deal only with one person | Second and third relationships built well before any renewal or change |
| Judgement | One person decides the unusual cases: pricing exceptions, quality calls, risk acceptance | Exceptions decided with others present, and the reasoning recorded at the time |
| Method | How the work is really done lives in one person’s head | Documenting the best performer’s actual method, then training others in it |
| Authority | Approvals clear only when one person signs | Delegated limits that are actually used, with sampling instead of checking everything |
| Identity | Customers believe they are buying the person | Repositioning what the business sells, or accepting the constraint and pricing it honestly |
The last two often belong to the owner, and they are the two least likely to appear on any risk list.
Score roles, not people
Not every dependence needs fixing. Score each critical role on two dimensions:
- Materiality: how much revenue, margin or delivery capability depends on it.
- Substitutability: how long and how much it would cost to restore the capability if the person were unavailable.
Act where both are high. Monitor where one is high. Leave the rest. The assessment should be made by the owner or manager responsible, not only by the person concerned or their own team, who may find it hard to judge objectively.
Build second relationships before you need them
Relationships held by one person are among the hardest dependencies to transfer, because trust cannot be handed over in a meeting. Start early, well before any planned change. Introduce a second person to each key customer, supplier or lender in a natural role: a production manager who attends quarterly reviews, an engineer who handles technical questions, an accounts contact who resolves invoices. Let them build a track record of being useful. Over time, the counterparty learns that several people in the business understand their needs. Do this before a contract renewal or a sensitive negotiation, not after a resignation, when the counterparty is already reconsidering the relationship.
Make judgement visible
Judgement on unusual cases, such as a pricing exception, a quality call or a decision to accept a risk, is usually the least transferable part of an expert’s value. It can still be shared. Decide exceptions with others present rather than alone. Explain the reasoning as the decision is made, and record it briefly at the time, because reasoning reconstructed later tends to become a justification rather than an explanation. Over months, a record of real decisions and their reasons becomes a practical guide that others can learn from and challenge, and it shows where a rule could replace a judgement.
Document the best performer’s actual method
Process documentation commonly fails in two ways. An idealised process, written by someone who does not do the work, is followed when it is presented and ignored afterwards. An averaged process, assembled from what most people currently do, writes mediocrity into the standard.
A better approach is to document the best performer’s actual method. Watch the person who gets the best results and record what they really do: the sequence, the checks, the shortcuts and why they take them, and above all the points where they stop following steps and start making judgements. This produces a standard that is demonstrably achievable, reveals the handful of decision points where dependence really lives, and creates a baseline for improvement.
Separate essential steps from personal habits, start with frequent, repeatable work rather than rare decisions, and expect some resistance, because a person’s method is often their standing. Make it clear that sharing their method increases their value to the business rather than reducing it.
Delegate in stages
Reducing dependence on judgement and authority requires delegation, which works best in stages: show the person how it is done, supervise them doing it, let them do it and report immediately, move to periodic reporting, and finally have them train someone else. Two rules make this work. Accountability stays with the delegator until the handover is formally recognised. And the real test is the unusual case, not the routine one, because that is where dependence lives.
A useful warning sign: if you find yourself chasing people for updates, you have assigned a task rather than delegated it. Delegation transfers the authority to act along with the obligation to report. The article on delegating without losing control covers this in more depth.
Make succession part of what good looks like
If people are judged mainly on their personal output, holding on to critical work is the rational choice. Change the measure: treat a manager as fully capable only when their function runs well in their absence, and make a developed successor part of the criteria for promotion or reward. That costs little to state and changes what ambitious people aim for. It also only works if successors want the role, so understand what motivates each person.
A worked example
This is an illustration. The owner of a 12-person precision machining business does all quoting for complex jobs, personally manages the three largest customers (about 55% of revenue), approves every purchase over $500 and is the only person who can program the five-axis machine for difficult parts. During a two-week absence, quotes stalled, a customer escalation waited and the five-axis machine sat idle on complex work.
The owner scores the roles. Quoting, the major customer relationships and five-axis programming score high on both materiality and substitutability. Purchase approval is high on delay but easy to change.
Over twelve months, the owner:
- Quoting: the estimator observes the owner quoting ten complex jobs and records the method, including the rates, set-up allowances and the risk factors the owner adds for difficult features. The estimator then prepares quotes with the owner reviewing every one, then one in five.
- Relationships: the production manager attends quarterly reviews with the three largest customers, and an engineering contact is established at each.
- Authority: the production manager’s purchasing limit rises to $5,000, with the owner sampling invoices monthly instead of approving each.
- Method: a second machinist learns five-axis programming in stages, starting with simpler parts and moving to difficult ones under supervision.
- Test: at month twelve, the owner takes four weeks of leave.
The absence goes smoothly. Quote turnaround falls from about six days to about two, because quotes no longer wait for the owner. The owner’s time on routine approvals falls from about ten hours a week to about three, freeing time for customer development. If the owner ever sells, a buyer will see a business that runs without its founder in the room.
How this applies to a small Australian business
Most small businesses start as arrangements built around their founders. Reducing dependence takes years, so start well before you need to:
- List the roles whose absence would cost material revenue or delivery within a quarter.
- Check leave records: untaken leave by key people is a free and reliable signal of dependence.
- Build second relationships with key customers and suppliers.
- Document methods from your best performers, starting with frequent work.
- Raise delegated limits and actually use them.
- Test by having key people take genuine leave.
- Talk to your adviser about key-person insurance and, for businesses with several owners, agreements covering what happens if an owner leaves or dies. These address sudden events, not the continuous cost.
- If you plan to sell, assume buyers will examine dependence closely, and prepare years ahead.
The articles on building standard operating procedures and business continuity planning cover related steps.
Signals worth watching
- Key people not taking leave.
- Approvals routing around a deputy back to the original person.
- Customer contracts or expectations naming an individual.
- Internal candidates declining senior roles.
- Documentation written after an incident and never used.
- Onboarding taking longer each year.
- Escalations always arriving at the same desk.
- Lenders or buyers asking about key people.
Common mistakes
- Relying on insurance or a named deputy as the whole solution.
- Writing procedures nobody follows.
- Rewarding indispensability.
- Delegating tasks without authority, or authority without accountability.
- Testing successors on routine work only.
- Waiting until a sale, illness or resignation to start.
Frequently asked questions
Is some key-person dependence unavoidable? Yes, especially in small, specialist or professional businesses. The aim is to reduce dependence where it is costly and to make deliberate decisions about the rest.
Will reducing dependence on me make me less valuable? It makes the business more valuable and frees your time for work only you can do. That is usually a better position for an owner.
How long does it take? Some changes, such as raising approval limits, take days. Building relationships and judgement in others takes months or years. Start with the highest-scoring roles.
Questions to ask
- Which roles would cost us material revenue or delivery within a quarter of someone leaving?
- Which approvals clear only when one person signs, and what does the queue cost us?
- Are our procedures based on our best performer’s actual method?
- Who holds our key customer relationships, and who else knows those customers?
- What would a buyer discount in this business today?
- When did our key people last take a genuine break?
Bringing it together
Key-person dependence is not just a risk that might happen one day. It is a continuous cost in delay, growth, capability and value, paid while everyone is still present. Find where dependence sits across relationships, judgement, method, authority and identity. Score roles on materiality and substitutability, document the best performer’s real method, delegate in stages, build second relationships and make developing a successor part of what good performance means. A business that runs well without its founder in the room has not been diminished. It has been finished.
Source: KEVOS notes. Examples and figures in this article are illustrations. This article is general information, not financial, insurance or legal advice.
