The Four Zooms
Context, containers, components, code. The discipline is that each level is a complete picture at its own resolution — and most architecture diagrams fail because they mix levels, which is exactly the same failure as mixing altitudes in a conversation.
Someone shows you an architecture diagram. It has users, three systems, a queue, two database tables,
a class called OrderValidator, and an arrow labelled "REST". Everyone nods and nobody
understands it. What is actually wrong with it?
The conversation that goes nowhere
One person is discussing strategy and another is discussing a database column, and both think the other is being unhelpful. It is the same failure as the diagram — and naming the level out loud usually ends it in one sentence.
The unreadable strategy
A strategy paper with an implementation detail in paragraph three loses every reader who needed the strategy. Each level must be complete at its own resolution and say nothing about the ones below it.
Starting at level 3
New joiners are shown the component diagram on day one and are lost for a month, because nobody drew levels 1 and 2. You cannot zoom in from nowhere.
Precision at the wrong altitude
Arguing about a class name inside a buy-or-build decision is level-4 detail in a level-1 question. It feels rigorous and it is noise — and it is how the real decision ends up being made by default.
Before you draw, say which level you are drawing, then refuse to put anything from another level on the page. A diagram that answers one question completely beats one that gestures at four — and the same rule governs documents, meetings and estimates. When a conversation stops making sense, it is usually because two people are at different altitudes and neither has said which.