top of page

The Accountability Gap: Why It’s Almost Never a People Problem, and What to Build Instead

  • 1 day ago
  • 2 min read

A while back, I sat with a CEO who had built a genuinely good leadership team. Smart people. Well-intentioned. Real commitment to the company. And yet nobody was holding anybody to anything. Deadlines slipped. Decisions got relitigated. And the CEO was quietly filling the holes herself, wondering why everything kept routing back to her.


Why This Looks Like a People Problem (And Isn’t)

If you lead a team, you’ve probably lived some version of this. And the instinct is to read it as a people problem. They’re not committed enough. They avoid conflict. They need to be tougher. Almost always, that read is wrong.


The accountability gap isn’t a values problem. It’s a structure problem. Most leadership teams are collegial. They like each other. They don’t want to create friction. And without a shared framework, clear roles, clear commitments, and a rhythm for checking in on both, accountability never actually gets established. It just gets assumed. Then it doesn’t happen, and the most senior person in the room becomes the accountability mechanism by default.



Accountability Starts With Definition

There’s a deeper layer underneath it, and it connects to something I’ve been writing about all month. You can’t hold people accountable to commitments that were never defined in terms of outcomes. When a commitment is vague, “let’s improve onboarding,” “let’s get aligned on pricing,” there’s nothing concrete to come back to. So the follow-up conversation feels like nagging instead of accountability, and everyone avoids it. Definition comes first. Accountability is what you build on top of it.


Three Things to Build

So, what do you build? Three things, none of them complicated.


First, clear commitments. Not a wish list. A short set of specific, owned, time-bound outcomes that the team agrees on out loud. Who is doing what, by when, and what does done look like.


Second, a rhythm. Accountability is not an annual event or a tense one-off. It’s a standing, low-drama cadence where the team looks at the commitments together and asks how they’re tracking. When it’s routine, it stops feeling personal.


Third, the honest conversation. Even with structure, someone has to be able to say “we committed to this and it didn’t happen, what got in the way?” without it becoming an attack. Most leaders were never taught how to do this. That’s a skill gap, not a willingness gap, and it’s learnable. The coaching piece matters here as much as the structure.


Where to Start This Week

Here’s a place to start this week. In your next leadership team meeting, pick one commitment that was made last month and didn’t happen. Name it out loud. Not to assign blame, but to model what it looks like to actually examine it. What got in the way? What’s the new commitment? That single conversation, done well, teaches the team more about accountability than any offsite ever will.


The CEO I mentioned didn’t have a bad team. She had an undefined one. Once the commitments were clear, the rhythm was set, and the honest conversation got modeled a few times, accountability stopped routing through her. It turns out the team was willing all along. They were just never given the structure that makes peer accountability possible.


Find the real problem. Do the real work. Build what lasts.


 
 
 
bottom of page