Deliver What Matters · LinkedIn
Accountability Without Authority Is a Trap
Organizations often say they want teams to own outcomes.
They want teams to improve user experiences. They want faster delivery. They want better mission results. They want teams to take initiative, solve problems, and continuously improve.
In other words, they want ownership. But ownership requires something many organizations struggle to provide: Authority .
Without it, accountability becomes a trap.
At CAIP, there was no shortage of people who cared about improving the experience. The team could see where applicants struggled. They understood which parts of the process created confusion. They knew where delays were occurring and where staff were forced into manual workarounds.
The problems weren’t hidden. In many cases, the people closest to the work understood them better than anyone else. But recognizing a problem and having the authority to address it are not the same thing .
The team could identify issues. They could make recommendations. They could explain the impact. But many of the decisions that shaped the experience lived elsewhere.
Priorities were established elsewhere.
Funding decisions were made elsewhere.
Requirements were often determined elsewhere.
Sometimes even the definition of success was determined elsewhere.
The team was expected to improve outcomes while operating within decisions they did not control. That tension is more common than most organizations realize.
This is where accountability begins to break down. Leaders often assume accountability means assigning responsibility.
A team is told: “You’re responsible for improving the experience.” Or: “You’re accountable for reducing processing time.” Or: “We need better outcomes from this effort.”
Those expectations sound reasonable. The problem emerges when teams lack the authority to influence the factors that determine those outcomes. When that happens, accountability becomes little more than expectation without empowerment.
Imagine asking someone to improve customer satisfaction while preventing them from changing the experience. Or asking someone to reduce processing time while limiting their ability to modify the workflow. Or asking a team to improve outcomes while requiring approval from multiple layers of leadership before making even minor adjustments.
Eventually, teams stop acting like owners because the system teaches them not to.
Most people have experienced some version of this.
A problem is obvious. A solution seems clear. The team is motivated to help. But before anything can happen, the idea must move through reviews, approvals, committees, governance boards, funding discussions, and competing priorities.
Weeks become months. Months become quarters. Momentum disappears.
The lesson people learn is subtle but powerful:
Seeing the problem doesn’t mean you can solve it.
Over time, that lesson shapes behavior.
People stop asking certain questions.
They stop challenging assumptions.
They stop looking beyond the next request because they’ve learned where their authority ends.
This is one of the reasons delivery often becomes the default focus. Delivery is something teams can control. Outcomes are not always.
When authority is disconnected from accountability, teams naturally gravitate toward the things they can influence. They focus on completing work. Closing tickets. Meeting deadlines. Delivering commitments.
Those activities are visible. They’re measurable. They’re achievable.
Improving outcomes is much harder when many of the decisions that shape those outcomes are outside the team’s influence.
Ownership requires more than responsibility. It requires decision-making authority .
Not unlimited authority. Not the absence of governance. Not freedom to do whatever a team wants.
Authority simply means the people closest to the problem have enough influence to act on what they learn .
They can challenge assumptions.
They can propose alternatives.
They can adjust priorities.
They can test ideas.
They can respond to evidence.
They can help shape the path forward rather than simply execute it.
That is very different from being an order taker.
At CAIP, progress accelerated when authority moved closer to the problem . Not perfectly, but enough for teams to influence decisions instead of merely reacting to them.
The conversations changed .
Instead of asking: “What should we build?” Teams started asking: “What’s the best way to improve this outcome?”
That’s a different conversation. And it produces different decisions.
Many organizations believe they have an accountability problem. What they often have is an authority problem .
They want ownership without empowerment. Responsibility without influence. Outcomes without decision-making authority.
Those combinations rarely work for long because accountability without authority doesn’t create ownership. It creates frustration.
If we want teams to own outcomes, we have to give them more than responsibility. We have to give them enough authority to influence the results they’re expected to achieve.
Otherwise, we’ll continue asking teams to improve conditions they were never truly empowered to change.
And that isn’t accountability. It’s a trap.
Where are teams being held accountable for outcomes they aren’t empowered to influence?
Reply or comment—I read every one.
CAIP is a program we follow throughout my book, Deliver What Matters.