Response times, stated rather than assumed
Without a written norm, everyone invents one, and the most anxious person's version becomes the culture.
A distributed team with no stated response norm does not have no norm. It has several, held privately and incompatibly: one person believes messages should be answered within the hour, another within the day, a third when they next sit down to focused work. For broader context on distributed asynchronous work, GitLab’s all-remote handbook is a useful reference.
The gap between them produces the two complaints you hear in every remote team — that people are unresponsive, and that nobody can concentrate.
Write down the tiers
Three is usually enough, and the point is that each has a channel and a time attached. For a practical software-side reference on how teams interpret response time, further details adds useful detail.
- Something is broken and affecting people now — a named channel or a phone call, minutes.
- Blocking someone's work today — direct message, same working day.
- Everything else — the default. Next working day, and it is genuinely fine to leave it.
The third tier is the one that has to be defended, because it is the one that makes deep work possible. If everything is implicitly tier two, the team is synchronous with extra steps.
The reason people chase is that they do not know what to do if something is genuinely urgent. Give them a route and the ambient chasing stops.
Separate reading from replying
Much of the anxiety in async teams is about whether a message was seen. A convention that acknowledges receipt — a reaction, a one-line 'looking at this today' — costs seconds and removes most of it.
It also protects the responder: an acknowledged message with a stated timeframe is not chased, whereas silence is.
Match the expectation to the time spread
A four-hour response norm is workable in a team spanning four hours and absurd in one spanning twelve, where it means somebody is answering at midnight.
The norm has to be set against the widest spread in the team, not against headquarters. Where a genuinely fast response is needed, that is a staffing question — a rota, a follow-the-sun arrangement — rather than a norm that quietly obliges one region to be permanently available.
Managers set it by behaviour, not by policy
A stated norm of next-day response, from a manager who replies within four minutes at all hours, is not the norm. People calibrate to observed behaviour and will match the fastest responder they report to.
If a manager works unusual hours, scheduled sending is the fix. It costs nothing and removes an implicit expectation that everyone else is on the same schedule.
Review it when the team changes shape
A norm set for a team in two adjacent countries stops working the day someone is hired eight hours away. Revisit it at each significant change rather than discovering the mismatch through resentment.