Question
Why does levels of abstraction fail?
Quick Answer
Defaulting to a single level of abstraction regardless of purpose. Detail-oriented people habitually operate at the subordinate level, burying their audience in specifics when a high-level summary would serve better. Abstract thinkers habitually stay at the superordinate level, offering frameworks and principles when their audience needs concrete steps.
Both fail in the same way: they let their cognitive comfort zone determine the level of abstraction instead of letting their current purpose determine it. The abstraction level becomes a personality trait rather than a tool selected for the job.
The fix: Choose a domain you work in daily — your job, a creative project, a personal system. Write three descriptions of the same thing at three different levels of abstraction. First, write a one-sentence description so abstract that it could apply to many different domains (the superordinate level). Second, write a one-paragraph description at the level you would use to explain it to a peer (the basic level). Third, write a detailed description that captures specific mechanisms, steps, or components (the subordinate level). Now answer: which description would you use to explain your work to a stranger at a dinner party? Which would you use to onboard a new colleague? Which would you use to debug a specific problem? Notice that each question selected a different level — and that the selection was driven entirely by purpose, not by which description was most "correct."
The underlying principle is straightforward: Too detailed is as unhelpful as too abstract — match the level to your current need.
Learn more in these lessons
- The right level of abstraction depends on your purpose
- Level disambiguation
What is true at one level of abstraction may not be true at another — check which level each claim operates at.
Go beyond the answer
This topic is part of The Staff Engineer’s Thinking Infrastructure — a guided sequence of 20 lessons.
After completing this path you will be able to consciously choose your level of abstraction, build shared mental models across teams through ADRs and RFCs, make architecture decisions that persist beyond your involvement, structure your own time in an undefined role, and manage the invisible emotional load of technical leadership.
Start the path →