FM-03: Responsibility Without Authority
A pattern in the world. What it looks like from the seat that owns without rights.
Justin R. Greenbaum · The Lexicon · April 2026
A VP of customer experience is held accountable for NPS. Half the score is driven by the billing experience, which is owned by Finance and runs on a release calendar she does not control. A head of conversational AI owns the bot’s CSAT score. The knowledge base the bot answers from is maintained by Marketing on its own roadmap. A care operations director is asked why first-call resolution dropped four points. The policy exceptions that would actually resolve the top customer complaint live in Risk. A frontline supervisor is asked why agent turnover spiked. The compensation bands and shift structures were set by HR two budget cycles ago without operations input.
None of these people are failing. Each one is absorbing a structural mismatch the system has routed onto a role rather than designed out of itself.
This has a name. It is Responsibility Without Authority.
The pattern is this. Accountability for outcomes is assigned to individuals or teams who lack the formal authority, resources, or decision rights required to change the underlying conditions. Performance is demanded without control. The system appears to function because the people inside it absorb the gap. Over time, the absorption is read as ownership.
Mismatch masquerades as accountability. The team that hits the number through coordination overhead is praised for grit. The manager who closes the gap by trading personal favors across reporting lines is described as a strong operator. The director who absorbs the constraint quietly is identified as high-potential. The signal the system reads is performance. The condition underneath is an authority distribution no one is empowered to change.
What Responsibility Without Authority gets mistaken for is the thing that makes it durable.
The misdiagnoses all rhyme. Ownership gap. Skills problem. Execution weakness. Escalation discipline. Each is a hero narrative. Each is how the system rewards the behavior that is wearing the person down. Leadership development teaches a behavior the structure is punishing. Coaching asks managers to push through constraints they cannot move. New escalation paths get added on top of paths whose resolutions are non-binding.
None of these substitute for authority. A person cannot decide what they have not been given the rights to decide. A person cannot escalate what the organization has made expensive to escalate. A person cannot keep absorbing what the organization has not equipped them to refuse.
Hero narratives are how Responsibility Without Authority survives contact with the operating committee.
The pattern recurs and changes costumes. In one organization it shows up as decentralization, with accountability decentralized while authority is quietly held at the center. In another, as an accountability culture with KPIs distributed to teams whose decision rights were not. In a third, as a flat operating model where the org chart is flat and the authority is not.
The conditions are structural, not individual. This is why training does not interrupt it. Training raises the ceiling on absorption. Better hiring delays the collapse. Replacing the exhausted operator with a fresh one resets the clock on the same geometry. None of these touch the asymmetry.
What interrupts it is structural. Authority realigned at the point of accountability. Decision rights tied to the outcomes a person owns. Escalation paths whose resolutions are binding. Permission to change rules, not only to comply with them. Where realignment is not possible, the cleanest move is to formally remove the responsibility rather than absorb the cost of holding it.
When Responsibility Without Authority has a name, the options change.
The person inside it stops taking the gap personally, which is the first structural move available to them. The manager above it stops evaluating that person against outcomes they have no rights to influence. The executive responsible for the function sees that the recurring miss is not a manager problem and that another layer of measurement will not move the constraint. The board reviewing the variance sees that no amount of accountability rhetoric will restore performance until decision rights move.
Naming does not fix. Naming changes what can be seen. What can be seen is what can be acted on.
If any of this feels familiar, it has a name and a taxonomy.
The canonical definition of FM-03, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-03.
A role-specific view of how the same pattern looks from the operator’s seat is at dripractice.com/lens/01.
A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.
Next in The Lexicon: FM-08, Decision Latency. It is what happens to the whole organization once enough Responsibility Without Authority gaps stack. Every decision needs alignment from places that were never paired with it. The decisions slow.
Subscribe to The Lexicon.