Is It A Capacity Problem Or A Decision Problem?

Most of the time, when someone says they have a capacity problem, what they’re actually describing is the downstream effect of a series of decisions that were never fully made. It shows up as capacity. Work is backing up, timelines are slipping, people are stretched, you’re in more things than you expected to be, and there’s a constant sense of “we just need a little more room.” So the natural conclusion is: we need more capacity... more people, more time, more space.

But if you zoom out, there’s often a different pattern underneath.

Work was taken on without a clear definition of what "done" actually looks like. Not just the deliverable but how far it goes, what it includes, and where it stops. Things were said yes to quickly, in the moment, without fully tracing what that yes sets in motion.

Decisions that should have narrowed scope didn't. Often, they've invisibly expanded it.

The work gets stretched. A little extra effort here, a little there. One extra round, one more request, one more thing that “makes sense.” Nothing dramatic. But it keeps expanding to fill the gaps.

None of those feel like capacity issues in the moment. They feel reasonable. Sometimes even necessary. And then, a few weeks later, something starts to feel off. Not just “busy" but more like everything is slightly harder than it should be. Work takes longer and things feel heavier.

People are holding more in their heads. You’re in more of it than you expected to be. Things that should be straightforward require more coordination, more cleanup, more checking. And from the inside, it’s confusing. Because you didn’t make a "bad decision". You made a series of reasonable ones.

But those reasonable add-ons compound. And now you’re solving for capacity… inside the same set of decisions that created the pressure. That’s why adding capacity typically doesn’t fix it. You hire, and the work expands to meet the new space. You carve out time, and it gets filled just as quickly. You try to protect the team, but the inputs haven’t changed, so the strain just redistributes.

I've seen this so many times throughout my career:

You bring someone on to take things off your plate, but you’re still in the work—onboarding, training, managing, reviewing, clarifying, stepping in to smooth things out—because the shape of the work itself never actually got cleaner. Or you block time to “get ahead,” and instead spend it catching up on things that shouldn’t have needed that much attention in the first place.

From the outside, it looks like growth. From the inside, it feels like you’re always slightly behind.

The shift is to recognize where capacity strain is the symptom, not the cause.

It shows up in moments that don’t feel like big decisions. A quick yes in a meeting. Letting something stay open because you don’t have time to fully define it. Taking on a piece of work because it’s faster than explaining it. Letting a deliverable expand because pushing back feels heavier in the moment.

Those are the moments that shape everything that comes after.

And they’re not easy to navigate in real time. They require you to slow down just enough to take context into account. Thinking about what could be impacted downstream, who will be affected, and whether or not there is enough added value to say "yes". That all feels like friction, especially when things are moving quickly.

But those are the kinds of decisions that change how things go and what needs to be managed during execution.

When those moments are handled cleanly, the work holds its shape. It doesn’t keep stretching. It doesn’t require the same level of correction later.

And when that starts to happen consistently, capacity behaves very differently. Not because you suddenly have more of it, but because you’re no longer generating the same kind of strain.

So before you solve for capacity, it’s worth asking:

Is this actually a capacity problem or is it a decision we made that’s showing up as a capacity issue?