There is a meeting that happens in large organizations with some regularity, and everyone who has sat in a senior seat has attended it. Someone introduces a major initiative — an AI transformation, an organizational redesign, a strategic shift that has been building in the boardroom for months. The slide deck shows milestones and budget lines. Executives nod. By the time the room clears, the initiative is declared a top priority, fully endorsed at the highest level, and completely without an owner. The CISO thinks the CTO owns it. The CTO believes the business units are responsible for adoption. The business unit leaders point to the executive team for direction. The CEO says it belongs to the leadership team collectively. Nobody in that description is lying. Everyone is genuinely responsible. And so the initiative spends the next year drifting.
The Structure Was Designed This Way
LHH's 2026 C-Suite Research found that AI accountability gaps now define the leadership agenda at major organizations. Grant Thornton's 2026 report documented the same dynamic with more specificity: CIOs are installing technology that COOs say their people cannot use, CFOs continue to fund the next phase, and no CEO steps in to reconcile any of it. Boards overwhelmingly believe the C-suite owns the AI strategy. The C-suite, surveyed independently, largely disagrees. These are not failures of communication. They are features of an accountability architecture that was built, over decades, to assign labels without assigning ownership.
This distinction matters more than most senior leaders want to acknowledge. A label says: this function is yours to oversee. Ownership says: this outcome is yours to produce, and if it does not happen, you are the person who did not make it happen. Accountability structures at the top of most complex organizations are built to support the former and explicitly avoid the latter. The result is an org chart that shows who is responsible and a strategy that nobody is driving.
In organizations where co-ownership has replaced ownership, the accountability system is functioning exactly as designed. The structure was built so that visible failure would be distributed rather than attributable. The problem is not that something broke. The problem is that it worked.
What the Execution Layer Already Knows
The people executing below the C-suite register this problem before anyone at the top acknowledges it. They receive conflicting priorities from different executives who each genuinely believe the organization is aligned. They attend progress reviews where no one asks the most clarifying question available: who is responsible if this does not work? Industry data puts the downstream cost into concrete terms. Roughly 95% of organizations are seeing zero return on their generative AI investments despite significant capital allocation. Leadership team dysfunction — which almost always includes diffuse accountability at the executive level — reduces overall organizational effectiveness by more than 40%. Those numbers are not primarily technology problems or budget problems. They are accountability structure problems that show up first in the people who are supposed to be executing.
The diagnostic signal is straightforward, even when the fix is not. In organizations where strategic ownership is genuinely clear, someone four levels below the C-suite can name the specific person who owns the most important initiative the company is running this year. They can describe what that person said they are accountable for and what it means when that person says something matters. In organizations operating with co-ownership, ask the same question in five different rooms and get five different answers. The execution layer is not slow because middle management is resistant or because frontline teams lack urgency. It is slow because it is waiting for a signal that was never sent.
What Real Ownership Requires
This is where the conversation gets uncomfortable. Real ownership — in the context of a major organizational initiative — requires something most executive accountability structures are specifically built to avoid: visible personal risk attached to a named outcome. An owner, in the meaningful sense, is the person who would be most clearly wrong if the initiative fails, and who knew that before taking the seat. That is not a blame architecture. It is a clarity architecture. It answers, in advance, the question that every execution layer is perpetually asking: whose signal should I follow when the signals conflict?
Most organizations respond to the ownership gap by adding more structure — more steering committees, more reviews, more cross-functional alignment sessions. These interventions increase coordination overhead without touching the underlying problem. A director who has attended three alignment sessions this month still does not know whose judgment to trust when the CTO and the COO are pointing in different directions on a Tuesday afternoon. The structure multiplied. The ownership question was never answered.
The executive accountability structures built over the last two decades were optimized to protect senior leaders from being visibly wrong, and by that measure they worked. Now the cost of that design is showing up in every major strategic initiative that has stalled, every AI investment that is not generating return, and every execution team waiting for a signal that was never sent. The first move is not to restructure the org chart or add another governance process. It is to ask the question that the most recent alignment session never asked: if this initiative does not produce results by the end of the year, who is the specific person who did not make it happen?
In Chapter 10 of Agile Sucks!, five civilian contractors reduced hostile incidents in a combat zone from over 800 per month to under 50 in twelve months. One structural condition that made this possible was the absence of co-ownership. Each person's accountability was specific, the outcome was named, and there was no one else in the room to point to. The accountability was not assigned by an org chart. It was accepted by the people doing the work, and it held because it had no ambiguity about who would answer for the result.
Read Agile Sucks! (When You Do It Wrong) →