What does it mean that team attention management?

What the team collectively pays attention to determines what it accomplishes. Team attention is a finite resource that can be designed, directed, and protected — or squandered on whatever is loudest, most urgent, or most emotionally salient.

Example: A growth engineering team at a SaaS company had eight engineers working on conversion optimization. Every Monday, the team reviewed its priorities. Every Monday, the priorities were overridden by the end of Tuesday. A customer escalation would redirect two engineers to a support issue. A sales request would pull another into a demo customization. The CEO would mention a competitor's feature in Slack, and the product manager would add it to the sprint. By Friday, the team had worked intensely all week but advanced none of its conversion goals. The engineering manager, Marcus, tracked the team's actual time allocation over four weeks. He found that the team spent only 31 percent of its time on its stated priorities. The remaining 69 percent went to reactive work: urgent requests, ad-hoc escalations, and shiny-object features. No single interruption seemed unreasonable in the moment — each was a legitimate request from a legitimate stakeholder. But the aggregate effect was devastating: the team's conversion optimization project, which the company's revenue model depended on, was perpetually two weeks away from meaningful progress. Marcus implemented what he called an 'attention budget' — a weekly allocation of team hours to three categories: committed work (the priorities that cannot be interrupted), responsive work (a buffer for legitimate urgent requests), and exploratory work (time for team-generated improvements). The budget was visible to stakeholders. When a new request arrived, the team's response was not 'yes' or 'no' but 'which category does this come from, and what does it displace?' Within one quarter, the team's progress on conversion goals accelerated by 3x — not because they worked more hours, but because their collective attention was finally directed at their collective priorities.

Try this: Track your team's attention allocation for one week. At the end of each day, have each team member spend two minutes recording how they spent their time across three categories: (1) Planned work — tasks aligned with the team's stated priorities. (2) Reactive work — tasks that were not planned but responded to external requests or incidents. (3) Administrative work — meetings, status updates, and coordination overhead. At the end of the week, aggregate the data. If planned work is below 50%, the team has an attention management problem. Discuss the results and identify the top three sources of attention diversion. For each source, decide: Can we eliminate it? Can we batch it? Can we route it to a single person rather than interrupting the whole team? Implement one change and measure the following week.