On day three, a new analyst is told to ignore the documented close process and follow a spreadsheet a senior colleague maintains by hand, because the documented process stopped matching reality years ago. A billing operations lead is the only person who knows the nightly sequence that reconciles two systems nobody ever integrated, a sequence that runs every night and appears in no runbook. An automation team’s project to digitize an approval flow keeps stalling on “edge cases,” and the edge cases turn out to be the actual operating process; the documented flow is the exception. A team’s numbers hold steady the week their most experienced coordinator is on leave, until the third day, when three handoffs she had been silently absorbing start failing in sequence.

None of these people are failing. Each one is holding a piece of the system that no design holds.

This has a name. It is Normalized Workarounds.

Here’s the pattern. Temporary fixes, exceptions, and informal sequences become permanent operating infrastructure. The formal system stops being the source of truth, and the organization can no longer tell the difference between how the work is supposed to happen and how it actually happens. Stability comes from memory, not architecture. The system stops improving and starts surviving on accumulated human patches, and the people holding those patches look, from the outside, like the most capable people in the building.

Endurance masquerades as resilience. The person who “just makes it work” is praised for ownership. The team that absorbs a broken handoff every week is called adaptable. The tribal knowledge that keeps a fragile process alive is filed as institutional strength. The workaround that should have been a two-week fix is, three years later, called how things work in the real world. The signal the system reads is resilience. The condition underneath is a system that has quietly stopped being designed.

What Normalized Workarounds gets mistaken for is what makes it durable.

Resourceful people. Strong ownership. Tribal knowledge. Operational maturity. Each is a hero narrative, and each is how the system rewards the behavior that is hollowing it out. Praising the person who makes it work removes any pressure to fix what they are working around. Documenting the workaround blesses it as the standard. Onboarding new hires into the workaround scales it. Building automation on top of it encodes it in software, which is where it becomes permanent.

Hero narratives are how Normalized Workarounds survives contact with the automation project.

The pattern recurs and changes costumes. In one organization it shows up as a reconciliation that only runs because one person stays late. In another, as an onboarding that teaches the unofficial process first and the official one for the audit. In a third, as an automation initiative that keeps failing on the cases that are not edges at all, but the route the work has actually taken for years.

The conditions are structural, not behavioral. This is why training the operator does not interrupt it; it raises the ceiling on the workaround. Hiring more people does not interrupt it; it teaches the workaround to more people. Replacing the person resets the clock on the same geometry. None of these remove the constraint that made the workaround necessary.

What interrupts it is structural. Remove the constraint the workaround exists to bridge, rather than formalizing the bridge. Reassign authority to the layer that has been absorbing the work. Make the workaround impossible to perform, and accept the short-term disruption that surfaces. Where the root constraint cannot be removed yet, the cleanest move is to freeze workaround expansion: no new exceptions until at least one is retired.

When Normalized Workarounds has a name, the options change.

The operator who has been the single point of failure stops reading her own indispensability as job security and sees it as a structural risk the system is asking her to carry. The manager above her stops praising the save and starts asking what made the save necessary. The executive sees that the automation project keeps failing because it is being pointed at a process nobody actually designed. The board sees that operational continuity and system health are not the same reading, and that one has been standing in for the other.

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-05, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-05.

A role-specific view of how the same pattern looks from the operator’s seat is at dripractice.com/lens/the-operator.

A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.

Next in The Lexicon: FM-02, Escalation Inversion. The workaround persists because the problem never traveled up. Escalation is the path that was supposed to carry it, and FM-02 is what happens to that path.

Subscribe to The Lexicon.

A senior staff engineer who used to flag architecture risks in design reviews has stopped. The reviews still happen, but her comments are narrower now, scoped to the technical detail in front of her. Three of her last four structural escalations were acknowledged and not acted on. A regional VP runs the all-hands, where engagement scores hold steady year over year and the questions submitted in advance are softer than last year, which she reads as alignment maturing. Two of her top three performers have quietly told their managers they are looking outside. A director of operations sends the weekly risk register up the chain. The register has not changed in eleven weeks, and the new risks she would have added six months ago no longer get added. A program manager closes a quarterly review with “whatever you decide works for us.” She means it; she no longer has a preference.

Each of these people is reading the system correctly. It has stopped responding to signal, and they have stopped sending it.

This has a name. It is Trust Exhaustion.

Here’s the pattern. Repeated misalignment and unresolved structural failures deplete trust faster than it can be rebuilt. People keep complying while belief collapses, engagement becomes mechanical, and discretionary effort disappears. The system reads the calm as alignment maturing. What it is reading is the absence of further attempts.

