A director of operations knows a two-page approval used to take a morning, but three teams have each bolted on a required sign-off since, so a routine request now takes nine days, because every step closed a real gap and no one owns the total. A compliance officer wants the control to catch risk, but the checklist has grown to forty items nobody reads in full, so it gets clicked through on faith. A senior engineer can ship the fix in an afternoon, but the change-management workflow demands four gates designed for a release ten times the size, so the afternoon becomes a week. A team lead sees her people using a side channel to get real work done, but the official process is the one that gets audited, so she maintains both, because the paperwork proves the work happened even when the work is elsewhere.

None of these people are failing. Each one is feeding a process that has outgrown the problem it was built to solve.

This has a name. It is Process Inflation.

Here’s the pattern. When the shared story that once told people why the work mattered goes quiet, process rushes in to hold things together, and procedure begins standing in for the meaning it replaced. From there it compounds. Each addition solves a local problem; no one owns the cumulative burden; risk aversion favors adding a step over removing one. Complexity accumulates beyond the original purpose. What began as lightweight coordination hardens into heavyweight procedure, until the workflow becomes the work. And because more steps look like more care, the organization reads its own thickening as a sign of maturity.

Procedure masquerades as rigor. The team that adds a gate is called careful. The manager who lengthens the approval chain is called thorough. The function with a documented control for everything is called mature; the one that questions a step has to justify removing it. The signal the system reads is diligence. The condition underneath is an organization spending more and more effort to deliver the same thing, and mistaking the effort for the outcome.

What Process Inflation gets mistaken for is what keeps it alive. We need process to scale. This is just how large organizations work. We need better documentation. People are not following the process. Each reading treats the inflation as either healthy growth or a compliance gap, so the repair is always to add, formalize, or enforce. More process is prescribed for a process problem; the coordination cost is accepted as the price of size; the workarounds are read as indiscipline rather than as evidence the process no longer serves. These readings are how Process Inflation survives contact with the process audit, the one review meant to catch it and the one most easily spent certifying that the steps are being followed rather than asking whether the steps should exist.

The pattern recurs and changes costumes. In one company it is an onboarding checklist that gains a line every time something goes wrong until no one can start work in the first month. In another, a hospital where each incident adds a form until the charting consumes the hour that used to go to the patient. In a third, an agency so wrapped in its own procedure that a routine decision now needs its own procedure to move through the procedure.

Training people on the process does not interrupt it; a well-run heavy process is still heavy. Hiring a process owner for each step does not interrupt it; it gives every step a defender and no one a mandate to subtract. Replacing the manager who let it grow does not interrupt it; the replacement inherits the same asymmetry, where adding a step is safe and removing one carries all the risk.

What interrupts it is structural. Put sunset clauses on new processes, so every step has to earn its renewal instead of living forever by default. Make the total cost of coordination visible in one place, so the burden now spread across everyone lands on a single desk. Give someone the authority to remove a step without assembling the consensus that adding it never required. Where the accumulation has already buried the work, the fail-safe is a periodic process audit with a deletion mandate, a standing review whose job is not to certify adherence but to cut.

When Process Inflation has a name, the options change.

The engineer who has been maintaining two workflows stops calling it diligence and sees a process that no longer touches the work. The manager above stops praising the thoroughness and asks what it now costs to deliver the same result. The executive stops reading a fully documented control set as safety and asks how much velocity and judgment the controls have quietly spent. The board stops accepting “we have mature processes” and asks whether the processes still serve the outcome or have become the outcome.

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

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

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

Next in The Lexicon: FM-06, Exception Inflation. Every heavy process breeds its own escape hatches, and the exceptions meant to relieve it slowly become the real operating system. FM-06 is what happens when “just this once” becomes how the work actually runs.

Subscribe to The Lexicon.

A division head can recite this year’s strategy, but when a new hire asks why the company chose this path over the alternative, the answer is a slide instead of a reason, because the logic that produced the plan was never written down and the people who held it have moved on. A team lead sees two directives that contradict each other but raises neither, because no shared story is left to say which one wins, so both get worked in parallel until one quietly starves. A finance manager approves a spend the same way it was approved last year, but no one in the room can name the goal it now serves, because the decision runs on precedent and the intent behind it has gone missing. A senior engineer nods through the alignment meeting, agreeing with everything, but walks out unable to tell her own team what changed or why, because the meeting produced consensus without conviction.

None of these people are failing. Each one is executing inside a story that no longer explains itself.

This has a name. It is Narrative Collapse.

