Mental Model Building

Mental model building

The difference between following instructions and understanding is prediction. Someone with a model can reason about a situation they have never seen; someone with procedures is stuck the moment reality differs.

Method

1. Ask what happens and why at each step. Procedures without mechanism produce brittle knowledge that fails on the first variation.
2. Predict before you observe. Say what you expect, then check, because a wrong prediction locates the gap in your model precisely.
3. Trace one path end to end. Following a single request or a single value through the whole system builds more understanding than studying components separately (see distributed-tracing).
4. Find the boundaries. What the system does not do, and where its abstractions leak, which is where models are usually wrong (see platform-abstractions).
5. Test the model by explaining it. Explaining to someone else reveals which parts you cannot actually account for (see teaching-technical-concepts).
6. Update deliberately on surprise. A surprising behaviour is evidence your model is wrong, which is the most valuable moment for revision (see learning-from-failure).
7. Read the implementation when the model runs out. The source is authoritative where documentation is aspirational.

Boundaries

Models are simplifications and wrong at their edges by construction. Building one takes longer than memorising a procedure and pays back on the first novel problem. Some systems are genuinely too complex for a complete model, which makes knowing your model's limits part of it.