An Employee's Vacation Can't Mean a Vacation for the Whole Process

SIGNAL 1: DECISIONS WAIT ON ONE SPECIFIC PERSON

Nobody approved the extra transport, nobody authorized overtime because there was no manager to sign off, a complaint sat unresolved because only one person understood what it was about — this is the most common pattern Skobało sees after vacation season. A good stand-in doesn't need to know every duty of the absent person, but they do need to be able to keep the primary process unblocked ("primary process blocked" is the outcome to avoid at all costs) — make day-to-day decisions, react to exceptions, and know who to ask for help, modeled on the "buddy system" borrowed from health-and-safety practice. If everything had to wait for one person's return, the organization didn't have a stand-in — it had a name written in a vacation spreadsheet.

SIGNAL 2: KNOWLEDGE LIVES IN SOMEONE'S HEAD, NOT IN THE PROCESS

"Only Paweł knows," "only Ania can do this" — so-called tribal knowledge is often invisible for most of the year, because someone is simply doing their job. Vacation reveals that the process isn't documented, data is scattered, and exceptions aren't recorded. It doesn't take ten binders of procedures — three short instruction sheets or a checklist on a shared drive is enough: a list of the most common exceptions, current contacts, what to watch out for. There needs to be a clear escalation path (if not Paweł or Ania, then who) and a stated location for where data lives — because it happens that someone closes their laptop for vacation, and something critical to the whole organization stays on that hard drive.

SIGNAL 3: RESULTS GOT WORSE

The most painful signal — core metrics drop, and sales is usually the first to flag it. The key question is why the result depended on one specific person's presence, and whether it really did — sometimes an objectively underperforming subcontractor is the real cause, not the process, so this is about honest analysis, not self-flagellation. If results decline whenever a manager or specialist is away, the process probably isn't stable — it's being stabilized by a person. Skobało cites a rule he once learned: you can tell a good manager by what happens when they're not at work.

SIGNAL 4: A SPIKE IN EMERGENCY ACTIONS

The plan got delivered — but at what cost? Extra transports, unplanned overtime triggered reactively, manual data patching, constantly shuffling people between processes, and escalations — plus calls to people on vacation, a practice Skobało has fought against for years, because one phone call can reset five days of rest. Delivering the order doesn't by itself mean the process worked correctly — it's worth calculating the real "vacation cost of instability" in overtime and express transport, because the organization pays for a lack of process resilience even when the customer ultimately gets their order on time.

SIGNAL 5: A BACKLOG MOUNTAIN WAITING ON RETURN

Hundreds of messages and unresolved decisions after returning don't necessarily mean failure — unless responsibilities were only frozen, not actually handed off. Protip for the next vacation: split tasks into three groups before leaving — those the stand-in must handle; those that consciously wait for the true owner (easier to live with when it's on a project timeline); and exceptional situations with a clear, pre-agreed escalation path at every level. A second, operational protip: read your inbox newest-first after returning, not chronologically — a good share of what flared up on day three or five of the vacation will already be resolved by the time you're back.

WHAT TO DO AFTER VACATION: FIVE QUESTIONS FOR A SHORT REVIEW

No big project is needed — a short meeting with the people returning from vacation, their stand-ins, and their direct managers, plus five questions: what stopped working or worked worse, what decisions did the team have to wait on, what knowledge did stand-ins lack, which problems generated cost or risk for the client, and what will we fix in the next two weeks. One-sentence summary of the episode: an employee's vacation can't mean a vacation for the whole process — if a process only works when one specific person is at their desk, it isn't stable yet.