Signs Your Operations Depend on One Person (and How to Fix It)

Every organisation has someone like her. She knows which customer gets special pricing, how to fix the stock report when it breaks, and why supplier payments go out on the 25th instead of the end of the month. When she takes two weeks of leave, the business does not stop, but it limps.

That person is usually loyal and badly overloaded, and they are rarely the cause. The cause is an operation that has quietly organised itself around one head instead of around clear processes and systems.

Eight warning signs to look for

Key person dependency rarely announces itself. It shows up in small, familiar moments. If several of these sound like your organisation, it is worth acting before the risk becomes a crisis:

• People wait for one person before acting. “Let’s ask Ahmad when he is back” is a common phrase, even for routine decisions.
• Leave is negotiated around the business. The person cannot take holidays during month-end, Ramadan season or the back-to-school rush, because nobody else can cover.
• Phone calls on days off are normal. Colleagues call during weekends or sick leave to ask where a file is or how to process an unusual case.
• Critical files live on one laptop or in one email inbox. Price lists, supplier agreements and reporting templates are not in a shared, managed location.
• Nobody else can explain the numbers. Reports go to management, but if a figure looks odd, only one person can trace where it came from.
• Customers and suppliers ask for them by name. Relationships that should belong to the company sit with an individual.
• New staff learn by shadowing only. There are no written procedures, so training depends on the expert’s time and memory.
• The person resists documenting. Sometimes from lack of time, sometimes because their knowledge feels like job security. Both are understandable, and both need handling with care.

Why this happens in growing organisations

In a company of fifteen people, having one person who knows everything is efficient. Decisions are fast, and there is no need for formal procedures. As the business grows to fifty or a hundred staff, the same arrangement becomes a bottleneck. Volume increases, exceptions multiply, and the expert spends the day answering questions instead of doing their own job.

Family businesses in Jordan and the Gulf often see this pattern twice: once with a long-serving employee who holds operational knowledge, and once with a family member who holds every approval. Both cases have the same root. Knowledge and authority were never moved from people into processes, documents and systems.

Take an engineering services firm in Amman with sixty employees. Its operations coordinator has been there twelve years. She schedules technicians, tracks spare parts, approves small purchases and knows every client’s site access rules. When she was off for three weeks after surgery, technicians were sent to the wrong sites, two clients were billed late and a site visit was missed because nobody knew that client required a security clearance letter in advance. None of this was in a system. All of it was in her head.

A practical plan to reduce the dependency

The aim is to keep the business running when the expert is away and to free them for work only they can do. Nobody is being replaced. Work through these steps in order:

1. List what only they do. Sit with the person for an hour and list every recurring task, decision and relationship they handle. Mark each one as daily, weekly, monthly or occasional, and note which would hurt most if missed.
2. Rank by risk. Combine how often each task happens with how much damage a failure would cause. A monthly payroll input and a daily dispatch schedule both rank high. An annual insurance renewal ranks lower, but still needs a reminder somewhere other than one person’s memory.
3. Name a backup for each high-risk task. Choose someone with the right level of access and judgement, and agree it openly with both people and their managers.
4. Document while doing, not after. The backup watches the expert perform the task and writes the procedure in plain steps, with screenshots where useful. The expert reviews it. This takes far less of the expert’s time than asking them to write documentation from scratch.
5. Reverse roles. The backup performs the task while the expert watches and corrects. Repeat until the backup can do it alone. Then update the written procedure with whatever was missing.
6. Move knowledge into systems. Client site rules belong in the client record. Special pricing belongs in the price list in the ERP (enterprise resource planning) system, not in someone’s memory. Recurring deadlines belong in a shared calendar or an automated reminder.
7. Test it. Ask the expert to take a planned week off without being contacted. Note every question that comes up and fix the gap behind it.

Handling the human side

This work can feel threatening to the person at the centre of it. Be direct about the purpose: the company values them, wants them to take proper leave, and wants their time spent on higher-value work. Recognise their contribution publicly, and if possible link their next step to a role that uses their experience, such as training others or owning process improvement.

Avoid treating documentation as an extra task to be done in the evenings. Agree protected time for it, and make the backup responsible for producing the written material. When the expert sees that the effort is shared and that their standing has grown, resistance usually fades.

Building operations that do not rest on one person

Book an hour with your key person next week and run the listing session from step one. It usually turns up a handful of tasks that would cause real damage if missed next month. Those are the tasks that need a named backup this week.

Our Operations Transformation service does this work with you: clear roles and ownership, practical SOPs (standard operating procedures) written with the people who do the work, and an operation that keeps running whoever is on leave.