Taming the Email Flood: Rules for the Team

Why the email flood is not a personal problem

Ask in the office of a small business what takes up the most time, and you often hear the same answer: emails. Most advice against it is aimed at the individual. Fixed times for the inbox, folders, filters, notifications off. That helps. But it overlooks the fact that a large part of the flood arises within one's own team, through copies to everyone, replies to all, and queries a short call would have settled.

This leads to the guiding question of this guide: what shared rules does a team need so that internal emails decrease and the remaining ones work faster, without anything important getting lost? To answer it, we clarify the terms, present a thinking model from the economics of common goods, review the findings, weigh two perspectives, and describe an email agreement with a four-week rollout.

A team's attention is a common pasture. Every unnecessary copy puts one more sheep on it.

Terms: email overload, interruption, availability expectation

Email overload describes a situation in which the number of incoming messages and the time needed to handle them noticeably crowd out the actual work. An interruption is an event that stops an ongoing activity and demands another, such as a notification of a new email. An availability expectation is the stated or unspoken assumption that messages will be read and answered within a certain time.

The guide on internal communication classifies a business's channels according to media richness theory. There, email is a lean, asynchronous channel for information with attachments, summaries, and everything that goes outside. It is unsuitable for discussions with many rounds. This guide builds on that and asks how a team uses the channel together.

The thinking model: the tragedy of the commons

In 1968, the biologist Garrett Hardin described an image that has since been used in economics and politics: the tragedy of the commons. A commons is a pasture owned jointly by all the farmers of a village. For each individual farmer, it pays to put one more sheep on the pasture, because the benefit is theirs while the damage from overgrazing is spread across everyone. Because everyone calculates this way, the pasture is eventually bare. Nobody acted unreasonably, yet everyone loses.

A team's attention works like this pasture. For the sender, a copy to five colleagues costs one click and protects them from the reproach of not having informed someone. For the five recipients, it costs perhaps ten minutes and five interruptions in total. Whoever calculates this way acts sensibly. When everyone calculates this way, the flood arises.

Hardin himself saw only two ways out: division or regulation from above. Later research, especially the work of the economist Elinor Ostrom (1990), showed a third: communities that manage their commons themselves through rules they have agreed on together, monitor visibly, and enforce in a friendly but noticeable way when they are broken. For a team, this means: the rules for emails should not be announced by the owner but agreed by the team.

What studies show about email, discipline, and expectations

That the way email is handled affects strain is well documented. Russell, Jackson, Fullman, and colleagues (2024) analyzed 62 empirical studies on work email. They found four behaviors that support both performance and well-being: agreeing on availability, sorting regularly, sending only what is relevant, and writing considerately. Two of these four concern not the recipient but the sender.

How costly it is to handle the flood with discipline alone is shown by a field study by Russell, Woods, and Banks (2017). Of 74 employees recruited from four organizations, 52 remained in the analysis. For half a working day, they recorded every email that interrupted them, 376 messages in total. Conscientious people were more likely to leave notifications unread in order to finish their current task, and thus came closer to their work goals. In return, their mood worsened. The authors interpret this as a trade-off: whoever resists the interruption pays with self-control.

Kushlev and Dunn (2015) showed in an experiment with 124 adults, described in the guide on the owner's self-organization: those who checked their email only three times a day experienced less stress than in a week without limits. Fixed times therefore help, but they are easier when the environment does not expect immediate answers.

It is exactly these expectations that Geldof, Verlinden, Baillien, and DeSmet (2026) studied. Their systematic review covers 24 papers with 25 studies on how an organization's culture and climate around digital availability outside working hours relate to well-being. In one of the included studies, higher expectations of reading email after hours went along with markedly less detachment from work and more emotional exhaustion. Several studies stressed the role-model function of managers: what they do themselves has a stronger effect than any written rule.

Self-discipline or team rules? Two perspectives

