Ana is the only person who really knows the Meridian account. She's been managing it for two years, she remembers why the delivery schedule changed in March, and she's the one who smooths things over when the client gets anxious. She's also on holiday for the next three weeks.
Nobody planned for this to be a problem. It just quietly became one, the way these things do — one renewal, one exception, one late-night email at a time, until a whole relationship lived mostly in one person's head.
This happens constantly, in every kind of business. Not because anyone did anything wrong, but because good people are so good at absorbing complexity that the complexity stops being visible. The company doesn't look fragile. It looks calm. Calm, because someone is quietly holding it together.
What a holiday actually tests
A two-week absence is a small, low-stakes way to find out something important: how much of your business depends on individual memory rather than on anything written down, shared, or connected.
Tasks can be reassigned easily enough.
Context can't.
The reasoning behind a decision, the history of a customer relationship, the small exceptions that were made and why... none of that transfers with a message saying "can you cover for me while I'm out." Someone can sit in Ana's seat but they can't sit in Ana's head.
Why this doesn't show up until it's tested
Experienced people are unusually good at covering for weak processes. They remember what the system doesn't. They know who to call, what the client actually wants versus what they say they want, which shortcuts are safe to take.
Althought that's a genuinely valuable skill, a business that runs on it is running on a person, not on a process. And a business running on a person finds that out the hard way eventually: when that person is on holiday, changes roles, gets promoted, or leaves.
August just happens to be the version of this test that comes every single year, on schedule, whether you're ready or not.
What the client actually notices
The Meridian account manager covering for Ana doesn't need to be as good as Ana. They need to know what Ana knows. If the client has to re-explain what was already agreed, or repeat a complaint they already raised, they will notice because the handover was incomplete.
An out-of-office reply solves the "who do I contact" problem. It doesn't solve the "does this person actually understand my situation" problem. That second one is the one that shapes whether the client trusts the company or just the individual they happened to build a relationship with.
Continuity has to be designed
Resilient organisations make operational knowledge accessible. Responsibilities are visible, customer interactions can be followed, decisions are recorded, and documents stay connected to the processes they support. The next action doesn't depend entirely on someone remembering that it needs to happen.
This doesn't make people less important, quite the opposite. When employees spend less time reconstructing context, searching for information and compensating for unclear processes, they can put more of their attention into the work that actually requires judgement, expertise and relationships.
This kind of continuity requires real decisions about how the organisation wants to work: where information should live, who is responsible at each stage, what should happen when that person is unavailable, and what the next person actually needs to carry on. These are management questions before they are technology questions.
Once those decisions are made, the right tools make them easy to follow through on. Made without them, the same tools just digitise the same dependency on Ana.
Where Odoo fits
This is the gap an integrated system like Odoo is built to close. CRM, Sales, Projects, Helpdesk and Documents connected to the same customer record mean that whoever picks up the Meridian account can see the actual history and not a summary someone had time to type up before leaving, but the real thing.
At Oxalyo, this is a core part of how we approach Odoo implementations. We look beyond the software configuration and examine how information, responsibility and decisions actually move through the organisation because digitalising a process without questioning how it works just preserves the same dependencies in a new system. The goal is to build processes that let people collaborate and hand off responsibility without having to rebuild context every time something changes.
Try it before your next holiday
There's a simple question worth asking this summer: pick one important customer, project or process, and imagine the person who knows it best is unavailable tomorrow. Could someone else pick it up without calling them - understand what's already been agreed, find the relevant information, and know what needs to happen next? Would the customer even notice a difference?
The answers can reveal more about the maturity of your processes than many formal audits.
Ana should be able to go on holiday and the Meridian account deserves to survive it without anyone noticing she was gone.
That is what operational continuity should look like - and summer is a very good time to find out whether you have it.