Response Times and Communication Norms

Ask five people on a distributed team how quickly a message should be answered and you will get five answers. That gap produces more anxiety and more unnecessary interruption than any tooling problem.

The problem, precisely

Without a stated norm, everyone infers one — usually from the fastest responder they have observed.

The consequences are predictable. Some people monitor chat continuously because they believe they must. Others take a day and are quietly considered unreliable. Senders cannot tell whether silence means "busy", "on holiday" or "ignoring you", so they follow up, which increases the volume, which increases the monitoring.

Meanwhile nobody has deep working time, because every notification might be the urgent one.

What to state

A default response time per channel. For example: chat within four working hours, email within one working day, documents for review within two.

The specific numbers matter less than that they exist and are the same for everyone.

What urgent means and how it travels. If everything arrives through the same channel at the same apparent priority, people cannot triage and must monitor everything. Define a route for genuinely urgent matters — a phone call, a specific mention, an on-call rotation — and use it only for those.

What no reply means. Silence on a proposal after the stated window: approval or objection? Both conventions work. Not choosing one means proposals stall indefinitely.

Working hours per person, published where people can see them, in local and reference time.

Whether out-of-hours messages are expected to be read. If a manager writes at 10pm, does the recipient reply then? Say so explicitly, because in the absence of a statement people assume yes.

The manager sets the actual norm

Whatever is written, the team observes what managers do.

A manager who replies at midnight establishes that midnight replies are normal, regardless of what the policy says. A manager who says "no need to respond outside hours" and then sends messages at 11pm has established the opposite of what they said.

If you want a norm to hold, the most senior person has to demonstrate it. Scheduled send is a small tool that resolves most of this: write when you want, deliver in working hours.

Distinguish the three modes

Naming these three explicitly resolves most confusion:

Now. Someone is blocked or something is broken. Rare. Has its own channel.

Today. Needed to make progress this working day. Normal chat.

Whenever. Context, updates, non-blocking requests. Should not generate a notification that interrupts.

Teams that make this distinction visible — in channel structure, in message conventions, in habit — reduce interruption substantially without slowing anything down.

The written request

An enormous amount of friction comes from underspecified messages.

"Can we talk about the API?" requires the other person to be present. The alternative states the question, the relevant background, what has been tried, what decision is needed and by when — and can be answered while you sleep.

It takes the sender ten more minutes. It saves a scheduled call, a time zone negotiation and a day of latency. Teams that adopt this as a norm feel noticeably faster despite responding more slowly.

Review it once a year

Norms drift. New people arrive with habits from elsewhere, a busy quarter erodes the boundaries, and within a year the practice differs from the document.

A short annual check — is this what we actually do, and if not, which should change — keeps the written version honest.