When a leader tells me their team has an accountability problem, I don’t start with the team.
I start with asking the leader questions.

In fifteen years of coaching founders and executives, I’ve found that accountability is almost never the root problem. It’s a symptom. And until you find what’s underneath it, you can replace people, run workshops, post core values on the wall, and the same problem will keep showing up with different faces.

What Leaders Mean When They Say “Accountability”

Before we talk about root causes, it helps to understand what leaders are actually describing when I hear them use the word “accountability.”

Usually it’s one of these: we’re not hitting our goals, people aren’t doing what they said they’d do, things aren’t getting done fast enough. Sometimes it’s more cultural. People don’t seem to care, they don’t seem stressed, they don’t seem as invested as I am.

That last one is worth pausing on.

Because sometimes what looks like a lack of accountability is actually just a difference in wiring. A leader who is highly urgent, highly visible about their intensity can misread a calm, methodical team member as someone who doesn’t care. The work gets done. It just doesn’t look the way the leader expects it to look.

Before you conclude you have an accountability problem, make sure you’re not actually looking at a perception problem.

The Real Root Causes

If it’s not a perception issue, here’s where I actually look.

The most common cause is lack of clarity. People weren’t aligned on what success looked like. The leader thought this, the team thought that, and when the outcome didn’t match expectations, someone got blamed for not being accountable.

That’s a communication failure, not an accountability failure. And the communication failure almost always starts at the top.

The second is overload. People can’t be accountable for more than they can actually do. If someone is stretched across six priorities and you keep adding a seventh, things are going to drop.

Some people won’t say no to their boss even when they should. They take on more than they can handle, and then they fail at something, and then you call it an accountability problem. It isn’t. You created the conditions for it.

The third is environment. When people stop caring, when morale is low, when someone toxic is allowed to stay, when mistakes are punished instead of learned from, accountability collapses.

Not because people are lazy, but because the environment stopped making accountability feel worth it. You can’t demand accountability in a culture that penalizes failure.

And then there’s the one leaders like least: sometimes the problem starts at the top. Their own behaviors, their own inconsistency, their own failure to model what they’re asking for. You can’t build an accountable team while being an unaccountable leader.

What I Actually Did About It

I worked with a CEO whose leadership meetings were running ninety minutes and accomplishing very little. He’d go around the table and ask everyone what was going on. People would share updates. Some conversations would spiral. By the end, they’d have chitchatted a lot and made very few decisions.

The first change I suggested was simple: build a scorecard. Each leader was responsible for a handful of numbers. Every week, before the Monday meeting, they updated it. Now the meeting had a spine.

That helped, but they were still getting stuck. When a number was off, the CEO would ask why, and the whole room would try to diagnose it together. Forty-five minutes on one problem. No resolution.

So I suggested one more change.

Stop asking why.

Start asking: What are you doing about it?

That question changed everything.

Instead of defending themselves, people came prepared. Instead of the team trying to solve each other’s problems in real time, each leader owned their numbers and owned the path forward. The meeting went from ninety minutes of noise to under thirty minutes of alignment. He started being seen as one of the most effective CEOs in his peer network.

One question. Different outcomes.

What Real Accountability Requires

The word gets thrown around so much it’s lost its shape. So let me be specific about what it actually takes to build it.

First, agreement. People have to know exactly what they’re accountable for and what success looks like. Not in general terms. Specifically. If I tell my COO they’re accountable for profitability, we need to agree on how we keep score, what decisions they have the authority to make, and what they flag to me versus handle themselves. Accountability without definition is just expectation without structure.

Second, authority. You can’t hold someone accountable for an outcome they don’t have the power to influence. If they need approval for every decision, if they have to run things up the chain before acting, they’re not accountable — they’re executing. Accountability requires real decision-making authority to go with it.

Third, bandwidth. Don’t make someone accountable for something they don’t have the time or resources to actually do. This sounds obvious. It’s one of the most common mistakes I see.

Fourth, safety. People have to know that taking on accountability doesn’t mean taking on the full personal cost of every failure. Growth isn’t linear. Mistakes happen. If the environment punishes every miss, people stop raising their hands. They stop owning things. They do what they’re told and nothing more.

One of the things I’ve borrowed from clients who’ve used a system like EOS is their accountability chart. A hierarchical map of who owns which accountabilities and outcomes, not who reports to whom. It creates clarity, reveals where people are overloaded, surfaces where the next hire needs to go, and makes the invisible visible. Most organizations have an org chart. Very few have an accountability chart. They’re not the same thing.

Here’s the Hard Part

When I sit down with a leader who says their team isn’t accountable, the conversation we end up having is almost never about the team.

It’s about the environment they built. The expectations they set, or didn’t set. The decisions they made that created the conditions their team is now operating in.

That’s not a comfortable conversation. Most leaders would rather replace a person than examine a system.

But if you replace the person without fixing the system, the next person inherits the same problem.

I’ve watched it happen. The leader fires the underperformer, brings in someone new, and six months later they’re saying the same things. New person, same issue.

At some point you have to ask what the common denominator is.

The team isn’t always the problem.

It’s just where the system breaks first.