Slack was launched in 2013 with a promise: it would replace email and make work better. Email was slow, disorganized, and siloed; Slack would be fast, searchable, and transparent. By 2019, Slack had ten million daily active users. By 2023, it had been embedded as the communication backbone of hundreds of thousands of organizations, from technology startups to financial institutions to government agencies. The promise was largely kept: Slack did replace much email, and in doing so it delivered on its efficiency claims. What it also did—and what was neither promised nor predicted—was transform organizational communication from an asynchronous activity that happened alongside work into a synchronous activity that replaced work as the default mode of organizational existence.
The central mechanism is not difficult to identify. Email, for all its problems, was bounded by the convention of the inbox: workers could check it at intervals, respond in batches, and maintain a separation between reading-and-responding time and substantive work time. Slack eliminated this convention by design. Its interface is a real-time chat environment modeled on consumer messaging apps. The channels are always open, always updating, always generating new content. The social dynamics of group messaging—the visibility of who is online, the expectation of response before the conversation moves on, the peer pressure of being seen to be engaged—create norms of continuous participation that email never imposed.
At the organizational level, the adoption of Slack and analogous platforms (Microsoft Teams, Google Chat, Discord for workplaces) produced a characteristic pattern. Communication volume increased dramatically: the low friction of short messages generated more messages than email had. Communication became more visible and public within the organization: private email threads became channel discussions visible to whole teams. Response expectations accelerated from the hours that email implied to the minutes or seconds that synchronous chat implied. And the cognitive profile of organizational communication shifted from occasional deep reading of substantive messages to continuous shallow monitoring of high-volume, short-form channels.
The cognitive consequences of this shift are measurable. A channel that receives new messages frequently must either be monitored continuously—which prevents any sustained focus—or ignored, but with the attendant anxiety of falling behind a fast-moving conversation and the social risk of appearing disengaged. The typical Slack user resolves this dilemma by monitoring continuously while working, splitting attention between the channel and whatever substantive work is nominally in progress. The result is neither genuine focus nor genuine engagement with the channel; it is the continuous partial attention state that defines the Slack-saturated knowledge worker's day.
The organizational proliferation of Slack channels compounds the problem. Organizations using Slack typically create dozens to hundreds of channels—by team, by project, by client, by function, by social interest. Each channel generates notification pressure. Workers subscribe to channels because non-subscription risks missing important information; subscription imposes monitoring obligations that multiply with each channel added. The channel proliferation problem is a variant of the email overload problem, accelerated: the low friction of channel creation means that the supply of attention-demanding communication grows faster than any individual can absorb.
At the collective level, Slack-type platforms have changed the structure of organizational knowledge. Email generated organizational memory in the form of searchable archives that, however imperfect, preserved substantive decisions, rationales, and information exchanges. Slack generates a different kind of knowledge structure: high-volume, low-density, rapidly aging. The short-form messages that dominate Slack channels contain less substantive information per message than email, making the archive less useful as organizational memory. Important decisions made in Slack channels are mixed with social chatter, emoji reactions, and off-topic discussions in ways that make retrieval difficult. Organizations that have moved to Slack-first communication have sometimes found that institutional knowledge that was previously preserved in email threads is now effectively inaccessible, buried in the noise of channel history.
The political economy of Slack and its equivalents mirrors the broader attention economy. These platforms are monetized by organizational subscription, but their design reflects the consumer engagement architecture of their cultural origins. The engineers who built Slack came from the same ecosystem—Bay Area technology culture, consumer social media, gaming—that built the attention-extraction machine of the broader internet. The notification architecture, the reaction system, the channel design, the online presence indicators: each design choice was made in a context where engagement was the product metric, and engagement-maximizing design was not critically reconsidered before being imported into the organizational context.
Reclaiming organizational attention from Slack-type platforms requires confronting the design ideology that produced them and the cultural norms that sustain their current use. The technical solutions—channel discipline, notification management, designated asynchronous hours—are documented and achievable. The cultural barrier is the equation of Slack responsiveness with organizational citizenship: the sense that the worker who does not participate continuously in the channels is not a full member of the organization. Dismantling this equation is a collective project that requires explicit leadership commitment, visible norm modeling, and the honest recognition that the most valuable cognitive work any knowledge organization does cannot be done in three-minute increments between channel messages.