Here’s the pattern. The system loses a shared explanatory story for why decisions are made and how actions connect to outcomes. The narrative was treated as an artifact, a deck to be refreshed, rather than infrastructure to be maintained, so as decisions piled up, the causal logic linking intent, tradeoffs, and outcomes stopped being kept current. Work continues, but meaning fragments. People still know what to do; they can no longer say why. Alignment becomes performative, agreement in the room and confusion outside it, and execution persists without conviction. When this shows up, it looks like people not getting the message, so the reflex is to send the message again, louder.

Re-alignment masquerades as diligence. The team that meets weekly to re-sync on priorities is called communicative. The executive who re-launches the strategy with a fresh framework is called a strong communicator. The organization that agrees quickly in every review is called aligned. The signal the system reads is engagement. The condition underneath is a shared story that has come apart, papered over by the motion of restating it.

What Narrative Collapse gets mistaken for is what keeps it alive. This is a communication problem. People just need more clarity. It is change fatigue. The strategy is fine, execution is lagging. We need to re-launch the narrative. Each reading treats the loss of meaning as a messaging gap, so the repair is always more messaging, and more messaging adds noise to a system that already cannot tell signal from restatement. These misreadings are how Narrative Collapse survives contact with the all-hands, the one recurring event meant to restore the shared story and the one most easily spent restating the slide and mistaking agreement for belief.

The pattern recurs and changes costumes. In one company it is a strategy that exists in five versions, one per audience, none of which reconciles with the others. In another, a hospital where every unit executes its protocol and no one can explain how the protocols add up to care. In a third, an agency running so many transformation programs at once that the reason for any single one has dissolved into the noise of all of them.

The conditions are structural, not behavioral. A communications training does not interrupt it; a clearer deck does not restore a logic no one is maintaining. Hiring a stronger storyteller does not interrupt it; a better narrator of a broken story tells a broken story well. Replacing the executive does not interrupt it; the replacement inherits a system that treats the narrative as an artifact and lets the next one decay the same way.

What interrupts it is structural. Re-articulate the original intent, out loud, so the reason the path was chosen is back in the room and not buried in a deck. Name the tradeoffs the strategy actually makes, so people can see what was chosen against. Reduce the strategy to a small set of causal claims that a person can hold without slides. Make the plain-language case for why this and not that, until people can explain the system without the artifact. Where the story has already come apart, the fail-safe is to suspend the change initiatives until narrative coherence is restored, so nothing new is stacked on a foundation no one can explain.

When Narrative Collapse has a name, the options change.

The engineer who agreed without conviction stops calling it alignment and sees a room that produced consensus without meaning. The manager above stops scheduling another re-sync and asks why the story keeps needing to be restated. The executive stops reading fast agreement as alignment and asks whether anyone can explain the strategy without the deck. The board stops accepting a polished narrative as evidence of a shared one and asks whether the people executing it can say why.

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

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

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

Next in The Lexicon: FM-16, Process Inflation. When the shared story is gone, process rushes in to hold things together, and procedure starts standing in for the meaning it replaced. FM-16 is what happens when the workflow becomes the work.

Subscribe to The Lexicon.

A senior engineer is the only person who understands the pipeline that runs the business, and she wants it documented before she leaves, but every sprint is full of shipping, so the knowledge walks out with her, because the system was built to extract her output and never to transfer what she knew. A new analyst wants to understand why the model works the way it does, but the runbook only tells him which buttons to press, so he follows the steps without grasping them. A team lead’s group runs the standard case flawlessly but freezes on anything novel, and because novel cases are rare, the gap never shows on a dashboard. A department head wants to keep the hard, judgment-heavy work in house, but a vendor will do it cheaper this year, so the competence gets outsourced, because the saving lands on this year’s budget and the loss on no one’s.

None of these people are failing. Each one is watching a capability leave the building faster than anyone is rebuilding it.

This has a name. It is Capability Atrophy.

Here’s the pattern. An organization that spends every quarter and invests in no year stops exercising the capabilities the future depends on, and the muscles it never uses quietly waste. The structure stays intact, so nothing looks lost. But the capability inside drains: skills decay, judgment weakens, and work becomes procedural rather than adaptive. The system still functions, now only within a shrinking range of conditions, fine on the cases it has seen and brittle on the ones it has not. Efficiency pressure rewards repeatability over mastery, so as experienced people leave, process is layered in to compensate, and over time process replaces understanding instead of supporting it. The loss never announces itself. It gets read as the system finally running smoothly.

