Base120 · Decomposition
Abstraction Laddering
Move up and down conceptual hierarchy to find appropriate solution level
When to use
"Use when a problem is stuck at one level of abstraction. Move up (more abstract) to see the pattern; move down (more concrete) to see the detail. The right level is where the problem is tractable."
Example
"Why is our software slow? (concrete) -> Why does our architecture have performance bottlenecks? (more abstract) -> Why did we choose a synchronous architecture? (even more abstract) -> Because we prioritized simplicity over throughput (root value). Each level suggests different solutions."
Common misuse
"Staying at the level where you are comfortable. A detail person stays concrete and misses the pattern; a strategy person stays abstract and misses the implementation. Both are avoidance, not analysis."