Building a Bench: No Single Point of Failure
Why this matters
Every small shop has a few people who, if they did not show up Monday, would bring part of the business to a halt. The one tech who knows the commercial accounts. The office person who is the only one who can run payroll. The owner who holds every password and supplier relationship in their head. Each of those is a single point of failure, a place where one absence stops the work. They feel like loyalty and efficiency right up until someone is sick, quits, or gets hurt, and then they are a crisis. Building a bench means making sure no one job, account, or piece of knowledge lives in exactly one head.
What a single point of failure looks like
A single point of failure (a spot where one missing person or thing stops everything) hides in plain sight because it works fine every normal day. Common ones in a field-service shop:
- The only person who can do a task. One tech certified on a system, one person who knows the invoicing software, one estimator.
- Knowledge that lives in a head, not anywhere else. The quirks of a big customer, the workaround for a flaky piece of equipment, why a job is priced the way it is.
- Relationships only one person holds. A key supplier who only deals with the owner, an inspector everyone leaves to one tech.
- Access nobody else has. Passwords, keys, accounts, the alarm code.
The test for each: if this person did not come in for two weeks, what breaks? Make that list. It is your risk map.
Why owners build these without meaning to
Single points of failure are not laziness, they are the natural result of how a shop grows. The fastest way to get something done is to give it to the person who is already good at it, every time. That is efficient today and fragile over time. The owner especially accumulates these because saying "I will just handle it" is always the quickest answer in the moment. Knowing the pattern is how you catch yourself doing it.
Cross-training: more than one person per critical job
The core fix is cross-training, making sure at least two people can do anything the business cannot run without. You do not need everyone to know everything. You need a depth of two on the things that would stop the work.
| Approach | What it gives you |
|---|---|
| Primary plus backup | One owner, one trained backup per critical task |
| Rotation | People periodically swap duties so skills stay fresh |
| Shadowing | The backup works alongside the primary on real jobs |
| Pairing on big jobs | Two techs on the high-stakes work so knowledge spreads |
A backup who was trained once a year ago and never used it is not a real backup. The skill has to be exercised, even occasionally, or it is theory.
Get the knowledge out of heads and onto paper
People are mortal and they leave. The knowledge they hold should not leave with them. You do not need a binder for everything, but the few things that would cause a crisis if forgotten belong somewhere durable:
- Customer and account notes in the job or customer record, not in one tech's memory. Access quirks, history, who to ask for, what went wrong last time.
- Process notes for anything done rarely but critically. Year-end tasks, how to handle a specific recurring problem.
- Why, not just what. The reasoning behind a price, a vendor choice, a workaround. The what can be relearned. The why is what gets lost.
Capture it as you go, in the normal flow of work, not in a heroic documentation project that never gets finished.
Solve the access problem before it is an emergency
Access is the single point of failure that turns an inconvenience into a disaster. If one person holds the only copy of a password, a key, or an account login, their absence locks everyone out at the worst time. Use a shared, controlled place for credentials and access, so that losing a person never means losing the keys to the business. This is also a security and continuity issue: when that person leaves on bad terms, you want to be able to cut access cleanly, which you cannot do if you do not even know what they hold.
The owner is usually the biggest single point of failure
Be honest about your own role. In most small shops, the owner is the largest single point of failure by far: the relationships, the pricing judgment, the supplier deals, the institutional memory, all in one head. That is exactly why the business cannot run without you and why you cannot take a real vacation. Reducing your own indispensability is not a threat to your job. It is the only path to a business that is worth more than your daily labor and that you can someday step back from or sell.
Where to start
You cannot fix every single point of failure at once. Rank them by damage: what would hurt most if that person vanished tomorrow? Start at the top. Pick the one whose absence would be the biggest fire, build a backup and write down the knowledge, then move to the next. A bench is built one critical role at a time.
References
- See related: Owner-Vacation Readiness: Can It Run Without You?
- See related: Onboarding a Process, Not Just a Person
- Trade-standard practice for business continuity and risk management