Slack did not invent the problem. Email had already colonized the working day before Slack arrived. But Slack refined the mechanism: it took the asynchronous message and made it synchronous by norm, took the discrete inbox and made it a continuous stream, and built an organizational culture around instant response that email, for all its intrusiveness, had never fully achieved. The notification cadence of Slack—a new message, a reaction, a thread reply, someone typing in a channel—is designed around a variable-ratio reinforcement schedule. It is the same architecture as a slot machine. You do not know when the next message will arrive or whether it will be important, so you check continuously. The checking becomes compulsive before it becomes a habit, and a habit before it becomes something most workers can identify as a structural problem.
The deep-work casualty is not incidental to this design. It is the product of it. Deep work—the state of cognitive engagement in which complex, non-routine problems are worked on with full concentration—requires an uninterrupted runway. The cognitive work of entering a complex problem, holding multiple variables in working memory, building toward a synthesis, and following a thread of thought to its end takes time and an absence of interruption. The runway varies by person and problem but is typically measured in tens of minutes at minimum and hours for the most demanding work. Slack's default notification structure makes a runway of this length structurally impossible unless the worker has actively and specifically prevented it. Most workers have not. Most organizations have not.
Law 2—reclaiming attention—identifies what is being surrendered here. Every time a worker shifts from a document they are writing to a Slack channel because a notification arrived, two things happen. The thought that was forming in the document evaporates. The expectation that the worker will respond quickly is reinforced. The first is a loss to the individual and to the work. The second is a loss to the organizational culture: each rapid response strengthens the norm that rapid response is required, which makes the cost of non-response feel higher, which makes it harder to ignore the next notification. The trap is self-reinforcing. Organizations adopt Slack because it seems to accelerate communication. It accelerates shallow communication while slowing—through structural interruption—the deep work that is the organization's most valuable output.
The personal experience of working in a Slack-heavy organization has a characteristic texture. There is always something happening. There is always something to respond to. The day is never empty. The sense of connection and activity is high. The sense of producing something that matters is low. At the end of a Slack-saturated week, a worker can often recall dozens of conversations but cannot point to a piece of work that demanded everything they had. The conversations were the work. The conversations are not nothing—communication is real work, coordination is real work—but they are not equivalent to the thinking that Slack's notification architecture has been systematically preventing.
The response available to the individual is limited but not zero. Notification silence is technically possible. Communicating expectations of response latency—I check Slack twice a day, at 10 and 3—is possible in some organizational cultures and impossible in others. Status settings can be used strategically. But these are individual adaptations to a structural problem, and the structural problem will persist unless the organization explicitly decides what it wants from Slack—what communication patterns it is trying to enable and what cognitive conditions it wants to protect—and configures its norms accordingly. Few organizations have this conversation. Most adopt Slack, watch communication volume increase, and conclude that communication has improved, without asking what else has changed.