Team Capability

The weekly leadership meeting has that familiar hum. The dashboards are mostly green. Everyone reports they’re busy, teams 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. It feels like driving with the parking brake on: burning fuel, making noise, not getting the speed you should.

This feeling has a name. It’s capability debt, 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 reach for one of two levers. Both feel decisive. Both are almost always wrong.

The first is hiring. The team can’t handle the new analytics platform, so we hire a data scientist. Problem solved? 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, and the rest of the team is no more capable than they were yesterday. Hiring a specialist resets their personal debt clock to zero. It doesn’t pay down the team’s collective balance.

The second is training. We send the whole team to a two-day workshop. They get a certificate. For a few days there’s a buzz. But a month later, how much do they remember? How much survives the next busy week?

This is where my background as a brain scientist kicks in. A fact heard once is a fact mostly lost. Without practice, we forget. A one-time training event is 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 compounds again the moment the workshop ends.

Here’s the reframe that changes everything. Capability is not a destination. It is not a skill you acquire and check off.

Capability is a rate of improvement you maintain.

The ground is always moving. A competitor ships a feature, a new tool gets adopted, a regulation changes. Every change opens a little new capability debt. The question is not whether the debt accumulates. It’s whether your systems for paying it down run faster than your systems for creating it.

How do you pay it down? The answer is deeply unsexy. Small, regular, structured repetitions. You do the actual thing, a little badly, in a safe place. Then you do it again, a little less badly, until it’s second nature. This is exactly why a billion-dollar corporate training industry sells you everything except it. Workshops and modules are easy to sell because they’re events, with a start and an end. Slow, steady, deliberate practice is just work. Unglamorous, and the only thing that has ever built a skill that lasts.

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

Durable learning isn’t built by cramming information in. It’s built by pulling it out. Forcing yourself to recall something strengthens the path back to it, and doing that over widening intervals is the most reliable way we know to make knowledge stick. Retrieval and spacing. It’s not new. It’s just hard.

I saw it firsthand scaling RoadBotics, the AI company I co-founded and ran to help governments manage their roads. We grew fast, the technology kept evolving, and we hired smart, driven people. But the true constraint was never talent. It was always capability. Could the sales team accurately explain the new model? Could operations use the new tools without errors? The answer was only yes once we stopped just announcing the changes and started building in the practice. When Michelin acquired us, the same pattern played out at global scale: the largest projects lived or died on one question, whether the people doing the work were genuinely capable of executing the new plan.

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

First, learn to see it. Capability debt shows up as friction:

• Rework. Which tasks get done over and over?
• Bottlenecks. Which processes always wait for one specific person?
• Avoidance. Which new tools or processes does the team quietly ignore, sticking to the comfortable old way?
• Burnout. Who is constantly heroic, saving the day? That person is paying everyone else’s capability debt with their own energy.

Once you see a specific gap, design the smallest rep that closes it. Don’t ask “who needs training?” Ask “what is the simplest repeatable action that closes this specific gap?” Is a new CRM field being filled in wrong? Don’t schedule a two-hour meeting. In the next standup, do a five-minute screenshare of the right way, then have each person double-check one teammate’s entry for the rest of the week. That’s the rep. Distributed, in the flow of work, active recall instead of passive listening.

Your job is to make it safe to be slow at first, and to celebrate the practice, not just the eventual polish.

This is a lens more than a checklist. Use it to see your team, your work, and your own role more clearly. It reframes the goal from hitting this quarter’s target to building the engine that can hit any target.

I write about this work every week, leading through change, building capable teams, and doing it without burning people out. The best place to follow along is LinkedIn, and the essays below go deeper. The first step is just to look: where is the interest payment on your team’s capability debt showing up today?

• Capability debt
• Capability under load
• What is Organizational Debt?
• What is Management Debt?
• Leading Through Change