Everyone Says They’re at Capacity. Are They?
When you introduce new initiatives or ask your team to look into something and they continuously return the answer, “I’m slammed” or “I’m at capacity” it can be quite frustrating. If everyone is at 110% capacity, but your utilization doesn’t look great, and the output of work doesn’t visibly seem to be that much more, it’s easy to automatically assume your team is exaggerating.
This is when we often see founders and leaders start to take on the work themselves or immediately post for a new hire.
Before you do either, read this whole article.
The problem we’re going to solve together is:
Your team believes they’re at capacity
You cannot prove they aren’t
Important initiatives aren’t getting done or owned unless you do it yourself
"At capacity" is a feeling, not a number
When someone says they're at capacity, it’s typically a report on how their week feels. And it’s real, we aren’t diminishing this. They probably have fourteen unfinished tasks, a bunch of chat threads that keep pulling them out of focus mode, and clients asking for a “quick glance” at something before end of day.
We can’t help your team solve this because while the feeling is legitimate, it’s not data.
If you ask them, “How many hours went to planned client work last week instead of reactive work?” nine times out of 10 you’re getting a guess.
If as a leadership team, you’re unaware of all of the “things” on your teams desk, then you’re letting the “I’m at capacity” and “I’m slammed” responses become your input and trigger for hiring.
Where do the hours actually go?
Capacity rarely disappears in one big chunk. Capacity is typically eroded away in small, tiny actions that aren’t logged in your project management tool.
The deliverable that's been "almost done" for three weeks still eats headspace and a daily check-in. As humans, we despise open loops.
The client's "small tweak" ended up taking 40 minutes. It felt dumb to log it in the PM tool because it was such a small ask.
Context switching between projects in one afternoon means a lot of time spent remembering where you left off. Researcher Sophie Leroy calls this "attention residue": when you switch away from unfinished work, some of your attention stays behind, and the next task gets worse work.
Status meetings, syncs, the meeting to prep for the meeting. (We have opinions about that one.)
If one person is the only one who can do a thing, they get pulled into every instance of it, on top of their actual job.
Capacity isn’t just hours available
This is by far the largest misconception in the working world.
“Capacity = hours available in a week”
Capacity is a formula of four things:
Hours: the time someone actually has after meetings and interruptions.
Skill: whether they can perform this specific work, and whether they can perform it without significant help. Three open hours don't help if the task needs your senior designer and your junior designer is the one who's free.
Context: how much they already know about the client, the project, and its history. Someone new to an account needs more time for the same task.
Mental availability: how much focus they have left. Four hours at the end of a week full of fire drills aren't the same as four hours on a Tuesday morning, especially if their role requires a lot of context switching.
What does this cost an organization?
If you're not a numbers person, here's what this looks like in dollars. These are example figures, so plug in your own if you want a more refined picture.
6-person delivery team at 40 hours a week = 240 hours
Say 20% of that leaks into untracked revisions, switching, and "can you take a look?" requests
That's 48 hours a week. More than one full-time person.
At a $65/hr blended rate, that's $3,120 a week in paid hours that aren't moving planned work forward
Over a quarter, that's $40,560. Over a year, $162,240.
If a team member quit, you'd notice. When their hours disappear a few minutes at a time, you don't.
Why hiring doesn't fix it
So you hire. It's the logical move. Everyone's maxed out, the revenue is there, add a person.
Three months later, the new hire is at capacity too.
That's because you added hours to a system that is designed to burn them. The new person inherits the same untracked revisions, the same pile of meetings, the same "ask so-and-so, they're the only one who knows." Within a quarter, they're slammed. And now you're paying one more salary for the same problem. (More on that in You Finally Made the Right Hire. So Why Is the Team Still Drowning?)
Sometimes you really do need another person. But you can't know that until you can see where the current hours are going.
How to track capacity without making anyone track their time
Nobody wants to fill out a timesheet. Good news: you don't need one and it probably wouldn’t work anyways.
Start with WIP (Work In Progress)
how many tasks each person has actively open right now. You can pull it straight from your PM tool, but each team member should confirm or edit their list. Start having people submit this asynchronously on Fridays. Just keep a running count. Watch whose number keeps climbing.
What WIP won’t be able to tell you
WIP shows you where to look. It doesn't tell you what's causing the capacity drain, what it's costing you in margin, or how much work actually fits in a person's week.
In our client work, we layer WIP with a few other signals to build a capacity baseline a team can actually staff and price against. In our experience, that takes about six months of tracking to get right. One quarter reveals patterns, two quarters reveals an objective truth, two years and you’re pretty dialed in.
Here's roughly how it builds:
Week 1: You'll see how much work is really in progress per person. This is the toughest week for leadership because it’s the week they feel most blindsided. People are often surprised by how much the team is managing or how much has slipped.
Month 1: You'll know where capacity is the tightest versus most available.
Month 3: You'll see patterns by client, project type, and time of year.
Month 6: You'll know how much work actually fits in your team's week, and you can staff to that instead of to 40 hours.
Why Starting Now is the Only Option
Here's the part that trips most teams up: they agree with all of this, then wait for a calm month to set it up properly. So it never happens.
Waiting for the perfect system is the definition of insanity. If you want to try the DIY approach, then this Friday, pull up your PM tool and count how many tasks each person has open. Then ask each of them to list everything they're actually working on. The favors, the revisions, the thing they're fixing for another team.
The gap between those two lists is the first thing you'll learn. Six months from now, you could be the only person in the room who actually knows how much work fits in your team's week. Or you could still be guessing.
If you want help turning that first count into a real capacity baseline, that's exactly what we do. Book a workflow session and we'll walk through it with you.
Clarity is a kindness. To your team, and to your margin.
