The Hidden Tax: How Slack's Always-On Culture Costs Employees Their Time

In 2016, the software company Basecamp sent an internal memo that would become a landmark in the battle against always-on work culture. The policy was simple: no after-hours chat. No Slack messages after 6 p.m., no weekend pings, no expectation of immediate response outside core hours. It sounds like a dream for anyone who has felt their phone buzz at 9 p.m. on a Tuesday and known, with a specific kind of dread, that the message would not wait until morning. But the fascinating part of the story isn't the policy itself. It's what happened in the 18 months after it was announced. Jason Fried, Basecamp’s co-founder, later wrote about the quiet resentment that surfaced among some of the company’s managers. They pushed back. They argued that the ban made it harder to coordinate, that they needed the ability to reach people instantly, that the business would suffer. Fried’s account, published in 2018, exposed something uncomfortable: the managers who resisted the ban weren't worried about productivity. They were worried about losing a cheap coordination crutch that had been masking poor planning. Let me be precise about the scope here. The problem with Slack culture is not that employees are too lazy to disconnect. The problem is that managers weaponized the tool to avoid doing the hard work of designing better workflows. When you can ping someone at any hour, you never have to think about whether the question could have been answered by a shared document, a scheduled stand-up, or a well-written spec. The constant availability becomes a substitute for structure. The manager who relies on Slack’s immediacy is essentially outsourcing coordination costs to their team’s personal time. This is where the design lens matters. Slack was built as a communication tool, but it quickly became a coordination tool—and a terrible one at that. Coordination requires intentionality: deciding when information is needed, by whom, and in what format. Slack’s default mode is synchronous, interrupt-driven, and flat. Every message carries the same urgency, which means no message carries the right urgency. The tool’s design choices—the notification badge, the unread count, the @channel ping—are not neutral. They are features optimized for engagement, not for human cognition. They are features that make the manager’s life easier at the expense of everyone else’s attention. The pushback against this culture is not anti-communication. It is a demand for intentional, context-aware communication that respects cognitive flow. Employees are developing their own asynchronous etiquette: response time norms, “I’ll get to this by end of day” disclaimers, deliberate muting of channels after hours. These are small acts of resistance, but they point to a larger structural failure. France’s 2017 “right to disconnect” legislation was a recognition that the law had to step in where organizational design had failed. Studies of the law’s impact show measurable reductions in burnout among companies that enforced it seriously. But legislation can only do so much if the underlying workflow remains broken. Basecamp’s answer was not just to ban after-hours chat. They redesigned their entire approach to work around asynchronous communication: written updates, scheduled check-ins, a culture of “it can wait until tomorrow.” The resistance from managers was a signal that the organization had been running on a hidden tax—the unpaid attention of employees. When that tax was removed, the managers had to confront the fact that their coordination habits were built on sand. The always-on norm is a symptom of structural inefficiency, not a sign of dedication. Killing it forces better project design. It forces managers to write things down, to plan ahead, to think about who actually needs what information and when. It forces the organization to absorb coordination costs that were previously externalized onto individuals. That is uncomfortable. It is also necessary. The next time you feel that Slack ping at 8 p.m., ask yourself: what problem is this message really solving? If the answer is “the manager didn’t plan ahead,” then the problem is not your availability. The problem is the workflow. And the only way to fix it is to stop pretending that constant responsiveness is a virtue.