Compliance masquerades as alignment. The team that no longer pushes back is described as mature. The all-hands with fewer questions is called focused. The risk register that stops growing is called stabilized. The engagement survey that holds steady is treated as proof the culture work is paying off. The signal the system reads is alignment. The condition underneath is people who have stopped expecting the system to respond to truth.

What Trust Exhaustion gets mistaken for is the thing that makes it durable.

The misdiagnoses are familiar. Burnout. Generational disengagement. Change resistance. An engagement problem. Each one personalizes a structural outcome. Each one prescribes an intervention the structure already knows how to absorb. Wellness programs land on people who have already disengaged. Recognition rewards the compliance the system is mistaking for commitment. Values refreshes ask the silent to speak more clearly. None of these touch the structural failure that produced the distrust.

Compliance is how Trust Exhaustion survives contact with the engagement survey.

The pattern recurs and changes costumes. In one organization it shows up as a leadership team celebrating the absence of attrition in a quarter where the two people most likely to leave already have. In another, as an engagement survey with the same neutral midpoint year after year and a comments field that returns nothing actionable. In a third, as a culture of psychological safety where the surface stays calm and the structural failures that produced the silence are never named.

The conditions are structural, not behavioral. This is why a new manager does not restore it. A new CEO does not restore it. A team offsite does not restore it. Each of these resets the relationship at the surface and leaves the structural breach intact.

What interrupts it is structural. A visible reversal of a known bad decision, named as such. A leader paying a personal cost for the structural failure that produced the breach. A consequence for the system, not the person who reported it. Where no recent failure has been corrected visibly, the cleanest move is to stop adding new asks until at least one prior failure has been structurally repaired.

When Trust Exhaustion has a name, the options change.

The senior engineer stops reading her own quiet as professionalism and sees it as the cost the system is asking her to pay. The director above her stops adding feedback loops and starts visibly correcting the failures that produced the silence. The executive responsible for the function sees that the steady engagement score is not a culture achievement and that another round of recognition will not produce belief. The board reviewing the year sees that the absence of dissent is not the alignment it has been described as.

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-15, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-15.

A role-specific view of how the same pattern looks from the HR seat is at dripractice.com/lens/hr.

A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.

Next in The Lexicon: FM-05, Normalized Workarounds. It is what people do once they have stopped trusting the system to respond. They do not push harder. They route around. The workaround becomes the work.

Subscribe to The Lexicon.

A chief product officer brings a pricing change to the leadership team. The data supports it. The customer signal supports it. The competitive window is closing. The meeting ends with a request for one more round of input from Legal, Finance, and the regional leads. A VP of engineering has approval to deprecate an internal platform. The timeline is set. Three weeks later, the migration has not started because two adjacent teams want to align on sequencing. A director of strategy presents a market-entry recommendation. The executive sponsor agrees with the analysis. The recommendation is tabled until the next offsite so the broader leadership team can weigh in. A general manager greenlights a headcount reallocation. HR, Finance, and the COO’s office each ask for a briefing before the req is posted. The req is never posted.

None of these people lack authority. Each one holds the title, the mandate, and the budget. What they lack is permission to use it without asking.

This has a name. It is Decision Latency.

The pattern is this. Decisions technically have owners, but action is delayed by expanding alignment requirements. Input is continuously gathered, socialized, validated, and revalidated. Authority exists on paper, but permission is socially negotiated. The system does not block decisions. It absorbs them.

Alignment masquerades as governance. The meeting that ends with “let’s get everyone on the same page” is praised as inclusive. The leader who pauses to build consensus is described as thoughtful. The process that routes a decision through four review layers is called mature. The signal the organization reads is care. The condition underneath is a system that has made deciding more expensive than waiting.

What Decision Latency gets mistaken for is the thing that makes it durable.

The misdiagnoses are generous. Strategic depth. Thoughtfulness. Inclusivity. Strong governance. Each one treats the delay as a feature. Each one rewards the behavior that is slowing the system down. Leadership coaching teaches patience the structure is exploiting. Process improvement adds gates to a pipeline already full of gates. Governance frameworks formalize the very alignment loops that replaced the decision.

None of these substitute for authority exercised. An organization cannot move faster by adding more people to the conversation. A leader cannot decide what the culture has made expensive to decide. A process cannot substitute for a person willing to be wrong.

Consensus is how Decision Latency survives contact with the board.

The pattern recurs and changes costumes. In one organization it shows up as a RACI matrix where every stakeholder is consulted and none are accountable. In another, as a culture of psychological safety where disagreement is welcomed and resolution is not. In a third, as agile governance where decisions are distributed to committees that meet biweekly and decide monthly.

