Replace presence dots with explicit response-time budgets

I'd rather our team treat response expectations as a small, machine-readable contract than infer them from presence dots or read receipts. An active dot only says something about application activity, and a read receipt doesn't prove someone has understood a request or is available to answer.

A message could carry one of three labels: `urgent`, meaning use the agreed escalation path; `same-day`, meaning respond during the recipient's current workday; or `async`, meaning no immediate response is expected. That would let me protect a block of coding time without worrying that appearing inactive looks like neglect. The label should describe the request, not become a score for individual response speed.

The categories could still flatten context, and managers could turn them into another monitoring system. Teams would need an exception path for genuinely urgent work. Would you trust explicit response-time agreements more than status indicators? Examples or counterarguments welcome.

The useful part is separating request priority from observed presence. I would add that the sender should state what counts as a response: acknowledgment, a decision, or a completed fix. Otherwise `same-day` just moves the ambiguity into a new field. Also, who sets `urgent` matters; letting every sender do it recreates the interruption problem.

This could reduce the social theater around being online. A person can be visibly active while presenting, debugging, or caring for something urgent away from the keyboard. But the labels need to be easy to use and socially respected, or people will keep adding anxious explanations like “sorry, just saw this.”

The exception path is the whole system, operationally. We would need a named on-call route for outages or customer-blocking incidents, while everything else stays in the queue. If “urgent” is merely a red tag in chat, it will become background noise within a week.

I would oppose storing detailed response-time performance by person. A label attached to the work item is useful; a dashboard ranking who answered in 18 versus 24 minutes is surveillance with nicer vocabulary. Retention, access, and manager permissions should be part of the design from day one.

The anxiety argument is plausible, but I would be careful about claiming these budgets solve it. Research supports a relationship between remote-work visibility concerns and faster responses, not that this particular labeling scheme reduces anxiety. That makes this a reasonable team experiment, not an established remedy.

I’m not convinced three labels are enough. “Urgent” often depends on who is blocked and what happens next, which a sender may not know. A short sentence with a real deadline might be clearer than a category, especially for small teams that do not need another protocol.