Codifying masquerades as maturity. The team that turns every judgment call into a checklist is called disciplined. The function that swaps experienced people for documented procedure is called scalable. The manager who removes the dependency on one expert is praised for reducing risk. The signal the system reads is maturity. The condition underneath is a slow hollowing-out, an organization that still delivers but no longer learns.

What Capability Atrophy gets mistaken for is what keeps it alive. Operational excellence. Scalability. Professionalization. Risk reduction. Each reading treats the loss as a sign of a system growing up, so the repair is to codify more: another runbook, another control, another judgment standardized away. None of it rebuilds the skill that is draining, so the drain continues under cover of looking mature. These readings are how Capability Atrophy survives contact with the post-incident review, the one moment built to ask why a function broke, most easily spent adding a checklist instead of restoring what the checklist replaced.

The pattern recurs and changes costumes. In one company it is a manufacturer that offshores the engineering it once did in house until no one left can judge whether the vendor’s work is any good. In another, a bank so dependent on documented procedure that a single retirement takes a capability no one can reconstruct. In a third, an agency that has standardized its casework so thoroughly that a case outside the template stalls, because no one still holds the judgment the template was built from.

The conditions are structural, not behavioral. More training hours do not interrupt it; hours spent memorizing the procedure deepen the dependency on it. Hiring stronger talent does not interrupt it; strong people poured into a structure built to extract output and skip transfer atrophy at the same rate as everyone else. Replacing the person who left does not interrupt it; the replacement inherits a runbook and none of the tacit knowledge the runbook was written to stand in for.

What interrupts it is structural. Run apprenticeship models, so tacit knowledge transfers person to person before it walks out the door. Protect time for skill development that shipping is not allowed to raid. Remove abstractions between decision and consequence, so the people deciding still feel what their judgment costs and stay sharp on it. Treat tacit knowledge as a first-class asset, tracked and maintained like any other piece of infrastructure. Where core competence has already been handed out to keep a function cheap, the fail-safe is to stop outsourcing core competence and pull the capability back inside.

When Capability Atrophy has a name, the options change.

The analyst pressing buttons he does not understand stops calling it onboarding and sees a role built to run a process, not to learn a craft. The manager above stops praising the clean runbook and asks what the team can no longer do without it. The executive stops reading stable output as a healthy function and asks what the function can no longer handle. The board stops accepting “we have professionalized” and asks what capability that professionalization quietly spent.

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

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-14, Narrative Collapse. When the work goes procedural and the skill drains out of it, the story a company tells about why any of it matters starts to thin. FM-14 is what happens when execution continues and the meaning behind it quietly goes.

Subscribe to The Lexicon.

A CEO knows the company needs to place a two-year bet, but each quarter arrives with a number to defend, so the bet slides to the next planning cycle, and the one after, because the calendar only rewards what closes before it ends. A head of R&D can see the platform will be obsolete in three years, but this year’s roadmap is already full, so the rebuild never gets staffed, because work that pays off after the current tenure has no one whose bonus depends on it. A VP is celebrated for pulling three at-risk launches over the line, but why all three were at risk is never examined, because firefighting is visible and the prevention that would have made it unnecessary is not. A product leader wants to hold capacity for the market the company will need next, but the market it has is on fire, so the capacity gets spent this quarter, because urgency always outbids importance in a room with a clock on the wall.

None of these leaders are failing. Each one is trading a future they can see for a present they are measured on.

This has a name. It is Strategic Myopia.

Here’s the pattern. Under sustained pressure, an organization optimizes for what it can measure this quarter and slowly loses the ability to see past it. Strategy stops being a set of bets about the future and becomes a sequence of reactions to the present. Second- and third-order effects fall out of view. Nobody decides they no longer matter; nothing on the calendar rewards seeing them. The dashboard that was meant to track the strategy quietly becomes the strategy, and the company optimizes for what the number can see and loses the rest. It calls the narrowing focus.

Narrowing masquerades as focus. The executive who kills the long-horizon project to concentrate on the quarter is called disciplined. The team that drops the two-year roadmap to chase the current fire is called responsive. The leader who says there is no time for strategy is called a realist. The signal the system reads is focus. The condition underneath is an organization narrowing its own field of view until only the quarter is left.

What Strategic Myopia gets mistaken for is what keeps it alive. The market changed. We need to be more agile. This is just execution debt. We will fix it next quarter. Strategy is a luxury right now. Each reading treats the narrowing as a temporary response to conditions, so the repair is always to execute harder and decide later. None of them widen the horizon, so the horizon keeps closing. Hero narratives are how Strategic Myopia survives contact with the strategy offsite, the one event on the calendar meant to widen the horizon and the one most easily spent reaffirming the quarter.

