How do I practice levels of abstraction?

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."

Common pitfall: 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.

This practice connects to Hierarchy and Nesting — building it as a repeatable habit compounds over time.