Shared Capacity

I want to start Shared Capacity with a situation from a company I was involved with, because it shows how easily a performance problem can be misread.

In this organization, the sales team was doing exactly what leaders wanted them to do. They were selling. They were bringing in business. They were creating growth.

From the outside, that looked like success. And in one sense, it was.

But every new sale created work somewhere else.

Someone had to process the account. Someone had to handle the client details. Someone had to manage the follow-up, the paperwork, the questions, the exceptions, and all the little pieces that make the sale real after the handshake.

A lot of that work landed on the administrative team.

And here’s where the story gets interesting. Nobody was trying to create a problem. Nobody woke up and said, “Let’s overload the support team.” The sales team was doing its job. Leaders were probably pleased with the numbers. The organization was moving.

But the work had shifted, and the capacity had not.

So what happened?

The administrative team started absorbing the gap. They carried more. They stayed later. They solved more problems in the background. They became the safety net for growth the system had not been resourced to support.

For a while, that can look like teamwork.

It can look like commitment. It can look like people stepping up. It can look like the organization is handling the growth just fine.

Until it isn’t.

Before I tell you what happened next, think about this for a second.

Have you ever been in a situation where one part of the organization was succeeding, but another part was quietly paying for that success?

• Maybe sales increased, but operations couldn’t keep up.
• Maybe a new program launched, but nothing came off anyone’s plate.
• Maybe leaders kept adding priorities, and the team kept saying yes because they didn’t want to look negative.
• Maybe the people holding everything together were praised for being dependable, while the workload that was draining them stayed invisible.

That’s the part leaders often miss.

In this situation, the administrative team eventually hit the wall. People started leaving. And once that happened, the problem became visible. Now leaders could see turnover. They could see service delays. They could see knowledge walking out the door. They could see the remaining team under more pressure.

But the real issue started earlier.

It started when the organization created more work than the support system could reasonably absorb.

That is Shared Capacity.

Shared Capacity is not just whether people are busy. People are always busy. Shared Capacity asks whether the workload, priorities, resources, and role expectations actually make performance possible.

Because when capacity is thin, people don’t just get tired.

Work slows down. Quality drops. Customers feel it. High performers become the default backup plan. And eventually, the people you rely on most may decide they can’t keep making up for capacity decisions the organization hasn’t addressed.

In this situation, when we looked back at the turnover, lost knowledge, service disruption, rework, leadership time, and pressure on the remaining team, the estimated cost was about $1 million in today’s dollars.

That is the cost of missing Shared Capacity.

And that’s why this lever matters. It helps leaders see when the problem is not effort, attitude, or commitment. It’s that the work has outgrown the capacity around it.

Let’s pause on the outcomes side first.

When Shared Capacity is the issue, it doesn’t usually show up with that label. Leaders may not hear someone say, “We don’t have enough capacity to support this level of work.”

More often, they see the outcomes.

Work starts piling up, even when people are working hard. That distinction matters. This isn’t always about effort. Sometimes people are giving a lot of effort, and the work still keeps stacking up.

Deadlines start slipping because too many priorities are active at the same time. Not because people don’t understand deadlines, and not because they don’t care. There may simply be more active work than the team can realistically move at once.

Quality can drop. Rework can increase. Response times can slow down. Those are often the places where a capacity issue becomes visible.

One of the biggest warning signs is when high performers become the default safety net.

That can look positive at first. They’re dependable. They step in. They figure things out. They keep things moving.

But if the same people keep absorbing the overflow, the organization may be relying on individual commitment to make up for capacity decisions leadership hasn’t addressed.

Eventually, new initiatives start to stall. Not because they’re bad ideas, and not because people are resistant to change, but because the team has no real room to absorb anything else.

So when you see these outcomes, the question is not just, “Why aren’t people keeping up?”

The better question is, “What is the workload asking people to carry, and does the team actually have the capacity to carry it?”

Now let’s look at what to examine.

If these outcomes are showing up in your situation, don’t jump straight to motivation, accountability, or attitude. Start with the work itself.

Where is work concentrated unevenly?

Sometimes the official org chart says the work is distributed one way, but the real workload tells a different story. Certain people, roles, or teams may be carrying more than anyone has formally acknowledged.

Next, look at which roles are absorbing hidden or unofficial work.

This is the work that doesn’t always show up in a job description. The extra follow-up. The cleanup. The workaround. The “can you just help with this?” work that quietly becomes part of someone’s regular load.

Then look for signs of pressure.

Backlogs, queues, escalations, delays, overtime, slow response times, and recurring bottlenecks are all useful signals. They can show you where the work is heavier than the current structure can support.

Also ask what has become urgent only because capacity is too thin.

Sometimes work is not truly urgent. It becomes urgent because no one had time to do it earlier, no one owned it clearly, or the team was already stretched when it came in.

Finally, ask what needs to stop, shift, simplify, sequence, or be resourced.

Shared Capacity is not solved by telling people to try harder. It’s addressed by making better decisions about workload, priorities, resources, and timing.

That’s the lens I want you to use when you move into the estimator.

Now move to the Shared Capacity section of the Performance Leak Estimator.

As you answer these questions, think about the workload, priorities, staffing, time, and resources connected to the issue you selected.

The question here is not just, “Are people busy?”

Most people are busy.

The better question is, “Does the team have the actual capacity to carry the work being asked of them?”

Look for places where the work may be heavier than the structure can support. Are certain people, roles, or teams carrying more than anyone has formally acknowledged? Is work piling up even though people are working hard? Are deadlines slipping because too many priorities are active at the same time? Are high performers becoming the default safety net?

Also pay attention to hidden work.

That may include extra follow-up, cleanup, rework, exceptions, urgent requests, handoffs, duplicated effort, or the “can you just help with this?” work that quietly becomes part of someone’s regular load.

This is not about blaming people for being overwhelmed or telling them to manage their time better. It’s about noticing whether the workload, priorities, resources, and role expectations actually make performance possible.

Take a few minutes to complete only the Shared Capacity section. Answer based on what is actually happening in your situation, not what the staffing plan, project plan, or job descriptions say should be happening.

When you’re done, save and continue.