What Happens to Your Operation When One Person Is Out for Two Weeks?

If the honest answer is that quotes stall, exceptions pile up and people start texting them on vacation, that person has become the system. The work is not written down anywhere else, so it waits for them.

This is the first pattern in Friction, Found, our series on the friction we see most often inside growing companies. It is also the one owners tend to notice last.

What does it mean when one person is the system?

It means the rules for how work gets done live in one person's head instead of anywhere the rest of the team can reach. They know which customers get the old price, which vendor needs a call instead of an email, and which orders can skip a step. None of it is written down, because it never needed to be. They were always there.

Picture an office manager who has been with the company for fifteen years. Every quote crosses her desk. Every odd order gets walked over to her. New hires are told one thing in their first week: when in doubt, ask her. She is very good at the job. She is also the only place the job exists.

How can you tell if your operation depends on one person?

Look at where questions go. If most of them end at the same desk, the knowledge is there and nowhere else. Four signs show up together:

Questions wait. Work sits in a queue until one person is free to answer.
Their time off gets planned around, or quietly interrupted.
New people take months to become useful, because training is mostly learning what to ask.
The software says one thing and they say another, and everyone trusts them.

That last sign matters most. When the team trusts a person over the system, the system has stopped being the record.

What does it cost when the work runs through one head?

The cost is waiting, and most of it never shows up on a report. A quote that could go out today goes out Thursday. An exception that needs thirty seconds of judgment sits for a day. Nobody logs the delay, because nothing looks broken. Everyone is busy.

There is a second cost, and it lands on the person. They cannot take a real vacation. They are hard to promote, because nobody else can do what they do. Their own work gets done in the gaps between everyone else's questions.

The third cost only shows up once. When they retire, move or get sick, the knowledge leaves with them, and the company finds out how much of the operation was never written down.

Why does this happen in well-run companies?

Because it starts as a strength. Early on, having one person who knows everything is fast. They make good calls, they catch mistakes, and customers like dealing with them. Nobody decides to make them the system. The business grows, the volume grows, and the knowledge stays where it started.

New software rarely fixes it. A system gets set up around the official process while the real rules stay in the same head. The team keeps asking, and the new tool becomes a second place to type. We covered that failure in what a single source of truth actually requires.

What is the first move?

Write down what they know before you change anything else. Start with decisions, since that is where the waiting comes from.

Spend an hour with them and list the calls only they make: pricing exceptions, rush orders, vendor workarounds, customer quirks.
For each one, write the rule in two sentences. What they decide, and what it depends on.
Mark the ones someone else could make tomorrow with that rule in hand.

This is one page, and it usually fits in an afternoon. The same approach works for an owner, which we walked through in which decisions in your business only exist in your head.

One caution. Do this with them, not to them. The person who does the work has to define the process that feeds the record. If the rules get written by someone else and handed down, the page will be wrong in small ways, and the team will go back to asking.

What if there is too much to fix and no obvious place to start?

Then map before you pick. When the list of problems is long, the first job is a picture of how work moves today: who touches it, where it waits, and who it waits on. A 30-minute process map your team draws is enough to show which queue is longest.

When the pain is specific, skip the map and go straight at it. Knowing which of those two situations you are in is most of the decision.

What does it look like when this gets fixed?

The work stops waiting on one person, and that person gets their own job back.

One documented example from our work: an events business ran its whole operation out of one spreadsheet, 50 worksheets wide, that one person understood. A formula that broke in one tab threw errors into the others. We replaced it with a platform built on a single database, automated the event emails from invitation through follow-up, and added a public page where people sign up on their own. The owner got about 8 hours a week back.

The knowledge did not disappear. It moved out of one head and one fragile file, into a place the business could rely on.

Does fixing this mean buying new software?

Usually not at first. The rules have to be written down before any tool can hold them, and writing them down often removes most of the waiting with nothing else changing. If a system change is needed after that, it is smaller and better defined.

Will the person feel like they are being replaced?

Only if it is handled that way. Most people in this seat are tired of being interrupted and would like a week off without their phone. Say that plainly, give them credit for what they have been carrying, and let them decide how the rules get written. The goal is fewer questions reaching them. It is not less of them.

Where should you start if you see this in your own company?

Start with one question: what would wait if this person were out for two weeks? The answer is your list.

If you would rather not sort it out alone, that is what a Friction Audit is for. Give us 45 minutes and we will walk through where your work waits on one person, what the waiting costs, and what to move first. The Leverage Map that comes out of it is yours to keep.