
The best model for how far a plane can fly treats it as a dot.
“Make the model as simple as possible” is common advice, and usually right. But simple in which direction? You can model an airplane three ways. If you want to estimate range, treat it as a point mass with drag. If you want to know whether the wings will tear off, model the aeroelastic structure. If you want to paint it, model the surface area and livery. Each throws away different things, and none is “the” model of the airplane. Each is a model for a purpose.
So the advice hides a prior question. Venkatesh Rao’s compressed test is:
how you model something depends on what you want to do with the model
Answering it splits models into two kinds that are judged by opposite standards. Simplicity is a virtue only after purpose has been named.
Two kinds of model
Manipulative models are for doing something specific: estimate, steer, optimize, troubleshoot, repair. Their quality is measured by whether they help with the intended action, so extra realism is usually a bug, because it adds degrees of freedom that do not improve the move. The point-mass airplane is a good manipulative model precisely because it ignores the wings, the rivets and the paint.
Appreciative models are for making sense of something on its own terms, before the action is clear. The people trying to understand flight before anyone knew which variables mattered could not know what to throw away. An appreciative model is measured by whether it creates a fertile image of the world: a frame that lets you notice more, ask better questions, and later derive more precise manipulative models.
That is where the simplicity advice fails. Once the purpose is fixed, every irrelevant detail is drag. Before it is fixed, the work is not yet intervention but perception, and premature simplification becomes premature deletion. You remove precisely the strange, ugly, inconvenient details that might have revealed what the situation is. Exploration feels inefficient for the same reason: it makes the mental model messier before it earns the right to simplify. The person who demands elegance too early is often demanding emotional relief, not understanding.
Moving between them
The two kinds are stages more than rivals. A rich model of an airplane becomes a range calculator once you discard everything except the variables relevant to range. The reverse is harder: someone has to extract the insight from a working trick and generalize it. Pythagorean triples were useful in practical geometry long before the Pythagorean theorem made the pattern appreciable, and the theorem, though less immediately worldly, proved far more generative.
The limit: seductive models
Appreciative models have their own failure: aesthetic capture. A model can be elegant and beautiful while going nowhere. A good appreciative model is fertile. It suggests lines of attack, exposes new distinctions and makes adjacent questions visible, whether or not it is pretty. A bad one is seductive. It feels profound because it compresses the awkwardness away, so it is easy to remember, easy to repeat, and sterile in use. That is the danger in treating beauty as a truth-signal: coherence can be manufactured by deletion. Elegance is a bonus when it happens; fertility is the real test.
So before criticizing a model, ask what it is for. If it is manipulative, ask whether it helps with the move it claims to support. If it is appreciative, ask whether it makes the world more fertile to think with. The harder judgment is when to switch, because appreciation without manipulation becomes private aestheticism, and manipulation without appreciation becomes optimization inside a shrunken world. The point-mass airplane is a fine tool for someone who already understands flight. Whether you understand your own situation well enough to start treating it as a dot is the question the simplicity advice never asks.
References:
- Venkatesh Rao, Appreciative versus Manipulative Mental Models, Ribbonfarm
- John Friedmann, Planning in the Public Domain