Back to blog
Coverage

Taking a Real Holiday as a Manager (the Team Survives)

5 min read
manager holidaydisconnecting on vacationdelegating authoritymanager time offright to disconnect manager

The short version

  • Managers check messages on holiday for a rational reason: they are the decision route, and nobody else has the authority.
  • Checking is what causes the messages. Once the team learns you read things, the threshold for contacting you drops to nothing.
  • Delegate authority with written limits, name one escalation route, and let the questions be answered from what you wrote down.
  • A manager who cannot take two weeks off has a delegation problem, and the team pays for it every week of the year.

Every manager has a version of this story: two weeks booked, phone checked at the gate, a decision made from a hotel lobby, a small argument about it at home. It is usually explained as being unable to switch off. The more accurate explanation is structural.

"I checked Slack from the airport."

Why you check from the airport

Three real reasons, none of which are about willpower.

You are the decision route. If nobody else has the authority to approve, unblock, or commit, then your absence stops work, and you know it. Checking is the cheapest way to prevent a fortnight of stalling.

You hold context nobody else has. Half the messages will be questions about things you know and have not written down anywhere, and answering them takes you thirty seconds and would take somebody else a day.

And there is a genuine anxiety that you will return to something that went wrong while you were not looking. That anxiety is worse than checking, so checking is the relief.

Checking causes the messages

Here is the part that is worth internalising, because it inverts the usual framing. The volume of holiday messages is a function of whether you are known to read them.

If you reply once on day two, every person who was hesitating about whether to contact you now knows it is acceptable. By day five you are effectively working. Conversely, a manager who is genuinely unreachable finds that the team resolves almost everything, because they have to, and the small number of things that genuinely could not wait go through the escalation route.

This is not a claim that the team would prefer you unreachable. It is an observation that the threshold people apply is set by your behaviour, not by your stated wishes.

Delegate the authority, not the inbox

The mistake is delegating the work and keeping the authority. That produces a deputy who can do everything except decide, which means everything reaches you anyway.

Write the limits down before you go, specifically, and tell the whole team rather than just the deputy.

Marek decides: scope cuts within the current sprint, hiring loop scheduling, spend up to 2,000 EUR, anything a customer needs answering this week.

Waits for me: the Q4 roadmap commitment, the contractor renewal, anything involving a person's role.

Reaches me: production down for more than an hour, or anything legal. By phone, from Marek only.

Three lines. The middle one is what makes the first credible, and the third is what lets you put the phone away, because you know the route exists and that it is narrow.

What the team actually needs from you

Sort the holiday traffic a manager receives and it splits cleanly. A small number of genuine decisions, which is what delegation handles. A rare emergency, which is what the escalation route handles. And a large number of questions about context: what did we agree with that stakeholder, why did we drop that approach, where does this stand.

That third category is the volume, and it does not need your judgement. It needs your record. With StandIn, the ninety-second brief you confirm at the end of each day accumulates exactly this: decisions made and why, current state, open questions, commitments. While you are off, your StandIn answers from it in your words, with a source under every answer, clearly labelled, and it never guesses. When the answer is not there, it says so and names Marek.

So the team gets its context without you, Marek gets the decisions he was given authority for, and the only thing that reaches you is the thing you agreed would. See retire your out-of-office.

Log off like you mean it

Two practical moves for the last day. Do not write an out-of-office that promises you will reply when you are back, because that is a delay rather than an answer, and it invites people to queue things for you. And tell the team explicitly that you will not be reading messages, which sounds obvious and is almost never said out loud.

There is one more reason to do this properly, beyond your own fortnight. A manager who visibly works through their holiday sets the actual norm for everyone who reports to them, whatever the policy says. Nobody on your team will take a real break if you do not.

Common Questions

How can a manager actually disconnect on holiday?

Delegate specific decision authority in writing, name one narrow escalation route, and make sure context questions can be answered from what you already wrote down. Willpower is not the constraint; being the only decision route is.

Is it irresponsible not to check in?

It is irresponsible not to prepare. Once authority is delegated with written limits and an escalation route exists, checking adds very little and costs a great deal, including lowering the bar for everyone else to contact you.

What if my deputy makes a decision I disagree with?

Accept it unless it is expensive to reverse, and treat the disagreement as calibration for next time. A deputy who is overruled on return learns that their authority was decorative, and next time everything will wait for you again.

How long before the holiday should I set this up?

Two weeks, so the deputy makes some decisions while you are still there. Handing over authority on the final afternoon means their first real decision is taken alone and under pressure.

When you're off, your StandIn is on.

It answers your teammates' questions from work you've already done, in your words, with a source under every answer.

You might also like