Email, messages and the response time problem

Most workplaces have converged on an unstated expectation of rapid response to messages, which nobody agreed to and which imposes a substantial cost.

Where the cost lands

An expectation of rapid response requires monitoring, and monitoring is incompatible with concentration.

Which means the norm does not merely consume the time spent replying. It prevents any period of the day from being usable for work requiring depth, because the monitoring never stops.

The cost is therefore not proportional to message volume. Even a low volume, if it must be watched continuously, produces the same fragmentation.

How the norm forms

Nobody decides it. It emerges.

Someone replies quickly. Others notice and match. Rapid response becomes a visible signal of diligence. Not matching it becomes conspicuous.

Senior people sending messages in the evening — frequently while explicitly saying no reply is expected — accelerate it, because the stated expectation carries less weight than the observed behaviour.

Which is why delayed sending is genuinely useful for anyone senior: it removes the signal regardless of when the work happened.

What can be agreed instead

The productive intervention is a team agreement rather than an individual practice, because an individual deviating from a norm bears a cost.

Explicit response times by channel. Email within a day. Chat within a few hours. Phone for anything urgent.

Stating this converts an implicit expectation into an explicit one, and explicit expectations are generally more relaxed than implicit ones because nobody would defend the implicit version out loud.

A convention for genuine urgency. If everything arrives through the same channel, everything is urgent. A separate route for actual urgency lets the ordinary route slow down.

Notification defaults off, with people opting in rather than out.

No expectation outside working hours, backed by senior people visibly not responding rather than saying it.

Individual practices that survive a normal workplace

Check at defined times rather than continuously. Three times a day is sufficient for most roles and feels alarming for about a week.

Close the client while working. Not minimised — closed.

State your pattern. A signature or status noting that you check at particular times sets expectations rather than leaving people guessing.

People are generally accommodating about a stated pattern and frustrated by an unpredictable one.

Handle each message once. Reading, deciding to deal with it later, and rereading it three times is a large hidden cost.

Writing messages that reduce the load

The other half, and it is the half within your control.

State what you want in the first line. A message whose purpose is unclear generates a clarifying exchange.

Say whether a response is needed. "No reply needed" is a gift and costs three words.

Put a deadline where there is one, and do not put one where there is not — false urgency is corrosive.

Ask one question per message. Multiple questions reliably receive one answer.

Use the subject line to state the topic and the action.

Copy fewer people. Each additional recipient multiplies the total time consumed and reduces the probability that any individual acts, because responsibility diffuses.

The meeting substitution

Worth noting because the two problems interact.

Some organisations reduce email by holding more meetings, which is generally a poor trade — a meeting consumes everyone's time simultaneously and produces no record.

Others reduce meetings by moving everything to chat, which produces continuous interruption instead.

The useful principle is to match the channel to the need: decisions requiring discussion in a meeting, information in writing, and urgent matters through a route reserved for them.

Most organisations use whichever channel is habitual regardless of the need, which is where most of the waste comes from.

Setting the expectation explicitly

Most response-time pressure is inferred rather than stated, and inferred expectations drift upward.

Saying plainly that you check messages twice a day, and that anything urgent should come by phone, resolves it in one sentence.

Almost nobody objects, because the actual requirement is predictability rather than speed. People can work with a colleague who replies within a day; they cannot work with one whose reply time is unknown.