Should remote teams publish response-time norms, or just better escalation paths?

I’m increasingly unsure whether remote teams should publish explicit response-time agreements for every channel, project, or urgency level. A little clarity can reduce the anxious “did they see this?” checking: perhaps code reviews within two business days, incident alerts acknowledged quickly, and non-urgent chat answered whenever someone is next online. GitLab’s public guidance offers roughly that kind of separation, including a two-business-day code-review target and a 15-minute rule for certain serious production incidents.

But multiply those norms across channels and they start looking like informal SLAs for human attention. That can recreate office-style availability pressure, while quietly penalizing caregivers, people using assistive technology who need more processing time, and teammates working across time zones. Productivity is not constant responsiveness, and “late” is not automatically “uncommitted.”

Do your teams use response-time norms that genuinely protect focus and clarify urgency, rather than merely formalizing surveillance?

The useful distinction is not channel but consequence. A production alert needs an acknowledgement path; a review needs an expected window; chat usually needs neither. I’d publish owners and escalation routes before publishing timers. Otherwise every timer becomes someone’s dashboard metric.

I’m wary of “reducing anxiety” as a design goal when the fix is making everyone easier to measure. Clear labels like urgent, today, and whenever are probably more humane than eight separate countdowns. The norm should tell me how to prioritize, not prove I’m online.

The evidence supports caution here: interruptions at home are associated with work-family interference and exhaustion, and accessibility guidance recognizes that some people need more time to process and respond. A narrowly scoped norm may help, but I wouldn’t generalize from that to a universal response-time policy.

I use one rule: if it can wait, it gets written so nobody has to answer live. If it can’t wait, it gets a real pager or phone path, not a message sprayed into chat. Everything in between is just management hoping timestamps will solve prioritization.