Capacity, what shapes it, and what leaders can do about it

Good morning. The phrase "we don't have capacity for that" gets used a lot. Sometimes it's accurate. More often, it signals that time and energy are being consumed in ways that aren't fully visible, or that what the team is being asked to carry and what they can reasonably carry haven't been honestly reconciled.

Capacity is rarely fixed. It's shaped, by what's on the list, by how priorities are communicated, by how much context-switching is required, and by whether the conditions for focused work exist. A team that appears to have no capacity might have significant capacity going to the wrong things, or being eroded by structural conditions no one has examined.

This is worth understanding before concluding that you simply need more resource.

Most leaders have a reasonable sense of what's on their team's plate formally, projects, deliverables, milestones. Fewer have a clear picture of the informal load: ad-hoc requests, coordination overhead, internal process work, the administrative drag that consumes time without appearing on any plan.

Heike Bruch and Sumantra Ghoshal's research, published in the Harvard Business Review, found that only about 10% of managers work in a genuinely purposeful, focused way. The other 90% squander time in unfocused, often reactive activity, responding to requests, attending meetings, managing small problems, rather than the work that matters most. Teams face a version of the same thing. The gap between what's on the task list and what's consuming precious hours is almost always larger than it appears, and almost always invisible until someone maps it.

The more useful question is how much of what's on the list is actually generating output, and how much is process, overhead, or accumulated habit.

Capacity is more than time. It's also the energy available to do the work well. Two people with identical hours can have very different effective capacity, depending on what's sustaining or draining them. Leaders who understand this pay attention not only to what their team is doing, but to the conditions they're doing it under.

Frequent context-switching is one of the more significant and underestimated capacity drains. The cognitive cost of moving between tasks, communication threads, and modes of thinking adds up. Teams that feel overloaded often become markedly more productive when given longer blocks of uninterrupted time, not more hours spread across the same fragmented day.

Capacity problems are hard to act on while the load stays invisible.

A simple way to make it visible: take one recent week and sort where the hours actually went into three buckets.

You don't need precision for this to be useful. Even a rough split tends to surprise people: the core-work bucket is usually smaller than anyone expects, and the maintenance bucket is doing more damage than anyone had noticed.

Once you can see the shape of the week, you have something concrete to question and rebalance, instead of a general sense that everyone's stretched.

One of the most concrete things a leader can do for their team's capacity is to be the person who says no, or "not now", to incoming requests. This requires a clear enough view of what actually matters that you can make the call confidently, and communicate it in a way the team can trust.

A team that doesn't see clear prioritisation from above tends to treat everything as equally urgent. And when everything is urgent, nothing actually is. The work that genuinely moves the needle gets sidetracked, or lost in the noise.

There's a version of leadership that treats incoming requests as the team's problem to absorb. A better version treats the leader as a buffer, someone whose job includes deciding what reaches the team and what doesn't. Protecting time, priorities, and capacity is how you make sure the team's energy goes to the work that genuinely matters, rather than the noise that collects around it.

When understanding where the time is actually going: "Walk me through what you're spending time on this week, the whole picture, not just what's on the plan. I'm trying to understand where our hours are actually spent, and how we can free things up."

When someone flags they don't have capacity: "Tell me more about what's consuming most of your time right now. I want to understand whether it's the core work, or the noisy things around it that we can reassess."

When deprioritising an incoming request on behalf of the team: "I'm taking this off the team's plate for now. Given what we're already carrying, it can wait until [time]. I'll let [person] know."

Capacity is something you manage. The leaders who understand that give their teams a fundamentally different experience of work.