Abstraction Laddering
Abstraction Laddering is a problem-framing technique that moves a problem statement up and down levels of abstraction: asking "why?" produces broader statements that show the purpose behind the problem, and asking "how?" produces narrower statements that point towards solutions. The group ends up with a ladder of related framings and chooses the rung at which the problem is most useful to solve. The idea of a ladder of abstraction goes back to S. I. Hayakawa's writing on language, and its use for framing problems was developed in the Creative Problem Solving community, where a close relative is known as Challenge Mapping.
Facilitation script
- 1
Explain the two questions and the two directions. Write the starting problem statement on a note, read it aloud and place it in the middle of the wall.
5 min - 2
Climb: ask why of the statement, write the broader statement above it, and repeat for three or four rungs. Add branches where the group gives different answers.
10 min - 3
Descend: go back to the starting statement and to one or two other rungs, ask how, and add more concrete statements below until they are specific enough to act on.
10 min - 4
Read the ladder from top to bottom together. Ask which rung is within the team's influence and which offers the most room for solutions.
8 min - 5
Mark the chosen rung or rungs, reword them as the questions for the next step, and note any rung that should go back to the sponsor for a scope decision.
7 min
Tips
Insist that every rung is written as a full problem statement and not as a keyword, otherwise the next why or how has nothing to grip.
Draw connecting lines as you go, because the value of the ladder is in seeing which narrow statement serves which broad one.
Expect the group to feel uncomfortable near the top, where statements start to sound like mission slogans.
That is the signal to stop climbing, not to argue about wording.
Common pitfalls
Climbing only: the group enjoys the big-picture statements, never comes back down, and leaves with a purpose statement and no workable problem
Answering how with finished solutions instead of narrower problem statements, which turns the lower half of the ladder into a premature idea list and closes off alternatives
Forcing a single line when the group gives several answers to one why, so the branch that held the more useful framing is never written down
Skipping the review at the end: the ladder stays on the wall as a diagram and the team carries on with the statement it started with
Letting the most senior person answer every why, so the ladder records one person's reasoning and the rest of the group does not own the chosen framing
Variations
Remote: build the ladder on a shared whiteboard with one person scribing and everyone else answering aloud or in chat; branching is easier to manage on a digital board than on a wall. Solo or pairs: the technique works well as a ten-minute warm-up for one person reviewing a brief. Larger groups: split into teams of three or four, let each team ladder the same starting statement, then compare the ladders and note where they diverge. Challenge Mapping, the Creative Problem Solving relative of this technique, works the same two directions but phrases every rung as a "How might we" challenge and asks "What is stopping us?" to move down.
Where it fits
When to use it
A brief arrives phrased as a solution ("build a chatbot") and the team needs to find the problem it is supposed to solve
The problem statement is so broad that nobody knows where to start, and the group needs more concrete entry points
Team members are arguing about solutions because each of them is silently working on a different level of the problem
You are about to run an ideation session and want to choose the framing deliberately instead of taking the first wording
A sponsor and a delivery team need to agree how much of the wider problem is in scope
When not to use it
You are looking for the cause of a specific failure or defect: use The 5 Whys or an Ishikawa Diagram, which trace causes and not purposes
The group wants to find its shared purpose and motivation: Nine Whys does that through paired interviews and stays in the upward direction
The framing is fixed by contract or regulation and cannot change: laddering only produces frustration about options the team does not have
The group knows very little about the problem yet: do research or stakeholder interviews first, because the rungs would be guesses
Related methods
Frequently asked questions
What is Abstraction Laddering?▾
Abstraction Laddering is a problem-framing technique in which a group takes a problem statement and restates it at broader and narrower levels. Asking "why?" moves up to the purpose behind the problem, and asking "how?" moves down to more concrete versions of it. The group then chooses the level at which it makes most sense to work.
What is the difference between Abstraction Laddering and The 5 Whys?▾
The 5 Whys asks why something went wrong and traces a chain of causes back to a root cause. Abstraction Laddering asks why a goal matters, which leads to a broader purpose and not to a cause, and it also moves downward with how. Use The 5 Whys to diagnose a failure and Abstraction Laddering to decide how to frame a challenge.
How many rungs should the ladder have?▾
Three or four rungs in each direction is usually enough. Stop climbing when the statements become so general that they would fit any project, and stop descending when a statement is concrete enough that someone could begin work on it. A ladder with branches at one or two rungs is normal and often more useful than a single straight line.
How does Abstraction Laddering connect to How Might We questions?▾
Each rung of the ladder can be rewritten as a How Might We question, so one session gives you questions at several levels of ambition. Teams often pick one broad and one narrow question to take into ideation. That gives the session room for bold ideas while keeping a practical option in play.
How long does Abstraction Laddering take?▾
Plan 20 to 45 minutes for a group of two to eight people working on one problem statement. A single person or a pair can sketch a useful ladder in about ten minutes. Allow more time if the choice of framing needs a decision from a sponsor who is in the room.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Abstraction Laddering into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Common practice from Creative Problem Solving, building on S. I. Hayakawa's ladder of abstraction; summary by Untools.