Capacity, Clarity, Skills: You're Probably Fixing the Wrong One

The reason your team's training doesn't stick, your best insight doesn't move, and "just try harder" never works. And how to tell which one you’re dealing with.

Read Time: 6 minutes

When I was building global training programs at Airbnb, leaders were constantly saying "we need to level up the team." That made sense as we continued to grow, but I've heard a version of it in coaching at almost every organization since.

Sometimes it's "we need better training." 

Sometimes "we needed this yesterday." 

Sometimes "how do we get more efficient." 

Sometimes it's just, "I need more time."

Every one of these is a real feeling, and almost every one is pointed at the wrong thing. I’ll tell you why.

When something isn't working, when the training didn't stick, when the team isn't stepping up, when you learned the thing and still aren't doing the thing, it feels like one problem. So we reach for the most visible lever: more instruction, more skills, or more speed, essentially putting effort towards fixing it downstream.

But that one feeling is usually three different things wearing the same mask, and until you can tell them apart, you'll keep throwing solutions at the wrong layer and wondering why nothing changes.

The three things are capacity, clarity, and skills. People typically collapse them which causes them to stay stuck, or for their team to stay stuck. So let me pull them apart.

Capacity vs. Clarity vs. Skills

Capacity = do you have the space?

Capacity is the time, mental, and emotional bandwidth to take something in, practice it, and turn it into behavior. From the inside it feels like space to think, or, more often, the absence of it: too much on your plate, managing the day rather than leading it, feeling like you have too many tabs open and unresolved in your brain (these could be things having to do with work, life, or world events).

You can hand someone the best training in the world, but if they have no bandwidth to absorb it, it evaporates. Not because they're incapable, but because a brain that's underwater can't take on new water. (There's real neuroscience here, the thinking brain goes quiet under sustained pressure, but that's its own story.) Capacity isn’t typically identified because it doesn’t always look like a problem to fix. It looks like a full calendar, or a busy brain, and it’s accepted as the way things are.

Clarity = do you have the direction?

Clarity is knowing what the specific situation actually needs. Not "do I know how to delegate," but "is this even something that should be delegated, and to this person specifically?" It's the difference between owning a full toolbox and knowing which tool this job takes. From the inside it feels like the fog lifting: oh, that's what's going on here.

Skills = do you have the ability?

Skills are the competencies themselves: do you know how to give feedback, run the meeting, or scope the project? It’s the one everyone reaches for first because it's the most visible and the most fixable. It's teachable, testable, and real. When a skill is genuinely missing, no amount of calm or clarity will generate it. You have to learn it. This is the trap: because skill is the layer we can see, we assume it's the one that needs fixing, and sometimes it is, but oftentimes it isn’t.

The simplest way to decipher these: capacity is space, clarity is direction, and skill is ability. You can have all the space in the world and have no idea where you're headed. You can know exactly where you're headed and lack the ability to get there. And you can have every ability and no space to use any of it.

The part that matters is the order.

You can't skip to skill, because capacity and clarity are what let a skill take root. A skill dropped into someone with no space and no direction has nowhere to land. It's like seeds scattered on pavement, nothing can take root.

I know this because I ran a test.

For most of a decade at Airbnb I built the plane while flying it, designing policies and programs while we were already running on them. Through hyper-growth I built our Trust and Safety training function and taught hundreds of people how to lead, decide under pressure, and have hard conversations. And I was good at it. People walked out of that room able to do things they couldn't do walking in, and passed the assessment to prove it.

And then there were moments when functional leads would tell me the training didn't work. People weren't doing the things they'd just demonstrated they knew.

For a while I agreed, it must be a training problem. It took me years, and my own first burnout, to see the skill was never the problem. We were in hyper-growth: every inbox was overflowing, every queue was backed up, we had pizza parties to claw through the backlog. We couldn’t onboard people fast enough and these new employees were learning new skills with zero bandwidth to absorb them, some literally working their queues during the training. The issue was capacity, and no amount of training was sticking because you can't convert what you have no space to absorb.

