TLDR

Span of control counts direct reports. Span of attention asks whether a manager can still give sound judgment to the decisions, people, priorities, conversations, and interpretation work the role requires. For CHROs, that is often the more useful capacity question.

Introduction

A manager can have a reasonable span of control on an organization chart and still be operating beyond practical capacity. The issue is not simply whether there are too many direct reports. It is whether the role asks one person to hold too many consequential threads at once: a priority that changed, a decision awaiting context, a struggling employee, an unresolved conflict, a cross-functional dependency, and the ongoing work of translating strategy for a team.

When attention is fragmented, leadership does not disappear. It becomes reactive. The manager handles what is loudest, most recent, or easiest to close, while interpretation, coaching, and decision quality receive whatever capacity remains. That is why headcount alone is an incomplete design measure.

Span of control is a structural measure. Span of attention is an operating reality.

Span of control remains useful. It can reveal overly layered structures, clarify accountability, and flag managers with unusually large teams. But it says little about the cognitive and relational work attached to each reporting line.

A people manager’s role often spans operations, communication, coordination, employee support, evaluation, strategy implementation, and change. The CIPD evidence review of people-manager responsibilities is a useful reminder that management is a portfolio of different kinds of attention rather than a single workload.

Two managers with the same number of reports may therefore face very different capacity conditions. One may lead a stable, experienced team with clear decision boundaries. Another may be translating a new operating model, repairing handoffs across functions, handling vacancies, and preparing people for difficult conversations. The chart sees the same span. The work does not.

Attention is consumed by interpretation, not only activity

The hidden load is often interpretive. Managers must decide what a strategic priority means locally, distinguish an exception from a pattern, judge when to intervene, and explain trade-offs in language their teams can use. These are not administrative tasks that can be assessed by volume alone.

Evidence on decision-making supports the importance of this distinction. A strategic-decision simulation examining cognitive load and task complexity found that perceived task complexity was negatively associated with strategic decision outcomes. The study involved 50 graduate-level management students in a simulated setting, so it does not establish a universal managerial limit. It does, however, reinforce a practical point: the quality of a decision depends in part on the cognitive demands surrounding it.

For a CHRO, the design question is therefore broader than, “How many people report to this manager?” It is also, “How many different interpretations, judgments, and relationship moments must this manager carry at the same time?”

The first losses are often leadership behaviors

When attention is saturated, managers tend to preserve urgent transactions first. They respond to messages, unblock immediate work, attend required meetings, and close visible issues. The first work to thin out is usually less visible: preparing for a difficult conversation, following through after a one-to-one, explaining why a priority changed, or noticing when two teams have begun acting on different interpretations.

A 10-day experience-sampling study of managers’ email demands found that higher daily email demands were associated with lower perceived progress toward work goals. Lower perceived goal progress was, in turn, associated with reduced initiating-structure and transformational leadership behaviors. This is association evidence from a small daily self-report sample, not proof that email causes poor leadership. Still, it illustrates how routine communication inflow can compete with the behaviors employees experience as leadership.

The signal is a pattern rather than an inbox count: important conversations are repeatedly deferred, decisions are revisited because context was lost, and managers communicate the what without enough of the why.

Capacity failures can look like performance failures

An overloaded manager may be described as inconsistent, insufficiently strategic, or weak at people leadership. Sometimes that assessment is fair. Sometimes it confuses an individual capability issue with a role-design issue.

A useful diagnosis separates three conditions:

• Capability: Does the manager have the judgment, communication, and decision skills the role demands?

• Capacity: Is there enough protected attention to use those skills consistently?

• Context: Are priorities, decision rights, and escalation paths clear enough for good judgment to travel?

This distinction matters because more training will not resolve an impossible attention portfolio. Nor will reducing direct reports solve a role where ambiguous priorities and cross-functional dependencies consume every available margin.

Design for attention before adding another program

CHROs and people leaders can make span of attention visible without inventing a universal threshold. Start by examining the work that competes for a manager’s judgment, rather than only the people assigned to them.

Ask five questions:

1. Which decisions require this manager’s interpretation rather than simple approval?

2. Which direct reports or teams face materially different operating conditions?

3. How often do priorities change, conflict, or require local translation?

4. Which conversations are consequential enough that preparation and follow-through matter?

5. Where do managers repeatedly become the human integration point between functions?

The answers will not yield one correct ratio. They will reveal where role complexity, rather than headcount, is consuming leadership capacity. That gives leaders a more useful basis for simplifying decision rights, clarifying priorities, redesigning support, or changing the work around the manager.

Protecting attention protects the conditions for constructive leadership

The downstream stakes are human as well as operational. A preregistered meta-analysis of leadership, engagement, and burnout, synthesizing 1,016 independent studies, found that constructive leadership was positively associated with follower engagement and negatively associated with burnout. The analysis also reported substantial variation across studies, and it does not test manager attention load directly.

The reasonable inference is not that a new span design will automatically improve engagement or prevent burnout. It is that organizations should take seriously any operating condition that repeatedly leaves managers without the attention required to lead constructively.

This is where leadership enablement has a role. Baryons is built to help keep organizational context, private guidance, and privacy-protected aggregate signal closer to the moments where leaders must decide and communicate. The aim is to help intent stay connected to execution when attention is under pressure, rather than to add another management task.

Final Thought

Manager effectiveness is often treated as a trait to assess after performance slips. Span of attention offers a more useful starting point: examine whether the role gives a manager enough room to interpret, decide, communicate, and follow through before judging the person inside it. Signal before symptom begins with noticing where leadership attention is already being spent.

If manager capacity is becoming an execution constraint, Baryons can help frame the conversation around leadership enablement, shared context, and earlier signal.

Manager strain usually gets named after a performance review. Leadership enablement is about noticing where attention is already stretched while there is still room to act. That is the work a Baryon supports. Bring a real capacity question to yours, name the team that keeps becoming the integration point between functions, and see where the load actually sits. Start at app.baryons.com or call 231-BARYONS.

Signal before symptom.

Without a Baryon so far? Spinning one up takes minutes and won’t cost you anything: create yours.

Think your managers are carrying more than the org chart shows? Book a demo and we’ll walk it through with a real team in mind.

Like to look before you leap? Watch the Baryon Overview on YouTube.