The first perspective says: email is a matter for the individual. Everyone knows their own work best, and what is noise for one is necessary information for another. Rules for everyone are patronizing and cannot be enforced anyway. This is supported by the fact that fixed checking times actually worked in the experiment by Kushlev and Dunn.

The second says: email is a matter for the team. Whoever wants fewer emails has to start with the senders, and those are colleagues. Without a shared expectation of response times, everyone who keeps fixed times remains worried about missing something. This is supported by the findings on the cost of self-control and on the effect of expectations.

I consider the second perspective the more important, because it makes the first possible in the first place. Fixed times for the inbox are good, but they demand willpower as long as the team expects immediate answers. An agreement on response times takes this burden away. By the logic of the commons, this is not an intrusion on individual freedom but the protection of a shared resource.

The email agreement: seven rules for the team

The tool of this guide is the email agreement: seven rules on one page that the team adopts together. They complement the three-question rule and the accompanying rules from the guide on internal communication and adopt its response times: chat within two hours during core hours, email within one working day, urgent matters by phone.

• Recipients: only those who have to act are in the To field. Those who are only informed are copied or receive the summary on Friday.
• Reply all: only if all recipients have to do or know something. Thanks and confirmations go to the sender alone.
• Subject: the subject says what the recipient should do and by when, such as 'Approve Müller quote by Thu 12 noon'.
• Two rounds: if a question needs more than two replies back and forth, call or arrange a short meeting. The result is then summarized in an email.
• Tasks: tasks are not assigned by email but entered in the shared task list. The email at most refers to it.
• Quiet hours: no reply is expected after work and at weekends. Whoever writes late schedules sending for the next morning.
• Example: owners and managers keep to the rules first, especially quiet hours and copies.

1. Week 1: count the volume

   For one week, everyone counts their internal emails and marks how many they received only in copy and how many required action.

2. Week 2: agree on rules

   At the team meeting, the figures are shown and the seven rules discussed, adapted, and adopted. Whatever the team does not support is dropped.

3. Weeks 3 and 4: try it out

   The rules apply. Whoever notices a breach points it out in a friendly way, without reproach. Distribution lists and groups nobody needs are closed.

4. End of week 4: review

   Count for a week again and compare. Rules that change nothing are dropped. Rules that work become part of onboarding new colleagues.

A worked example shows how much this can achieve for an office assistant in a business with 15 employees. The figures are freely chosen.

What follows beyond email, and where the limits lie

Whoever contains the email flood shifts some messages to other channels. That is intended, but only if each channel has a clear purpose. Otherwise the flood moves into the chat. The guide on reducing tool sprawl describes the guiding rule that applies here: one piece of information, one place. For customer inquiries that land with several people, a shared inbox or a ticket system can help, as the guide on bundling customer inquiries shows.

One limit lies with external emails. Customers and suppliers do not follow the team's agreement. For them, the business's own commitments on response times apply, not the internal rules. A second limit is distributed work. Whoever does not sit in the same office cannot just pop over, and the two-round rule then needs a fixed path for short calls. How that works is described in the guide on organizing distributed teams.

Conclusion: how does a team tame the email flood?

We set out to ask
shared rules a team needs so that internal emails decrease and the remaining ones work faster. The answer follows from the thinking model of the commons: the flood arises from many small, sensible decisions by senders, and that is why personal discipline alone does not help. According to the findings, it is even costly as long as the environment expects immediate answers.

What works is an agreement the team adopts itself: few recipients, no reply all without reason, a subject with action and deadline, a conversation after the second round, tasks in the task list, quiet hours, and leadership that goes first. A team's attention is limited. Whoever protects it gains time not for emails, but for the work.

The next step

1. Count your internal emails for one week and mark which came only in copy.
2. Ask two colleagues to do the same, and compare the figures at the next team meeting.
3. Present the seven rules and let the team decide which should apply.
4. Close distribution lists and groups nobody needs.
5. From now on, keep to quiet hours yourself and send late messages on a delay.