The most common failure is framework fragmentation — using one or two frameworks and ignoring the rest. A leader who lives in F3 finds failure modes everywhere but never makes decisions, because decisions require F4. A leader who lives in F4 names tradeoffs fluently but misses the systemic failures that F3 would have surfaced.
FM11 (Observability Blindness) at the organisational level looks like this: the team has rich opinions about the system but no structured way to verify them. F5 exists to address this — the seven review questions are a structured probe that reveals what the team believes versus what the system actually does.
The second failure is using the map as performance rather than reasoning. The vocabulary of F8, without the substance of F1 through F7 behind it, is jargon. A technical leader who names AT5 without analysing what the centralisation actually constrains has borrowed the language without doing the work.
Concept: The Complete Mental Map Thread: T12 (Tradeoffs) ← naming costs implicitly → making costs explicit across all frameworks Core Idea: The nine frameworks form a single reasoning system; using them as isolated tools produces local analysis, not system understanding. Tradeoff: AT6 — structured completeness vs rapid triage speed Failure Mode: FM11 — organisational observability blindness; rich opinions without structured verification Signal: When the same system produces conflicting analyses from different engineers — traverse all nine frameworks in order; the disagreement lives at the framework boundary being skipped Maps to: Reference Book, Frameworks 1–9