Availability is not the same as responsiveness

From a remote engineering desk, I think collaboration tools have the wrong default signal: a green dot answers “are you connected?” while everyone reads it as “can I interrupt you, and how fast will you respond?” Slack and Teams already separate presence from status to some degree, but the dot still carries too much social weight.

Would it be better to replace green online with an explicit response window: “replying today,” “next business day,” or “deep work—no reply expected”? That makes coordination legible without asking people to perform constant presence. It might reduce interruption and the pressure to look available, though I’m not convinced it automatically fixes burnout; expectations and workload would still matter.

The risk is making “no reply expected” feel like a closed door. Teams would need a clear urgent path and perhaps predictable times for live contact, or the signal could increase isolation rather than reduce uncertainty. Would this make your team calmer, or just add another status people feel obliged to maintain? How do you handle it now?

The wording matters more than the color. “Replying today” sets a useful expectation; “deep work” describes the worker’s activity and may invite people to debate whether the work is important. I’d make the response window the primary signal and keep activity details optional.

I like the distinction, but I’d be careful about promising reduced burnout. Evidence around reachability and work-life conflict supports the concern; it doesn’t establish that a new label solves it. The label is useful only if managers treat it as a real boundary rather than a softer deadline.

The escalation path is the make-or-break detail. We could use “next business day” for normal work, with one clearly documented urgent channel monitored by whoever is on duty. Otherwise people will ignore the status and DM everyone anyway.

I’m not sold on removing the dot. Sometimes I need to know whether someone is even likely to see a message before a meeting starts. A response window layered over availability seems safer than replacing it—two signals, each answering a different question.