FM-01: Responsibility Compression
A pattern in the world. What it looks like from the edge.
Justin R. Greenbaum · The Lexicon · April 2026
A director is copied on a hiring decision she never actually participates in. A senior engineer inherits a migration whose scope was frozen two quarters ago by someone who has since left. A regional VP learns about a contract renegotiation through a customer complaint. A frontline supervisor is asked why NPS dropped in her region and starts the meeting by listing the six things she cannot change.
None of these people are failing. Each one is absorbing a system-level load that has been routed, informally, to the place where it can be held without renegotiation.
This has a name. It is Responsibility Compression.
The pattern is this. Responsibility is progressively pushed downward to the point of execution while authority, context, and decision rights remain upstream. Individuals closest to the work absorb accountability for outcomes they cannot meaningfully influence. The system appears responsive because humans compensate. Over time, responsibility collapses to the edge, where failures surface as burnout, churn, or “performance issues.” Upstream structures remain unchanged.
Compression masquerades as competence. High performers absorb more load and the organization calls it ownership. The team that worked the weekend is praised for grit. The regional operator who quietly built the workaround because the official process does not actually work becomes a case study in bias for action. The symptom is not dysfunction. The symptom is resilience.
What Responsibility Compression gets mistaken for is the thing that makes it durable.
It gets mistaken for grit, so you hire more of it and pay for it with turnover. It gets mistaken for ownership, so you spend leadership offsites teaching a behavior that the system is actively punishing. It gets mistaken for accountability culture, so you install OKRs and quarterly reviews on top of responsibility routes that have no authority paired to them. It gets mistaken for bias for action, so the people closest to the dysfunction are asked to move faster inside it.
None of these are substitutes for authority. A person cannot decide what they have not been given the decision rights to decide. A person cannot escalate what the organization has made expensive to escalate. A person cannot stop absorbing what the organization does not know is being absorbed.
The misdiagnosis is not incidental. It is the mechanism. Each of the four frames above is a hero narrative. Hero narratives are how Responsibility Compression survives contact with leadership.
Across twenty-seven years and four companies, I watched the same pattern recur and change costumes. In one place it wore the clothes of a lean operating model. In another it was packaged as a transformation program. In a third it was celebrated as what made the company different. The denominator was always the same. Someone at the edge was carrying the load that the design of the system had routed there because redesigning it was slower than letting them carry it.
The conditions that create the compression are structural, not behavioral. This is why individual-scale interventions do not interrupt it. Training the frontline harder raises the ceiling on absorption. Hiring more resilient operators increases the payload before collapse. Replacing the burned-out senior engineer with a new senior engineer resets the clock on the same geometry.
What interrupts it is structural. A single accountable owner, named, with decision rights and documented scope. Escalation paths that reduce risk rather than increase it. Leadership that absorbs consequence instead of distributing it. Removal of the incentives that reward silent compensation.
When Responsibility Compression has a name, the options change.
The person inside it stops taking the compression personally, which is the first structural move available to them. The manager above it stops evaluating the compressed person against outcomes they do not control. The executive responsible for the business unit sees that the high-performer attrition pattern is not a hiring problem. The board member reviewing quarterly results sees that the regional variance is not about regional management.
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-01, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-01.
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-10, Leadership Saturation. It is the shape the compression takes when the person absorbing it is also the person supposed to fix it.