There’s a conversation that happens in almost every organization I work with, in one form or another. A leader is frustrated because their team keeps dropping the ball on something. The balls are different every time: a deliverable that keeps slipping, a process that nobody follows consistently, a decision that should have been made weeks ago. But the frustration is always the same: why can’t they just be accountable?

Here’s the uncomfortable question I always ask: accountable to what?

Accountability without infrastructure isn’t accountability. It’s blame. And there’s an important difference. Real accountability requires clarity about what you own, genuine authority to act on what you own, and consequences that are proportionate and predictable. Take away any one of those and you don’t have an accountability structure. You have a frustration structure — a system perfectly designed to generate resentment in all directions.

Most small organizations have the consequences part figured out. That’s usually not the problem. The problem is the first two. People don’t have clear enough ownership. Or they have nominal ownership but no actual authority. They’re responsible for outcomes they can’t control because the decisions that drive those outcomes still route back to the founder or the executive director.

“When a system fails, the honest question isn’t who dropped the ball. It’s who designed the field.”

I worked with a nonprofit some time ago that was perpetually frustrated with their program staff for missing reporting deadlines. The staff was competent and genuinely committed. The deadlines kept getting missed anyway. When I started asking questions, what I found wasn’t a people problem. It was a system problem. The reporting templates changed frequently and without notice. The approval process required sign-off from someone who was chronically unreachable. The data needed for the reports lived in a system that program staff didn’t have full access to. The deadline kept getting missed because the system made it nearly impossible to hit.

But the conversation at the leadership level was entirely about accountability. Why won’t people just take this seriously? Why do we always have to chase this down?

When I showed the executive director what I’d found, her first reaction was embarrassment, not defensiveness. She hadn’t designed the obstacle course intentionally. It had just accumulated incrementally, the same way most operational friction does. One workaround at a time, with nobody pausing to ask whether the path still made sense.

The most important discipline in building accountability is learning to separate system failure from individual failure. Before you have the accountability conversation, ask whether the person actually had everything they needed to succeed. Clear ownership. Real authority. Access to the right information. A process that was actually followable. If any of those were missing, the accountability conversation is the wrong conversation. The system conversation is the right one.

Build the infrastructure. Then hold people to it.