Move up and down levels of abstraction

Abstraction Laddering

Abstraction laddering is a technique that helps you reframe problems by moving up to more abstract levels ('why') and down to more concrete levels ('how').

In one sentence

Move up and down levels of abstraction

Quick facts
Time required
5–10 minutes
Primary benefit
Reframing Problems
Techniques
9 individual techniques
Category
Analogical Thinking
What it is

The core mechanism.

Abstraction laddering is a technique that helps you reframe problems by moving up to more abstract levels ('why') and down to more concrete levels ('how').

The science

Where it came from.

Research in problem-solving shows that the ability to shift between different levels of abstraction is key to finding innovative solutions. Studies in cognitive psychology demonstrate that experts are particularly skilled at moving between abstract principles and concrete details. This aligns with design thinking practices that emphasize the importance of properly framing problems before attempting solutions.

Techniques

9 techniques, each ready to use.

Each technique is a distinct prompt or operation. Apply them one at a time or combine several for deeper exploration.

01
Current Problem
State your challenge clearly
What specific problem are you trying to solve right now? State it as clearly and concretely as possible. This is your starting point on the abstraction ladder. Example: 'Our app's signup process has a 40% abandonment rate.'
02
Why? — Level 1
First level abstraction up
Why are you trying to solve this problem? What's the purpose behind addressing this specific issue? This moves you one level up the abstraction ladder. Example: 'We need to simplify the user onboarding experience.'
03
Why? — Level 2
Second level abstraction up
Why does that broader purpose matter? What's the even bigger goal or need? This takes you another level up the ladder. Example: 'We want to increase user adoption of our service.'
04
Why? — Level 3
Third level abstraction up
Why is that larger goal important? What fundamental value or principle underlies it? This brings you to a high level of abstraction. Example: 'We believe our service improves people's quality of life.'
05
Alternative Frame
Select a different abstraction level
Looking at the different levels of abstraction you've identified, which one offers the most promising reframing of your challenge? Choose a level that's not too abstract (vague) or too concrete (limiting).
06
How? — Level 1
First level abstraction down
From your chosen abstraction level, ask: How might we address this challenge? This brings you one level down toward concrete solutions. Example: 'How might we create a more inviting first-time user experience?'
07
How? — Level 2
Second level abstraction down
How specifically could we implement that approach? What more concrete methods could work? This brings you closer to specific solutions. Example: 'How might we reduce the perceived complexity of our signup form?'
08
How? — Level 3
Third level abstraction down
How exactly would we execute that method? What specific, actionable steps could we take? This brings you to very concrete solutions. Example: 'How might we create a single-field progressive signup form?'
09
Parallel Ladders
Explore multiple abstraction paths
Create multiple abstraction ladders starting from different 'Why?' answers at the same level. This helps explore parallel solution spaces. What different paths of reasoning might lead to diverse approaches to your challenge?
Best practices

How to apply it effectively.

Start by clearly defining your current problem framing. Move up the abstraction ladder by asking 'Why?' to explore broader purposes. Move down by asking 'How?' to explore concrete solutions. Choose an abstraction level that provides helpful insights while remaining actionable. Create multiple ladders to explore different perspectives. Look for connections between levels that might suggest innovative approaches.

Best use cases

When to reach for this.

  • When you're too close to a specific problem formulation
  • When the problem scope might be wrong (too narrow or too broad)
  • When you need to find the right level of abstraction for a solution
  • When different stakeholders are solving for different levels of the same problem
Other strategies in this category

Keep exploring.