Question
Why does abstract vs concrete thinking fail?
Quick Answer
Getting trapped at a single level and mistaking it for the whole picture. Abstract thinkers stay zoomed out and produce strategies that ignore implementation reality. Concrete thinkers stay drilled down and produce solutions that miss systemic patterns. The skill is not choosing the right level —.
The most common reason abstract vs concrete thinking fails: Getting trapped at a single level and mistaking it for the whole picture. Abstract thinkers stay zoomed out and produce strategies that ignore implementation reality. Concrete thinkers stay drilled down and produce solutions that miss systemic patterns. The skill is not choosing the right level — it is moving between levels deliberately.
The fix: Pick a problem you are currently working on. Write it down at three levels of abstraction: (1) the broadest framing — what is the category of problem this belongs to? (2) your current working framing — the level where you have been spending most of your time, (3) the most granular version — what is the specific, concrete instance right now? Read all three. Which level have you been stuck at? Move one level up or down and spend ten minutes thinking from that new vantage point. Notice what becomes visible.
The underlying principle is straightforward: Moving between levels of hierarchy is an active thinking technique.
Learn more in these lessons
- Drill down and zoom out as thinking operations
Moving between levels of hierarchy is an active thinking technique.
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 →