Daimler Mail on Holiday: Should Vacation Email Be Deleted on Arrival?

The room

The psychology: vacation fade-out effect

Vacation research asks a blunt question: how long does a holiday’s benefit last? Jessica de Bloom and colleagues followed 96 Dutch workers before, during and after a winter sports vacation. On five of seven indicators, including mood, tension, energy level and satisfaction, the workers reported improvements during the holiday. By the first week back at work, the measures had generally returned to their pre-vacation levels. The authors titled their paper accordingly: lots of fun, quickly gone.

What speeds the fade-out? Jana Kühnel and Sabine Sonnentag studied 131 teachers and found that work engagement rose and burnout scores fell after vacation, then faded within a month. Higher job demands after the vacation made the benefits fade faster. Burnout here is the study’s questionnaire measure; the World Health Organization’s ICD-11 describes burn-out as an occupational phenomenon resulting from chronic workplace stress that has not been successfully managed, not as a medical condition. Charlotte Fritz and Sabine Sonnentag, studying 221 university employees, found that high workload right after vacation was related to higher exhaustion on return and two weeks later.

This is where the inbox comes in. A backlog of several hundred emails is a job demand waiting at the door. It lands on the first day back, exactly when the research suggests demands do most to erase what the holiday gave. It also reaches into the holiday itself, because a growing inbox invites checking in. Daimler’s rule addressed both sides at once: for those who used it, nothing accumulated, so nothing had to be watched from the beach and nothing waited on return. Porth’s talk of a clean desk is a plain-language description of reducing post-vacation demands.

Why smart people fall for it

Three mechanisms help explain why deleting holiday email, rather than simply hiding it, changes what a vacation and the return from it look like.

1. 1

   The backlog is a return-day demand

   Held mail still lands on the first day back. Deletion with a redirect removes the kind of post-vacation demand that research links to faster fade-out.

2. 2

   A growing inbox invites checking in

   When messages pile up, checking during the holiday feels like damage control. If nothing accumulates, there is nothing to keep under control.

3. 3

   The redirect hands the decision back

   The automatic reply tells senders who can help now. Deciding whether a message still matters becomes the sender’s job, not the absent employee’s.

What did Daimler Mail on Holiday actually change?

Much of the coverage in 2014 described Daimler as deleting its employees’ holiday email. That is accurate, but it leaves out the design choices that made the rule workable. It was optional: each employee decided whether to switch it on. It came with a mandatory redirect, so no sender was left with silence. And it sat alongside board principles telling managers not to expect constant availability, which addressed the expectation behind the email, not only the mailbox.

The opt-in design has a clear logic. Some roles cannot hand everything to a deputy, as Brenscheidt warned, and some employees prefer to keep their mail and deal with it later. Forcing deletion on them would have been a harder sell to staff and to the business. Making it optional also made it easier to agree: the works council gained a protection employees could claim, and those who wanted to work as before could do so.

The cost of opt-in is that it may leave the hardest cases untouched. The employees who feel most pressure to stay reachable are plausibly the least likely to switch on a tool that tells customers their message has been deleted. Without usage data, Daimler could not tell whether Mail on Holiday reached those people or mainly served those who would have rested anyway. That is the central unanswered question of the case.

Deletion also shifts work to senders. A message that matters has to go to the deputy or be resent after the return date, as the sample auto-reply described by Marketplace made clear. That is a small cost for each sender and arguably a useful filter, since much holiday email may not need the absent person at all. But it depends on deputies being real, briefed and available, which is an organisational task rather than a software setting.

Why delete email rather than hold it until people return?

Option D, a locked mailbox that releases held mail on return, would also have stopped people checking in from holiday. In that sense it is stronger than Daimler’s choice. But it leaves the whole backlog waiting on the first morning back, which the vacation research suggests is the worst moment to add load. Kühnel and Sonnentag found that higher job demands after vacation accelerated the fade-out, and Fritz and Sonnentag found that workload just after vacation was related to higher exhaustion on return and two weeks later.

Deletion with a redirect changes the shape of the problem. Work that arrives during the absence goes to someone who is present, or it is resent later by people who still need it. The returning employee faces the work that is genuinely theirs, not a record of everything that happened while they were gone. Porth’s phrase, a clean desk, is about that difference.

There is a trade-off in information. Held mail keeps a complete record. Deleted mail loses context the employee might have wanted, such as threads they were copied on or decisions taken while they were away. Deputies and handover notes can recover some of it. SAP’s approach, as described in 2012, kept team discussion on shared platforms that people could review on return, which preserves context without filling a personal inbox.

None of these studies tested email deletion directly. They measured vacation effects and post-vacation workload, not mailbox settings. The link to Daimler’s rule is an inference: if workload on return speeds the fade-out, a policy that removes a predictable part of that workload is a reasonable lever. Whether it worked at Daimler is unknown, because the company did not measure it.

How would a modern team decide?

A modern team would start with the deputy, not the software. Deletion and redirects only work if every absence has a named, briefed person who can act on what arrives. That means handover rules, real capacity for deputies, and clarity about which decisions can wait two weeks.

It would then decide where the default sits. Daimler chose opt-in, which respects choice but leaves uptake to individuals. A team could instead make the redirect standard for all leave and let employees opt out, or make it standard only for groups whose work can be fully delegated. Where the default sits shapes who ends up protected, so the choice should be made explicitly, agreed with employee representatives and reviewed.

Third, it would measure. Daimler kept no usage statistics, which left the policy impossible to evaluate. Today a team can count how many absences use the setting, how much mail is redirected, how often senders resend, and how much email employees open while on leave. Short surveys before and after vacations, similar in spirit to those used in the fade-out studies, would show whether returns are getting easier.

Finally, it would look at the first week back. If post-vacation demands erase the gains fastest, then protecting the return matters as much as protecting the holiday. That points to organisational choices: fewer meetings on the first day, time set aside to catch up, and deadlines that do not fall on the first morning after leave.

The manager's playbook

1. Name and brief a deputy for every absenceMake handover a standard step of approving leave, and give deputies the time and authority to act on what arrives.
2. Redirect senders instead of storing a backlogUse automatic replies that name who can help now, and say clearly whether the message will be read later.
3. Choose the default deliberatelyDecide with employee representatives whether deletion is opt-in, opt-out or standard for certain roles, and record the reasons.
4. Put availability expectations in writingTell managers, as Daimler’s board principles did, that constant availability is not expected, and have senior staff follow the same rule.
5. Protect the first week backLimit meetings and deadlines on return days, and track email read during leave and workload after it.

Questions people ask