The conditions are structural, not behavioral. This is why faster meetings do not interrupt it. Better decks do not interrupt it. More data does not interrupt it. Each of these speeds up a process whose purpose has become avoiding the decision, not making it.

What interrupts it is structural. Clear deadlines with consequences for missing them. Named deciders with reversal authority. Separation of input from approval. Cultural permission to decide with incomplete information. Where the decision rights cannot be clarified, the cleanest move is to escalate once, visibly, rather than let the alignment loop run until the window closes.

When Decision Latency has a name, the options change.

The product leader stops treating the fourth alignment meeting as due diligence and sees it as the system avoiding a commitment. The VP above her stops adding reviewers and starts naming deciders. The executive responsible for the function sees that the missed window was not a planning failure and that another governance layer will not restore speed. The board reviewing the quarter sees that no amount of strategic patience will produce results until someone is permitted to act.

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-08, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-08.

A role-specific view of how the same pattern looks from the product leader’s seat is at dripractice.com/lens/product.

A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.

Next in The Lexicon: FM-15, Trust Exhaustion. It is what happens after enough decisions stall. The people who used to push for resolution stop pushing. They have learned that the system does not reward it.

Subscribe to The Lexicon.

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.

A CEO sits in the daily engineering standup because architecture decisions keep getting reversed two levels down. A COO clears the small-vendor purchase order list each morning because procurement will not sign anything off without her review. A general counsel reviews routine vendor NDAs that her three direct reports are afraid to commit to without her name on them. A division president takes the call from a frustrated customer because the regional GM does not have the authority to offer the resolution the customer is asking for.

None of these leaders are mismanaging their time. Each one is absorbing a structural load the system has routed upward, faster than it has equipped lower layers to absorb it.

This has a name. It is Leadership Saturation.

The pattern is this. Volume, ambiguity, and risk travel upward faster than authority travels downward. Senior leaders become the default resolution mechanism for problems whose ownership was never installed elsewhere. Decision quality degrades as the queue grows past what any one person can think clearly about. Availability becomes sporadic. Strategic work gets displaced by operational triage. The leader’s calendar fills with arbitration.

Saturation masquerades as accessibility. The executive who responds at midnight is praised for hands-on leadership. The leader who attends every operational meeting is described as engaged. The CEO who personally clears the small-vendor list is celebrated for not losing touch with the work. The signal the system reads is gratitude. The condition underneath is structural overload.

What Leadership Saturation gets mistaken for is the thing that makes it durable.

The misdiagnoses all rhyme. Strong leadership. High engagement. Flat hierarchy. Hands-on management. Each is a hero narrative. Each is how the system rewards the behavior that is killing it. Leaders who refuse the next escalation get scored as disengaged. The org is praised for being unbureaucratic while every nontrivial decision routes through the same six people. Retention conversations focus on coaching the executive instead of redesigning the queue.

None of these are substitutes for distributed authority. A leader cannot decide faster than the work is generated. A leader cannot strategize while arbitrating. A leader cannot delegate what the organization has not equipped lower layers to receive.

The misdiagnoses are not incidental. They are the mechanism. Hero narratives are how Leadership Saturation survives contact with the board.

The pattern recurs and changes costumes. In one organization it shows up as an executive team running on adrenaline because the layer below has no real decision rights. In another, as a chief of staff function that quietly expanded because routine work needs an arbitrator and there is no one else equipped to be one. In a third, as an open-door culture that has calcified into the only door.

The conditions that produce saturation are structural, not individual. This is why coaching the executive does not interrupt it. Better calendars raise the throughput on the existing queue. Stronger assistants compress more decisions into the same available hours. A new chief of staff is a new amplifier on the same input.

What interrupts it is structural. Hard limits on what the executive layer is allowed to decide. Decision rights pushed down with the authority to actually use them. Error tolerance baked into lower layers, so leaders are not the only safe place for ambiguity to land. Explicit redistribution, repeatedly enforced. If leaders are always available, the system will never mature.

When Leadership Saturation has a name, the options change.

The leader inside it stops mistaking responsiveness for effectiveness. The team below stops reading every escalation as a personal failure. The board stops treating burnout at the top as a personnel issue. The organization stops applauding the behavior that is collapsing it.

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-10, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-10.

Next in The Lexicon: FM-03, Responsibility Without Authority. It is the upstream condition that produces saturation in the first place. Accountability assigned where decision rights are not.

Subscribe to The Lexicon.

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.