Capability Debt: The Unseen Drag on Your Team's Performance

The weekly leadership meeting has that familiar hum. The dashboards are mostly green. Everyone reports they are busy, their teams are fully booked. But the big project for the quarter is two weeks behind. A key client is unhappy about a fumbled handoff between sales and implementation. And one of your best engineers, the one who used to be fired up in every meeting, just looks tired.

Everything seems fine on the surface, but the engine is laboring. The work isn’t moving smoothly. It feels like driving with the parking brake on. You’re burning fuel, making noise, but not getting the speed you should.

This feeling has a name. It’s capability debt. It’s the invisible, compounding gap between what the work now demands of your people and what they can actually do, today, under pressure. It’s the difference between the org chart and reality. And most organizations are drowning in it without ever naming it.

When leaders feel this drag, they usually reach for one of two levers. Both feel decisive. Both are almost always wrong.

The first lever is hiring. The team can’t handle the new analytics platform, so we hire a data scientist. Problem solved, right? Not really. You’ve hired a skill, but you haven’t built a capability. The new hire has to learn your culture, your systems, your customers. The rest of the team is no more capable than they were yesterday. Hiring a specialist just resets their personal debt clock to zero. It doesn’t pay down the team’s collective balance.

The second lever is training. We send the whole team to a two-day workshop. They get a certificate. They learn the new process. For a few days, there’s a buzz. But a month later, how much do they remember? How much is actually being applied when things get busy?

This is where studying how the brain actually works comes in. A fact heard once is a fact mostly lost. Hermann Ebbinghaus measured exactly this back in 1885: a day after you learn something, only about a third of it is still there. The one piece of good news is that the curve flattens, so the loss is not total. And the fix he found is still the best we have. Spacing the repetitions out. In his own data, thirty-eight repetitions spread over three days did the work of sixty-eight crammed into one. A one-time training event is like making a single, large interest payment on a massive loan. It feels good in the moment. It stops the angry phone calls for a week. But it doesn’t touch the principal. The debt remains, and the interest starts compounding again the moment the workshop ends.

Here is the reframe that changes everything. Capability is not a destination. It is not a skill you acquire. It is not a box you check.

Capability is a rate of improvement you maintain.

The ground is always moving. A competitor ships a new feature. A new piece of software is adopted. A key regulation changes. The market shifts. Every single change opens up a tiny bit of new capability debt. The question is not whether the debt will accumulate. The question is whether your systems for paying it down are running faster than your systems for creating it.

And how do you pay it down? The answer is deeply unsexy. You pay it down with small, regular, structured repetitions. You do the actual thing, a little bit badly, in a safe environment. Then you do it again, a little less badly. You do it until it becomes smooth.

This is precisely why a billion-dollar corporate training industry exists to sell you everything except this. Because workshops and e-learning modules are easy to sell. They are events. They have a start and an end. But a process of slow, steady, deliberate practice? That’s just work. It’s unglamorous. But it’s the only thing that has ever actually built a skill that lasts.

This isn’t just a leadership aphorism. It’s grounded in a century of memory science and the real-world scars of building a company.

The science is clear, and it is old. Durable learning isn’t built by cramming information into our heads. It’s built by pulling it out. This is called retrieval practice. In one of the cleanest studies on it, by Roediger and Karpicke, the group that mostly tested itself read a passage about three times; the group that just reread it went over it about fourteen. A week later, the testers remembered more. The retrieval is the thing, not the re-reading. Spreading that retrieval out over time, known as spaced practice, makes it stick even better. The catch most people miss is that the right gap is not simply “longer.” It scales with how long you need to remember something, and stretched too far, recall actually drops. None of this is new. It is just hard to sell.

I saw this firsthand scaling my last company, RoadBotics. We built AI to help governments manage their roads. We were growing fast, and the technology was constantly evolving. We hired smart, driven people. But our true constraint was never talent. It was always capability. Could the sales team accurately explain the new machine learning model? Could the operations team use the new internal tools without errors? Could a new project manager run our discovery process with a new client?

The answer was only ‘yes’ when we stopped just announcing the changes and started building in the practice. We funded the boring work of building capability, not just the exciting work of building features. When we were acquired by Michelin, I saw the same pattern play out on a global scale. The largest, most complex projects lived or died on one question: were the people doing the work genuinely capable of executing the new plan?

So what do you do? You can’t boil the ocean. You have to start small. The leader’s job is to become a detector for capability debt and an architect of small, effective reps.

First, learn to see the debt. It shows up as friction. Look for the symptoms:

• Rework: Which tasks have to be done over and over?
• Bottlenecks: Which processes always get stuck waiting for one specific person to review or fix them?
• Avoidance: What new tools or processes are being ignored by the team, who stick to the old, comfortable way?
• Burnout: Who on your team is heroic, constantly saving the day? That person is paying everyone else’s capability debt with their own energy.

Once you see a specific point of debt, your job is to design the smallest possible rep to start paying it down. Don’t ask, “Who needs training?” Ask, “What is the simplest, repeatable action that closes this specific gap?”

Is a new field in your CRM being used incorrectly? Don’t schedule a two-hour meeting. In your next team standup, do a five-minute screenshare showing the right way. Then, for the rest of the week, have each team member double-check one entry for a teammate. That’s the rep. It’s distributed, it’s in the flow of work, and it’s active retrieval, not passive listening.

Your job is to create the conditions for this practice. To make it safe to be a little slow at first. To celebrate the practice, not just the eventual perfection.

This isn’t a problem you solve by reading one article. Naming capability debt is just the first step. Seeing it, measuring it, and building the systems to pay it down is the core work of modern leadership.

It’s a lens. You can use it to see your team, your work, and your own role more clearly. It reframes the goal from hitting targets to building the engine that can hit any target, now and in the future.

I write about this work every week: leading through change, building capable teams, and doing it without burning out. You can follow the ongoing conversation on LinkedIn, or read more of the essays here on the site.

The first step is just to look. Where is the interest payment on your team’s capability debt showing up today?

• What is Technical Debt?
• What is Debt Financing?
• The Founder’s Ledger: What to Keep, What to Give Away, and How to Tell the Difference
• What is Debt Service?
• What is Senior Debt?