A two-level hierarchy of customer benefits mapping a product's full problem space. Dan Olsen's example is TurboTax: top-level benefits — improve confidence, save time, save money — each with child benefits underneath them.
Apply: sort every candidate feature idea into an existing rung of the ladder; a genuinely new top-level rung is rare and should be treated as a notable strategic addition, not a routine one. Complements Problem Space vs. Solution Space as a way to organize problem-space needs before they're run through the Kano Model.
Olsen uses two techniques to build a benefit ladder: the onion model, which peels a high-level problem (e.g., "help me prepare my taxes") down through successive layers toward atomic customer benefits, and the five whys, asking "why does that matter" repeatedly to drive the same descent. The atomic benefits at the bottom then "ladder up" into a small number of macro benefits at the top.
He also warns against vague noun-based benefit statements like "security" — a benefit statement should be phrased with a verb (e.g., "protect my identity from theft") so the team is forced to say what value is actually being created, rather than gesturing at a category.
Olsen's interview method for actually building a ladder: after a customer states a benefit they want, ask "why does that matter to you?" and repeat with each new answer. "Each time I ask why I'm trying to get the customer to go to a higher level benefit." Different customers' answers, and different starting complaints from the same customer, often converge on the same one or two macro benefits after several rounds of "why" — revealing the shared higher-level need underneath surface-level, detailed answers. Contrast with Onion Model (Problem-Layer Peeling), which peels a generic problem statement downward into specifics rather than climbing a specific benefit upward.
The underlying need on a benefit ladder can stay stable for decades while the solutions serving it rotate through generations. Olsen's example: "listen to music on the go" produced troubadours, transistor radios, the Walkman, the Discman, MP3 players, the iPod, and finally phones — successive answers to the same need across roughly 30 years. See The '11 out of 10' Question for how the iPod's arrival specifically reset that need's satisfaction ceiling rather than fixing something broken.
Most "new" feature ideas aren't new value. Olsen's caution for brainstorming sessions: most new feature ideas a team generates aren't new value at all — they're just alternate ways to deliver the same small set of "evergreen" macro benefits already on the ladder. A genuinely new benefit ladder (a new underlying need, not a new delivery mechanism for an old one) is rare, and worth flagging specifically when it shows up.