The pattern recurs and changes costumes. In one company it is a research budget trimmed every year to protect the quarter until there is nothing left to commercialize. In another, a hospital so tuned to this month’s throughput that the capability it will need next decade is never built. In a third, an agency that runs on emergencies so completely that the reforms meant to end the emergencies never get scheduled.

The conditions are structural, not behavioral. A visionary offsite does not interrupt it; the horizon widens for two days and closes the following Monday. A new mission statement does not interrupt it; a slogan does not change which work gets staffed. Replacing the executive does not interrupt it; the replacement inherits the same incentives and shortens the same horizon within a quarter.

What interrupts it is structural. Run short-term and long-term decisions in separate lanes, so the future is not forced to bid against this week’s fire for the same attention. Make a named leadership role accountable for future-state health, so someone in the room loses when the horizon closes. Protect strategic work with time that urgency is not allowed to raid. Accept deliberate short-term pain where it buys long-term position, and treat the willingness to absorb it as a sign of health. Where the horizon has already collapsed to the quarter, the fail-safe is to freeze the optimization and widen the time horizon before deciding anything else.

When Strategic Myopia has a name, the options change.

The VP who has been rewarded for firefighting stops calling it performance and sees a role built to spend the future. The manager above stops praising the saves and asks why the same fires keep starting. The executive stops reading strong execution as a healthy strategy and asks what the company can no longer see. The board stops accepting “we are staying focused” and asks what focus has cost the horizon.

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

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

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

Next in The Lexicon: FM-13, Capability Atrophy. An organization that spends every quarter and invests in no year stops exercising the capabilities the future depends on. FM-13 is what happens when those muscles quietly waste.

Subscribe to The Lexicon.

A VP of sales knows a deal is real, but it does not fit the stages the forecast tool recognizes, so it gets logged unqualified and dropped, because the pipeline number now sets priorities the VP used to set. A hiring manager wants to make an offer, but the scorecard lands two tenths under the bar, so it dies in committee, because the rubric became the verdict instead of an input. A support director’s team is resolving harder cases on purpose, but the handle-time dashboard is red, so headcount gets pulled from the work that needed it, because the metric outranks the context it cannot see. A product manager sees a feature is right for the next two years, but it costs a point on this quarter’s chart, so it gets cut, because the chart carries more weight than the people who built the roadmap.

None of these people are failing. Each one is deferring to a number that was never supposed to hold the final say.

This has a name. It is Metric Authority Drift.

Here’s the pattern. A metric arrives to inform a decision, one input among several. Over time it is easier to point at the number than to defend a judgment, so the number starts carrying the decision alone. People stop asking whether it is meaningful and start asking whether it is green. The measure that stood in for the goal becomes the goal. Authority drifts onto the metric, and no one ever decided to hand it over. Leadership reads following the data as rigor, which is the reverse of what happened. Judgment was not informed. It was replaced.

Deference masquerades as rigor. The manager who cites the dashboard for every call is called data-driven. The team that hits its number is called high-performing long after the number stopped meaning what it did. The leader who follows the metric is never asked to justify it; the one who overrides it has to defend the exception. The signal the system reads is rigor. The condition underneath is a decision quietly handed to a number.

What Metric Authority Drift gets mistaken for is what keeps it alive.

Data-driven leadership. Accountability. Operational maturity. Professionalization. Each is a hero narrative, and each is how the system rewards the behavior that blinds it. Praising the data-driven manager removes the reason to ask what the data cannot see. Treating the override as the thing that needs defending teaches everyone to stop overriding. In reality, it is abdicated judgment.

Hero narratives are how Metric Authority Drift survives contact with the quarterly business review.

The pattern recurs and changes costumes. In one organization it is a sales team walking away from real revenue because the deal does not fit the stages the tool recognizes. In another, a hospital guarding its throughput metric while the care it was built to protect erodes. In a third, a “we go where the data tells us” mantra so complete that the decision the data cannot see never gets made.

The conditions are structural, not behavioral. Better dashboards do not interrupt it, because a cleaner number is easier to defer to. More data-literacy training does not interrupt it; it teaches people to trust the number more, not less. Tighter targets and better KPIs do not interrupt it; they deepen the metric’s authority instead of bounding it.

What interrupts it is structural. Declare zones where judgment openly overrides the metric, so there are decisions the number does not get to make. Have leaders model metric refusal in the edge cases, so overriding is something the room watches, not something it punishes. Keep metrics as inputs, not verdicts, each tied to a named owner who holds the call. Run retrospectives on decision quality, not just outcomes, so a sound call that missed the number still counts as sound. Where a number has fully captured a decision, the fail-safe is to invalidate it as the decision authority and force the judgment back into the room.

