Somewhere right now, a person is typing “just bumping this to the top of your inbox” into Slack, which is a sentence that should not exist. Slack was launched in 2013 under headlines that called it, without apparent embarrassment, an email killer. It killed nothing. It added a second inbox with worse manners — one that lights up red, shows your name in it, and expects an answer before lunch.
This is the pattern, and it has repeated too many times to be an accident. Asana was founded in 2008 by two Facebook engineers who wanted to free teams from email. Trello, Notion, Teams, Basecamp — each arrived with the same pitch, roughly: stop digging through threads, work in the open, be free. And each, within a few years, grew a notifications tab, an unread count, a mentions view, a little badge that follows you to your phone. The email killers became email. The worker who once maintained one queue now maintains five, and checks all of them before coffee, and is behind on all of them by ten.
It would be comforting to blame bad design — feature creep, engagement metrics, the usual suspects. But the tools keep converging on the inbox from completely different starting points, which suggests the inbox is not a bug that keeps reappearing. It is a thing people keep building on purpose.
Here is the less comfortable explanation: the queue is not really a communication system. It is a status system. Being reachable is how availability gets performed at work now — the green dot, the fast reply, the visible presence in the channel. Responding quickly to messages is one of the few legible signals of diligence left in jobs where the actual output is ambiguous, delayed or shared. Nobody can see you thinking. Everybody can see you answering. So the queue fills a need that has nothing to do with the content of the messages, and that is why deleting one queue accomplishes nothing. The performance doesn’t disappear; it relocates. Kill email and the performance moves to chat. Kill chat and it would move to whatever shipped next quarter, badges and all.
This also explains the strange emotional texture of the modern inbox — the guilt, the dread, the low-grade sense of failing at something you were never explicitly assigned. If the queue were just correspondence, an unanswered message would be a postponed task. Instead it reads as a small public absence: you were called on, and you weren’t there. People don’t apologize for having too much email. They apologize for being unreachable, which is a confession about presence, not paperwork.
Ray Tomlinson sent the first networked email in 1971 and later recalled the message as a forgettable test string, something like “QWERTYUIOP.” Half a century of infrastructure has been built on top of a keyboard mash, and the great project of the software industry ever since has been to replace it — an effort that has produced, reliably and expensively, more places to be reached.
The honest product pitch, then, is not a better inbox. It would be a workplace where availability is not how you prove you exist — where the green dot means nothing and an unanswered message is just a message. Nobody has figured out how to sell that, because it isn’t software. It’s a manager deciding that the fastest replier is not the most valuable person in the room. Until that happens, every email killer will keep arriving on schedule, and each will ship with a badge, and the badge will turn red, and you will check it before coffee. Not because the tool failed. Because it worked.