The best teams I’ve worked with share a common pattern: they have both ownership and accountability. After years of observing what makes teams truly effective, I’ve developed a framework that explains how to create and maintain this powerful alignment.

Full Agency

Quadrant 1: High Ownership + High Accountability - “Full Agency”

This is where magic happens. Teams control their destiny and own their outcomes.

Example: A product team owning their entire stack, choosing their technology, controlling their deployment pipeline, and being measured on actual user outcomes.

Characteristics:

• High morale and rapid innovation
• Quick decision-making
• Strong ownership culture
• Low turnover

What it sounds like: “We chose this approach and we’ll fix it if it breaks.”

Teams in this quadrant move faster because they don’t waste cycles on coordination overhead and political maneuvering. When you deploy directly to production and carry the pager, you’re incentivized to build quality in from the start. The coupling of ownership with accountability drives healthy behaviors that increase both velocity and quality.

Sometimes the biggest obstacle is recognizing you already have Full Agency. Teams may play it safe, thinking they need better test coverage or more mature observability before embracing continuous delivery. But often the capabilities are already there—the real barrier is fear. Research confirms this: teams with both autonomy and clearly defined responsibilities perform better across all key metrics.¹

Quadrant 2: Low Ownership + High Accountability - “Held Hostage”

All of the responsibility, none of the control. This is organizational cruelty.

Examples:

• A director told to “commit” to five OKRs when they said two was realistic, only to have priorities reset two weeks later
• A QA team owning the release process but unable to reject untested code, then dealing with the inevitable production incidents
• A customer success team measured on NPS but unable to influence product decisions

Characteristics:

• High burnout rates
• Finger-pointing and blame culture
• Talent exodus
• Teams embracing the Stockdale Paradox (brutal facts + faith they’ll prevail)

What it sounds like: “I told them this would happen but nobody listened.”

This quadrant destroys good people. I’ve watched talented engineers become cynical and disengaged when forced to be on-call for systems they can’t improve. The solution is often straightforward: give teams the ownership to match their accountability. In one case, moving release ownership to development teams led them to automate the entire process within two months. They solved their own pain once they had the power to do so.

Quadrant 3: High Ownership + Low Accountability - “Fiefdoms”

Teams control their domain but deflect when things go wrong. This breeds empire building and technical debt.

Examples:

• A team rejecting outside contributions, demanding tests be rewritten as structural inspection rather than behavior verification
• Architecture teams focused on technology rather than business problems, mandating tool choices without accountability for outcomes
• Teams exhibiting not-invented-here syndrome, rewriting working code without understanding its full scope, worsening developer experience and testability

Characteristics:

• Innovation theater without results
• Mounting technical debt
• Empire building and territorial behavior
• Unaware of problems they’re creating for others

What it sounds like: “This is how we do things here.”

These teams often exist due to short-sighted leadership that values delivering something fast over something maintainable, or values firefighting over fire prevention. Problems typically have to come to a head before inexperienced leaders recognize there’s even an issue, even when they’ve been warned.

Quadrant 4: Low Ownership + Low Accountability - “Rest and Vest”

Nobody controls it, nobody’s measured on it, it just… exists.

This is the theoretical quadrant, named after the “rest and vest” workers from HBO’s Silicon Valley who collected paychecks while hanging out on Hooli’s rooftop. It’s the organizational equivalent of Milton from Office Space: still on payroll but nobody knows what they do.

Theoretical characteristics:

• Work that exists but nobody owns or is measured on
• Systems running on inertia alone

While I haven’t encountered true “Rest and Vest” situations in practice (dysfunction may be tolerated but rarely is doing nothing), the quadrant exists as a logical endpoint when both ownership and accountability approach zero. Perhaps it manifests more as abandoned projects than abandoned people.

Diagnosing Your Organization

Ask these questions about any team or project:

1. “Who can change this process/code/decision?” (Ownership test)
2. “Who gets called when this breaks?” (Accountability test)

If the answers are different people or teams, you’ve found dysfunction.

The healthiest teams I’ve worked with have the same answer to both questions. This doesn’t mean everyone does everything. It means the unit of organization (the team) has coherent ownership and accountability. This creates healthy incentives.

The Matrix Structure Trap

Many organizations try to separate these elements intentionally, especially in matrix structures. “You own the implementation, they own the architecture, and this other team owns the outcome metrics.”

This sounds sophisticated. It’s not. It’s a recipe for turning your entire organization into “Held Hostage” teams with Fiefdom characteristics: the worst of both worlds.

Conclusion

Ownership and accountability work best as a package deal. Organizations that try to separate them create predictable patterns of dysfunction. Understanding these dynamics isn’t just academic—it’s the difference between teams that ship and teams that suffer.

Your action item: Take your most frustrating current project or team dynamic and map it to these quadrants. Then ask yourself: what would need to change to achieve Full Agency?

The answer might be uncomfortable. It usually requires giving up control or accepting accountability. But that discomfort is the price of building teams that actually work.

---

References

1. 2024 DORA State of DevOps Report. The report found that teams with “decision-making autonomy and access to necessary tools” combined with “clearly defined responsibilities” showed stronger performance across deployment frequency, lead time, change failure rate, and recovery time.