--- title: "Key-person risk: when your operation lives in one person's head" url: "https://www.octalhq.com.au/insights/articles/key-person-risk-operations" kind: article description: "Key-person risk: when your operation depends on one person who \"just knows\" how it works. Why it's dangerous, and how to move that knowledge into a system." published: "2026-07-19T00:00:00.000Z" updated: "2026-09-21T03:12:24Z" topics: ["Operations"] --- # Key-person risk: when your operation lives in one person's head If your business only runs smoothly because one experienced person knows how it all fits, you have key-person risk — and it shows the day they're away. Here's how to reduce it. Key-person risk is when your operation depends on one person who holds the process in their head — the workarounds, the exceptions, the "you also have to remember to…". It works beautifully right up until that person is on leave, unwell, or leaves — and then it doesn't. ## The short version - Key-person risk = critical process knowledge living in one person's head. - It's common in businesses running on workarounds and undocumented steps. - The danger is invisible until the person is unavailable — then it's acute. - You reduce it by moving the knowledge into a system anyone can run. ## How does key-person risk build up? No one designs key-person risk — you grow into it. A capable person figures out how to keep things running despite imperfect tools. Over time, more of the "how" lives only with them: which spreadsheet to update, which step to do after which, how to handle the odd cases. The business quietly becomes dependent on their memory. It's often your best people who create the deepest risk, precisely because they're good. They absorb the mess so no one else has to think about it. The operation runs smoothly, so nobody notices that "smoothly" means "entirely through one person's head." The better they are, the more invisible the dependency — and the bigger the hole when they're gone. ## What does it look like when it bites? Consider a family-run manufacturer on the Gold Coast. Deb has run the office for twelve years. She knows which customers pay on time and which need a nudge, which supplier to call when the usual one is out of stock, the exact order jobs have to be booked so the factory doesn't jam, and the dozen little exceptions that never got written down because Deb just handles them. Then Deb has a fall and is off for six weeks. Suddenly nobody knows why a job that looks routine keeps getting bumped, why one customer's orders always need a deposit first, or how the end-of-month run actually works. The business doesn't stop — but it stumbles, badly. Deadlines slip, a supplier gets paid twice, a good customer gets treated like a stranger. The owner spends those six weeks reverse-engineering a system that lived entirely in one person's memory, under pressure, while still trying to run everything else. That's key-person risk cashing in. And notice: nothing was broken while Deb was there. The risk was invisible right up to the moment it wasn't. ## Why is it dangerous? - **Continuity** — if they're away, the wheels wobble; if they leave, they take the operation's manual with them. - **Bottleneck** — everything routes through them, so they can't take real time off, and the business can't move faster than they can. - **Fragility** — one illness or resignation, and you're rebuilding process knowledge from scratch, usually under pressure. There's a growth cost too. A business that depends on one person can't scale past that person's capacity. Every new customer, site or job piles onto the same head. Until the knowledge comes out of that head, the ceiling on the business is the ceiling on one person's time and memory. ## Isn't "but they'd never leave" enough? "But they'd never leave" isn't a plan. Even the most loyal person gets sick, takes holidays, has a family emergency, or eventually moves on. And it's unfair to them: they can't switch off, can't fully delegate, and carry a weight that isn't really theirs to carry. Relying on a single person to hold the operation together is a risk you're carrying whether or not you've named it — and it's a risk to them as much as to you. It also quietly affects what the business is worth. If you ever want to sell, step back, or bring in a partner, an operation that only works because of one irreplaceable person is a red flag to any buyer. A business that runs on documented, systemised process is worth more and sells more easily than one that runs on somebody's memory. Reducing key-person risk isn't just insurance against a bad week — it's building something that can stand on its own. ## How do you reduce it? The durable fix is to move the process out of the person's head and into a system — one that encodes the steps, handles the exceptions, and can be run by anyone with the right access. The knowledge stops being a person's memory and becomes part of how the business runs. That's different from writing a manual, which tends to go stale and unread. When the know-how is built into the software — the steps happen in the right order because the system guides them, the exceptions are accounted for because the system handles them — the process is followed by default, not by memory. That's the move from [tribal knowledge to a system anyone can run](/insights/articles/tribal-knowledge-to-a-system). It doesn't remove your experienced people — it frees them. Once the routine is held by the system, they stop being a walking single point of failure and start spending their time on the judgement calls that genuinely need them. Deb doesn't get replaced by software; she gets to take a holiday without her phone going off, and the business keeps running while she's gone. ## Related reading - [Workflow systems: the complete guide](/insights/articles/workflow-systems-complete-guide) — the pillar overview. - [From tribal knowledge to a system anyone can run](/insights/articles/tribal-knowledge-to-a-system) — how the knowledge gets captured. - [The true cost of spreadsheets holding your business together](/insights/articles/true-cost-of-spreadsheets) — where a lot of that hidden knowledge lives. ## The honest first step Reducing key-person risk starts with surfacing what only lives in someone's head. Mapping your operation — including the workarounds and exceptions — makes the invisible knowledge visible, which is the first step to building it into a system. The value is in what that mapping finds. *Tell us what you run, and we'll show you what's possible.*