The Misdiagnosis File

It gets called: a lack of leadership (also travels as: nobody steps up; no ownership)

The framework calls it: FM-1, Authority Vacuum

No role holds final decision authority for a defined scope. Decisions stall, escalation loops, and waiting for direction becomes the standing condition. Then individuals get blamed for not stepping up into authority that no position actually carries.

You cannot lead from a chair that has no authority bolted to it. That is not a character flaw. It is architecture.

The discriminating question: Can you name the position, not the person, that holds final decision authority for this scope?

Published in Goe 2026a (failure-mode taxonomy) and defined in the glossary.

It gets called: micromanagement (also travels as: control freak boss; can't let go)

The framework calls it: FM-2, Authority Inversion

Decisions escalate to the wrong layer because the structure routes them there. Senior people drown in calls the front line should own; front-line calls wait days for a signature. Everyone blames the executive's personality. Swap the executive and watch the new one drown in the same inbox.

If every occupant of the chair develops the same disease, check the chair.

The discriminating question: Would a different occupant of the same chair end up with the same inbox?

Published in Goe 2026a (failure-mode taxonomy) and defined in the glossary.

It gets called: a communication problem (also travels as: silos; people don't talk to each other)

The framework calls it: FM-6, Information Latency Failure

The decision-relevant signal arrives after the decision window closes, or arrives and is suppressed. The information usually existed inside the organization the whole time; the pathway failed it.

Training people to speak up does not fix a structure that routes the signal around the position holding the call. The framework treats information pathways as command architecture, not as a soft skill.

The discriminating question: Did the signal exist inside the organization in time to matter, and did a pathway carry it to the position that held the decision?

Published in Goe 2026a (failure-mode taxonomy) and defined in the glossary. Documented case: The Challenger launch decision.

It gets called: that's just how things work around here (also travels as: the unwritten rules; the real org chart)

The framework calls it: FM-8, Structural Drift

The documented command architecture and the actual decision paths have quietly diverged. New hires get two orientations, the official one and the real one. Workarounds became the standard. The org chart is a historical document.

Drift is not a discipline failure. Every organization drifts. The failure is having no mechanism that detects it.

The discriminating question: When did anyone last compare the documented chart against the way decisions actually route, and whose job is it to notice the gap?

Published in Goe 2026a (failure-mode taxonomy) and defined in the glossary.

It gets called: bad leaders (also travels as: a toxic culture; a people problem)

The framework calls it: FM-10, Premature Behavioral Attribution

Structurally rooted failure gets attributed to personality, style, or culture before anyone verifies the structure. It is the most common analytical failure in the catalog, because it feels like an explanation and it ends the inquiry.

The framework's rule is an ordering rule: verify the structure first. Conduct analysis is valid only after the structural conditions are confirmed. Behavioral fixes applied to structural failures don't just miss; they hide the failure for another cycle.

The discriminating question: Was the structure verified before the people were blamed?

Published in Goe 2026a (failure-mode taxonomy) and defined in the glossary. Documented case: Wells Fargo cross-selling.