When Metric Authority Drift has a name, the options change.

The product manager who cut the right feature stops calling it discipline and sees a decision the dashboard made for him. The manager above stops reading “follows the data” as rigor and asks which calls the data is quietly making. The executive sees that a data-driven review and a well-judged operation are not the same reading, and that one has stood in for the other. The board sees that a green dashboard is not evidence the right decisions are being made; it can be evidence they have been handed to the dashboard.

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

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

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

Next in The Lexicon: FM-12, Strategic Myopia. Once the number holds the authority to decide, the organization optimizes for what the number can see and slowly loses the rest. FM-12 is what happens to strategic vision when the dashboard becomes the map.

Subscribe to The Lexicon.

A site reliability engineer knows a dependency is fragile and will fail under peak load, but the last person who raised a “theoretical” risk spent two sprints defending it in reviews, so he files it as a backlog ticket nobody prioritizes. A compliance analyst sees a gap that belongs in front of the steering committee, but surfacing it means owning a remediation she has no budget for, so she notes it in a memo and moves on. A regional manager has flagged the same staffing shortfall three quarters running, and each time it came back as a question about her forecasting, so this quarter she stops flagging and absorbs the overtime herself. A product lead can see a launch date slip becoming inevitable six weeks out, but the meeting where that gets said rewards confidence, so the slip surfaces at week one instead, when it is a crisis rather than a heads-up.

None of these people are failing. Each one has correctly priced what escalation costs and decided to carry the problem instead.

This has a name. It is Escalation Inversion.

Here’s the pattern. The escalation path exists on paper, but using it is slow, costly, or reputationally risky, so problems get absorbed at the edge until they either resolve quietly or detonate in public. Escalation volumes stay low. The formal process is documented and clear, while the informal rule everyone has learned is that raising a problem makes you the problem. Leadership reads the low volume as things being under control, which is the exact opposite of what the low volume means.

Silence masquerades as stability. The team with the fewest escalations is called high-performing. The manager who never brings problems up is called low-maintenance. The quarter with no red flags is called clean. The engineer who handles it without noise is the one who gets promoted. The signal the system reads is stability. The condition underneath is a team that has learned raising the problem costs more than carrying it.

What Escalation Inversion gets mistaken for is what makes it durable.

Empowered teams. Strong local ownership. A mature, low-noise culture. Only edge cases escalate. Each is a hero narrative, and each is how the system rewards the behavior that is blinding it. Praising the quiet team removes any reason to ask what it is absorbing. Treating escalation as noise teaches people that signal is unwelcome. Reading a clean dashboard as a healthy operation confuses the absence of reports with the absence of problems.

Hero narratives are how Escalation Inversion survives contact with the risk review.

The pattern recurs and changes costumes. In one organization it shows up as an incident postmortem asking why nobody raised the risk, when three people had raised it informally and watched it go nowhere. In another, as a quarterly risk register that stays green right up to the failure. In a third, as a “no surprises” culture so loud that a surprise becomes the only thing that ever gets through.

The conditions are structural, not behavioral. This is why telling people to escalate more does not interrupt it; it raises the ask without lowering the cost. Adding an escalation channel does not interrupt it; it adds a path without adding a reason to walk it. Replacing the manager resets the relationship and leaves the incentive intact.

What interrupts it is structural. Strip the cost, so raising a problem is reputationally and metrically neutral. Reward the early signal, so the person who flags the risk before the failure is the one who is valued, not the one who absorbed it. Measure what did not escalate, the distance between what the edge knew and what reached the top. Where the incentive cannot be changed quickly, the cleanest move is for a named owner to go ask for the problems directly, and to make the asking safe.

When Escalation Inversion has a name, the options change.

The engineer who has been filing fragile-dependency risks as backlog tickets stops reading his own quiet as good judgment and sees it as a cost the system is charging him to stay safe. The manager above him stops counting low escalation volume as a healthy team and starts asking what the team has decided not to send up. The executive sees that the clean risk review and a low-risk operation are not the same reading, and that one has been standing in for the other. The board sees that the absence of escalations is not evidence the system is sound; it can be evidence the system has gone quiet.

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

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

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

Next in The Lexicon: FM-11, Metric Authority Drift. When the edge goes quiet, leadership leans harder on the dashboard. FM-11 is what happens when the dashboard stops informing the decision and starts being it.

Subscribe to The Lexicon.

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.