Accountability is one of those concepts that sounds simple until you try to build it into an organization.
The Version That Doesn’t Work
The version of accountability Eric Cecava started with was simple: set a clear expectation, measure whether it was met, and address the gap if it wasn’t. That sounds right. In practice, it produced compliance without ownership, which is not the same thing.
Compliance means people do what they’re measured on. Ownership means people care whether the thing actually works. The gap between those two is enormous in operational terms. A team that is compliant but doesn’t own the outcome will hit the metric and miss the point. A team that owns the outcome will find a way to make things work even when the metric doesn’t capture what’s happening.
This distinction showed up most clearly in quality reporting. Teams could be made to document the right things at the right intervals. What was harder was getting them to care about what the documentation represented. Compliance was achievable. The orientation that made compliance meaningful was something else entirely.
What Changed the Thinking
The shift came from watching how teams responded to failures. A team with compliance-based accountability would, when something went wrong, focus on whether the correct steps had been followed. If they had, the process was cleared and the outcome was treated as acceptable. The problem was that acceptable process and acceptable outcomes are not the same thing.
A team with ownership-based accountability responded differently. They wanted to know why the outcome was wrong, not just whether the steps were followed. The failure triggered investigation into the system, not just documentation of compliance. That orientation is what produces improvement over time.
The change in Eric Cecava’s own approach was to stop treating accountability primarily as a consequence mechanism and start treating it as a communication structure. What does this person understand about what they’re responsible for? Do they have what they need to do it? Is there something in the system that’s making it harder than it should be?
How the Framework Changed
The framework Eric Cecava uses now starts with clarity about the outcome, not the process. The outcome is what the team owns. The process is how they’ll pursue it, and it’s subject to revision when it stops working. Setting accountability to a process instead of an outcome is one of the most common ways organizations lock in underperformance.
The second element is making sure the team has what they need. Accountability without authority is frustration. People cannot be held responsible for outcomes they don’t control. Before holding anyone accountable for a result, it’s worth being confident they had the resources, the authority, and the information to produce it.
The third element is the follow-through. Accountability systems that don’t address gaps consistently don’t survive. If some people are held to a standard and others aren’t, the standard loses meaning. That consistency is uncomfortable sometimes. It’s what makes the system real.
What It Looks Like Now
The accountability structure Eric Cecava would build now looks less like a compliance framework and more like a series of ongoing conversations. Where are we against the outcome? What’s in the way? What does the team need? Those conversations, conducted regularly and honestly, do more for performance than any reporting structure.
The measurement still matters. But the measurement is a starting point for a conversation, not a conclusion. When a metric is off, the question is: what does this tell us about what’s happening? Not: who do we hold responsible?
Getting that right took longer than it should have. The work is still ongoing.