Response expectations need explicit agreement
Aliases: response norms · communication contract · service-level expectation
What it is
Response-time expectations are a shared agreement on when different requests should be acknowledged and resolved. A sender can read silence as neglect while a recipient reads it as permission to respond later; the conflict is often between two unstated clocks.
Why it happens
Channels, mentions, read receipts, and send time imply urgency, but their meaning varies. Remote work removes the cues that reveal whether someone is busy. Senders seek certainty by chasing; recipients defer viewing to protect attention. Explicit acknowledgment and resolution windows separate “I saw this” from “I can finish this,” making it safer to be offline.
Studying it
- Paradigms: analyse sent, acknowledged, and completed times by request type; interview both sides; compare chasing and dropped work before and after a norm.
- Variables: request type, channel, acknowledgement delay, completion delay, escalation count, and perceived pressure.
- Methodological caution: averages hide long tails and power differences; report by urgency, role, and time zone.
Where it stops holding
One fixed minute count cannot fit every kind of work. Incidents and ordinary discussion need different promises, as do clients and internal colleagues. A rule without rotation and compensation can disguise an all-hours on-call demand.
Applying it
- Define acknowledgement and handling windows for a small set of request classes, including when to use a live or on-call route.
- State the required action, deadline, and whether acknowledgement alone is enough; let recipients give an estimated time first.
- Keep availability user-correctable rather than inferring interruptibility from online or keyboard activity.
- Verification: sample actual delays against commitments and anonymously test whether chasing fell without raising after-hours burden.
Related
- Same group: V10.03.1 Temporal overlap sets the ceiling for synchronous collaboration · V10.03.2 An asynchronous default expands the collaboration range
- Nearby: V4.06 Time zones and response expectations · V2.08 Availability and willingness to be interrupted · V6.05 Notifications and collaborative noise
- Search terms:
response-time expectations·communication norms·availability