Why Does Your Whole Company Feel Busy but Nothing Deep Gets Done?
Because the organization runs on responsiveness, not focus — and an always-on culture quietly makes deep work impossible. Everyone is busy answering, reacting, and staying available, so no one has the protected attention to do the work that actually moves the business forward. The activity is real. The depth is missing. And the gap between the two is one of the most expensive problems a company can have without ever seeing it on a report.
Yesterday we looked at attention as a personal resource. Today we scale it up, because a team has a collective attention reserve, and most organizations drain it without noticing — then wonder why their smartest people produce so little of their best work.
Key Takeaways
· Organizations reward responsiveness because speed is measurable and depth is not — so busyness quietly substitutes for real productivity.
· Nir Eyal’s “cycle of responsiveness” shows how an always-on culture becomes self-reinforcing, demanding everyone be available all the time.
· A team has a collective attention reserve. The Hanlon Capacity Reserve™ re-points to it: Demand (the org’s attention leaks) and Protect (defending deep work at scale).
· Protecting focus is structural, not personal: meeting discipline, trigger control, and psychological safety to be unreachable when it matters.
· The leader sets the tempo. A leader who pings at all hours has written the real policy, whatever the handbook says.
Busyness as a Proxy for Productivity
Start with the measurement problem, because it drives everything else. In knowledge work, depth is hard to see and speed is easy. You can count emails answered and meetings attended; you cannot easily count the quality of a decision or the originality of an idea. So organizations, reaching for something measurable, quietly start rewarding the visible thing.
Cal Newport, in Deep Work, names this directly: “we use busyness as a proxy for productivity. The person who responds fastest looks productive, so they are treated as productive, and everyone learns the lesson. Soon the whole culture optimizes for responsiveness — and responsiveness is the precise enemy of the sustained focus that real, valuable work requires. The company gets busier and shallower at the same time.”
It is worth being honest about why this is so hard to resist. A fast reply produces a visible artifact — a sent message, a closed loop, a small hit of completion. Deep work produces nothing visible until it is finished, sometimes days or weeks later. So in any given hour, the shallow choice feels more productive than the deep one, even though over a quarter the reverse is true. Newport’s insight is that “without a clear measure of depth, people and organizations drift, almost gravitationally, toward whatever is easiest to see.” Naming that drift is the first defense against it.
The Cycle of Responsiveness
Nir Eyal, in Indistractable, describes how this hardens into a self-reinforcing loop he calls the “cycle of responsiveness.” When everyone is expected to reply instantly, people keep their channels open and their attention fragmented, which generates more immediate messages, which raises the expectation further. The faster everyone responds, the faster everyone is expected to respond.
What makes this insidious is that it looks like dedication. The person answering at all hours is praised; the person protecting focus looks unresponsive. Eyal’s deeper point is that “the always-on culture is usually a symptom of something organizational — high demands paired with low control over one’s own schedule — not a personal failing. You cannot fix it one heroic individual at a time. You have to change what the organization rewards and tolerates.”
There is a compounding cost here that rarely gets counted. Eyal observes that “people reach for distraction in part to escape the discomfort of an environment that feels out of their control.” So an always-on culture does not just fragment attention — it actively fuels the craving for more distraction, as overwhelmed people seek small escapes from the pressure. The team becomes both more interrupted and more interruptible at once. Breaking that loop is not about demanding more discipline from individuals; it is about lowering the organizational pressure that makes focus feel impossible in the first place.
The Capacity Reserve™ at the Scale of Team Attention
This month we have used one instrument — the Hanlon Capacity Reserve™ — to read finite resources in three movements: Demand, Protect, Restore. A team’s attention is a reserve too, and this week we read it through the first two movements. The difference at the team level is that you are not just reading the gauge; as a leader, you set it. The tempo, the interruptions, and the protected focus are organizational choices.
Demand: The Organization's Attention Leaks
Name the leaks honestly, because they are usually structural rather than personal. The biggest are familiar: meeting overload that fragments every working day, an always-on messaging culture where any ping expects a fast reply, and the constant context-switching that leaves no one with an unbroken stretch of real concentration.
Eyal offers a clarifying test to apply across the board: “is this trigger serving us, or are we serving it? Held up against most recurring meetings and notification habits, the answer is uncomfortable. They persist not because they create value but because no one has questioned them. The first act of leadership is to look hard at what is actually shredding the team’s focus — and to accept that the answer usually implicates the organization’s own norms.
A useful exercise is to audit a single ordinary week against the calendar. How many hours went to meetings that could have been a short written update? How many times did the team’s attention get pulled by a message that was not actually urgent? How many stretches of two uninterrupted hours did anyone actually get? Most leaders are startled by the answers. The fragmentation is not a few bad days; it is the steady state, and it is almost entirely self-imposed. That last point is the hopeful one — what an organization created, an organization can change.
Protect: Building Focus Into How Work Runs
Protection at the team level is a matter of design. Eyal’s recommendations translate cleanly into operating rules: “handle email and messages in batches rather than as a constant stream, require meetings to carry a real agenda and the smallest necessary guest list, and make it visibly acceptable to be “heads-down” and temporarily unreachable.” Newport adds “the idea of a shallow-work budget — deciding deliberately how much of the team’s time should go to logistics and administration, and protecting the rest for depth.”
None of it works without psychological safety. Eyal is clear that “people will only protect their focus if they trust they will not be punished for being briefly offline. That safety is set from the top. When leaders model unplugging — and explicitly bless it — they give the whole organization permission to do the deep work the business actually needs.
Practically, the most durable protections are the ones built into the system rather than left to individual courage. A standing company-wide focus block that everyone honors is stronger than asking each person to carve out their own and defend it alone. A norm that after-hours messages can wait until morning is stronger than telling people they are free to ignore the boss’s midnight email. The goal is to make focus the default and interruption the exception — so that protecting deep work is simply how the place runs, not a small act of rebellion each person has to perform every day.
The Leader Sets the Tempo
In the end, a team’s attention culture is a reflection of its leader’s behavior far more than its stated values. A leader who sends messages late at night and rewards the fast reply has established the real expectation, no matter what any policy says about balance. People read what is rewarded, and they match it.
The reverse is just as powerful. A leader who protects their own deep work, who does not expect instant answers, and who praises the considered response over the quick one resets the tempo for everyone. You are not only managing your own attention. You are setting the rhythm the whole organization will keep.
This is why the work cannot be delegated to a wellness program or a policy memo. People do not follow what is written; they follow what is rewarded and what is modeled. If the most senior person in the room is visibly protecting focus and visibly fine with being briefly unreachable, the permission is real. If they are not, no policy will overcome the example. The tempo of an organization’s attention is one of the truest expressions of its leadership — and one of the most quietly consequential.
Frequently Asked Questions
Doesn’t responsiveness matter? We can’t just stop replying to people.
Responsiveness matters for what is genuinely urgent — which is far less than the always-on culture implies. The goal is not silence; it is batching the non-urgent so that fast replies don’t crowd out the deep work that actually moves the business.
Won’t protecting focus slow the team down?
It slows the visible busyness and speeds the valuable output. A team optimized for instant replies produces a lot of motion and little depth. Protecting focus trades motion for the work that actually matters.
How do I start without disrupting everything at once?
Pick one structural change: cut a recurring meeting, end the after-hours reply expectation, or protect a company-wide focus block. Start there, model it yourself, and let the results make the case for the next change.
How does this connect to last week’s point about energy?
Attention is one of the resources your team’s reserve holds, and fragmentation drains it fastest. Protecting focus is one of the most direct ways to protect the broader capacity we discussed last week.
Final Thoughts
A company can be enormously busy and produce almost nothing deep, and for a long time the busyness will hide the loss. Activity is visible; the missing depth is not, until you notice how rarely your best people get to do their best work.
So manage the team’s attention the way you would manage any resource you depend on. Name what is fragmenting it, protect focus by design rather than by exhortation, and set a tempo from the top that makes deep work possible. Do that, and the busyness gives way to the thing it was always supposed to produce.