Claim
Inside a strategic narrative, the buyer's pains are the gates between where they are and the new-game victory state — not isolated "problems." Frame your features as the gifts that get them past the gates. Problem-framing commoditizes; obstacle-framing positions the product as necessary to win.
Mechanism
Problem-framing answers "what does this tool do?" — and any competing tool can answer the same way. Obstacle-framing answers "what stands between you and the new-game victory?" — which only makes sense within the narrative your product authored. The buyer's mental rehearsal of the journey now has your features in it as load-bearing assists, not as fungible solutions.
Conditions
Holds when:
- The strategic narrative is already established and the buyer has bought into the new game.
- Each obstacle maps cleanly to a buyer-felt gap, not an internal product surface.
Fails when:
- The audience hasn't yet bought the new game. They hear "obstacles" as theatre.
- The mapping is forced — features that don't actually clear an obstacle but get listed anyway dilute the narrative.
Evidence
"Problem framing — sales teams lack insights — commoditizes the solution. Obstacle framing — how do you get reality into all your sales calls? — positions the tool as necessary to win the new game."
Zuora's deck lists obstacles as questions: How do you measure lifetime value? How do you track changing preferences? Each obstacle becomes a slide; each slide leads into a feature gift.
— Andy Raskin on Lenny's Podcast, 2026-04-28
Signals
- Sales decks open with the new-game state, then walk obstacles, then features.
- Demo flow follows the same arc; reps don't lead with the product UI.
- Buyers nod at the obstacles before seeing the features.
Counter-evidence
April Dunford warns against story-first decks that hide whether the product is actually competitive. Obstacle-framing without genuine differentiation is theatre. Use only after positioning has confirmed the product wins on its unique-value axes.
Cross-references
- Sell the world-shift, not the product comparison — the wrapper this works inside