There’s a situation an owner often misses for years, because it looks like stability. One employee knows every password, holds the whole process in their head, talks to the key suppliers, and simply “keeps things running.” When everything in your business depends on one person, it feels like you’ve saved on headcount and bureaucracy. In reality, you’ve quietly built up a debt — and one day you’ll have to repay it all at once, at the worst possible moment.
This risk even has an engineering name: the “bus factor.” The question is simple and uncomfortable: how many people would have to “get hit by a bus” — quit, fall ill, burn out, fall out with you — before the work grinds to a halt? If the answer is “one,” you don’t have a team or a system. You have a single point of failure, and your money, your clients, and your reputation are all tied to it.
Why It Looks Like Savings But Is Really Hidden Debt
The all-rounder who “carries everything” genuinely pays off at first. No need to hire more people, no need to write procedures, no need to split up access. They’re fast, because the context lives in their head rather than in documents. You get used to every question being answered with “just ask Olia.”
The catch is that this saving only holds while nothing goes wrong. You don’t pay for duplication or for writing things down — but instead you quietly pay a higher price for risk. And that risk isn’t linear: it grows silently over years, then materializes all at once. A two-week illness in peak season. A sudden resignation after a conflict. An offer from a competitor. The plain burnout of a person who has been “everyone” for years.
The moment that key person disappears, you suddenly learn how much rested on them alone: where the access to email and ads lives, how the price is actually calculated, what was promised to whom verbally, why “this client is special.” The business doesn’t stop cleanly — it starts failing detail by detail, each one small on its own, yet together they paralyze the work.
How to Measure Your Dependency on One Person
Before you fix anything, it’s worth measuring it — calmly, without emotion or blame. A few simple questions give you an honest picture.
First, access. List every critical system: email, domain, hosting, ad accounts, online banking, CRM, point of sale, social media, the client database. Next to each, note who has access. Wherever there’s only one name, that’s a red line.
Second, knowledge. Which processes exist only as a spoken “this is how we’ve always done it”? Pricing, order handling, returns, dealing with suppliers — if it isn’t written down anywhere, it lives in a single head.
Third, the absence test. Honestly imagine this person goes on holiday for two weeks and is completely unreachable. What stops on day one? Day three? After a week? Whatever breaks fastest is exactly where you’re most fragile.
Once you’ve written this out, the vague dread of “everything rests on one person” turns into a concrete list. And a list can be worked through, item by item.
Where to Start Reducing the Risk
The main mistake at this stage is trying to rewrite everything over a weekend. It scares the team, angers the key person (“so you don’t trust me”), and almost always stalls. Dependency should be reduced gradually, starting with whatever would hurt most.
Start with access. It’s the fastest, cheapest move with the biggest effect. Access to email, the domain, advertising, banking, and the client database should belong to the business, not to a specific person, and should have at least two owners. This isn’t about distrusting an employee — it’s about an account never becoming a hostage to one person’s mood or health.
Next, critical processes. Not all of them at once — just the three or four the business can’t earn without: how an order is taken and fulfilled, how the price is calculated, how a customer problem is handled. These need to be captured so that someone else can repeat them step by step. Not a hundred-page manual, but a working description that people actually read and actually follow.
And separately, the knowledge that lives nowhere but memory. The quirks of specific clients, the arrangements with suppliers, the history of “why we decided it this way.” This is the most fragile part, because you can’t see it until it’s already gone, together with the person.
The Role of a System: Keeping Knowledge Out of One Head
Writing processes down is a right step, but not enough. Paper and files in someone’s messenger age, get lost, and settle right back “in one person’s head.” Real resilience comes from a system where knowledge and actions live by default, not as one employee’s goodwill.
In practice that means a few things. Orders, clients, and agreements sit in a shared place, not in personal chats. The price is calculated by transparent logic you can see, not “however Olia worked it out.” Access is granted by role, so when someone leaves you close one account instead of frantically recalling ten passwords. The routine a person used to remember either runs on its own or prompts someone to do it.
We’ve been building systems like this for Ukrainian small and mid-sized businesses since 2018, running them on our own infrastructure and supporting them afterwards — precisely because we’ve seen, dozens of times, how everything ends up resting on one person and how that story ends. The goal is simple: the business should belong to its owner, not to the employee who accidentally became indispensable.
An “Indispensable” Employee Isn’t a Compliment
It’s worth naming one more side of this honestly. The person everything rests on is trapped too. They can’t take a proper holiday, they’re afraid to get sick, they spend years carrying what should long ago have become a system. “Indispensable” sounds like praise, but in practice it’s burnout and quiet tension in the relationship with the owner.
Lowering the bus factor benefits both sides. The owner stops being a hostage, and the key person earns the right to be ill, to rest, and to grow instead of forever patching holes. Shared responsibility isn’t about replacing someone. It’s about a business that can breathe without one specific person on hand 24/7.
If you recognize your own situation, start small. Draw up that same list of access points and critical processes. And if you’d like an outside view to calmly map out exactly where your business is thinnest, that can begin with a conversation or a short brief — no commitment, just a way to see the whole picture at once.