What Happens When Your Ops Manager Takes a Two Week Holiday?

“I write these guides from what we see in production, not from what sounds good in theory. If something doesn't work for real businesses in the UAE, it doesn't make the page.”

The Key Person Problem

Every business has them. The person who knows where everything is. How the shipping schedule works. Which suppliers need to be paid first. Why the system requires that one extra step that nobody documented. The person whose brain is the company's operating manual.

This isn't a compliment to that person. It's a structural failure. When critical business knowledge lives in one human brain, the business runs on biological infrastructure with a 100% guaranteed failure rate. People get sick. They quit. They burn out. They take holidays. They retire.

And when they're gone, even temporarily, every process they owned slows down, breaks, or stops entirely.

What Systems Replace

The solution isn't making people less important. It's making their absence less catastrophic. That's the difference between a business with documented systems and one running on institutional memory.

A documented system means the approval workflow is written down, not memorized. The shipping schedule runs from a shared dashboard, not a personal spreadsheet. Supplier payment priorities are configured in the accounting software, not stored in someone's head. Client reporting runs automatically, not from a personal laptop folder.

The Ras Al Khor company spent AED 45,000 after the crisis building what they should have built before it. A centralized operations platform that codified every process their ops manager had been running manually. Approval workflows with automated routing. A shipping management dashboard visible to the entire team. Supplier payment schedules in the system with automatic reminders. Client reports that generate from live data instead of manual compilation.

When the ops manager returned, his job changed. Instead of being the engine, he became the mechanic. He optimized processes, handled exceptions, and trained the team. The daily operational grind ran without him because it ran on systems, not memory.

The Holiday Test

You don't need a crisis to identify this risk. Give your key operations person a Friday off. Don't prepare. Don't brief anyone. Just let it happen. See what breaks. See what slows down. See who calls you confused.

That one day test reveals exactly how dependent your business is on individual people instead of systems. If nothing breaks, your operations are genuinely systematized. If three things break before lunch, multiply that by 10 for a two week absence.

Most Dubai SMEs with 15 to 80 employees have between 2 and 5 key person dependencies. Each one is a ticking clock. Not if they'll be unavailable, but when.

Building Resilience Before the Crisis

The cost of building operational resilience before a crisis is roughly 30% of what it costs after one. The Ras Al Khor company's AED 143,000 in damage plus AED 45,000 in system building totals AED 188,000. If they'd invested AED 45,000 six months earlier, the AED 143,000 never happens.

Start with your most critical role. Map everything that person does. Identify which tasks require their judgment versus which tasks run on rules they've memorized. The rules based tasks go into automated systems. The judgment based tasks get documented with decision frameworks so someone else can handle the straightforward cases.

Ask yourself honestly: if your most critical person didn't show up tomorrow, which processes would stop?

That list is your priority.