So we tested it. Two onboarding cohorts, a dozen people each. One got the shorter program the leads wanted: efficient, productive, and fast. The other got a longer version, longer not because we added content, but because we added implementation sessions: built-in space to practice, ask questions, and work through how the skills applied to real situations. That's the moment an abstract skill found its actual home and could be applied. And every time skills were applied, they became easier to reach for.

At the 90-day mark, the cohort with more implementation time was more productive, showed sharper critical thinking, and had made real improvements to their operational processes. They also stayed longer. The only variable that was different with this group was more space.

The setting in this case was tech, but the mechanism is the same for humans in any team: any time you ask people to change how they work while they're underwater, the same thing happens. Capacity gave folks the space to think, which allowed them to gain more clarity so they could apply the skill properly, and only then did the skill convert into behavior.

The thing that most organizations miss is that those sessions are the first thing "efficiency" wants to cut, because they look like fat. But that's the whole point. When you optimize for speed without looking at effectiveness, you cut the exact thing that makes the learning stick, and then wonder why it didn't. This isn’t an efficiency win, it’s a retention problem that hasn’t had a price tag assigned to it yet.

"I need more time" is the most honest thing a person under pressure can say, though what they need isn't hours, it's space to think. The reflexive answer is "go faster," or "try harder,” which starves people of the one thing they need (space) and calls it discipline.

Sometimes it really is the skill (but never ONLY the skill)

None of this means skills don't matter. Sometimes, once you've cleared capacity and clarity, a genuine skill gap is exactly what's left, and no amount of space will fill it.

I worked with a leader drowning under a team that wouldn't stop asking permission for everything. He read it as a performance problem. But he was on autopilot, moving too fast to see his own pattern: he was handing over rigid, step-by-step checklists instead of outcomes, the how without the why, so his people had no space to problem-solve and no choice but to keep checking in. 

The very thing he did to buy back time was generating the pings eating his time. 

In coaching, he finally had space to think (capacity) and saw the pattern (clarity). But seeing it wasn't the fix. Underneath was a real, teachable skill he'd never learned: how to delegate an outcome instead of a procedure. We built it, and his team finally ‘stepped up.’ 

Notice the layers: it looked like his team's failure, turned out to be his own, and even then, more space or more clarity wouldn't have solved it, only the skill would. But he couldn't have learned that skill while drowning and blind to the pattern. Capacity opened the door, clarity walked him to the right doorway, and the skill got him through it.

Diagnose the layer, then act.

Next time something isn't sticking, on your team or in yourself, resist the reflex to grab the most visible lever.

Here's the key: you diagnose in the opposite direction from how you build. The layers get built bottom-up (capacity, then clarity, then skill), but you troubleshoot top-down, starting with the visible layer and working underneath it.

Start with skill. Is it genuinely a case of not knowing how? Teach it, or go learn it, but it won't stick without the space to absorb it. If the skill's already there, the block is underneath. Keep going.

Then clarity. The skill exists, but not the sense of when or why to use it here? The work isn't more instruction, it's the space to connect what's known to what's in front of you (applying theory to the real world situation).

Then capacity. Is there any space to absorb this at all, or is everyone underwater? If it's this, no amount of training or insight will land. The space has to come first.

Getting the diagnosis right is what determines whether anything actually changes.

The uncomfortable truth for anyone optimizing for speed: capacity and clarity are the two things you’ll skip first, because they feel like the opposite of speed. But they’re not a delay before the real work, they are the real work!

If you skip them, you'll pay later anyway, in the skill you keep half-using, in the training that never sticks, and in the widening gap between what you know and what you actually do. It cultivates a disconnect between your intention and your impact.

Clarity that never converts into action is just a nicer kind of stuck. That conversion, clarity into aligned action, is its own practice, but it can't come first. First, you have to build the conditions where clear thinking is even possible.