The Mind Map

The diagram that follows — the one-page map of all nine frameworks — is the signature artefact of this book and the series. It shows:

F1 and F9 at the perimeter, because they are the input lenses and the empirical constraints
F2 and F3 as paired guardrails: what should be true and what goes wrong when it is not
F4 at the centre, because every decision passes through the tradeoff vocabulary
F5 as the process layer between analysis and decision
F6 as the classification that determines which other frameworks to weight heavily
F7 and F8 as the output and vocabulary layers

Print it. Put it somewhere you see it. The value of the map is not reading it — it is having it so close to hand that you stop needing to consult it.

Concept: The Nine Frameworks as a System

Thread: T12 ← Optimisation under constraints (Book 1) → Unified decision vocabulary (Book 6, Ch 1)

Core Idea: Nine frameworks — mental models, principles, failure modes, tradeoffs, review questions, archetypes, diagrams, infrastructure components, and engineering laws — form a complete analytical system. Each framework answers one kind of question; together they cover every major concern in system design and engineering leadership.

Tradeoff: Generality vs Specialisation (F4 #6) — the frameworks are intentionally general; applying them to a specific system is where engineering judgment comes in

Failure Mode: Observability Blindness (F3 #11) — using frameworks in isolation without seeing how they connect creates analysis that catches only one class of problem

Signal: Architecture review, incident post-mortem, new system onboarding, job interview, technical strategy decision — any situation where you need to think rigorously about a system

Maps to: Reference Book Ch 5–13 (one chapter per framework); Book 4 Ch 1–2 (frameworks applied to system design); Book 6 Ch 1 (frameworks applied to leadership)

Read in the book →

← Entering from a Problem