The power of strategic narrative | Andy Raskin
Executive Summary
Andy Raskin joins Lenny Rachitsky to discuss a shared strategic narrative, old-game to new-game shifts, stakes and collaborative revision. Selected coverage omits category-design opinions and detailed Airbnb/Guild examples. Company examples and growth claims are his account, unverified here. Narrative is not proof of a market change; stakes need honest evidence. Untimed topics are editorial, not video chapters.
Key Takeaways
Use one story across the business
Raskin describes strategic narrative as a story the CEO uses across marketing, sales, product and other work. It can guide choices rather than merely decorate a deck. His account of business results is difficult to isolate, so the interview does not establish a measured causal return from narrative.
Avoid opening with self-congratulation
He calls the familiar problem, solution and why-we-are-better pitch the arrogant doctor. His criticism is about a structure that can encourage bragging, not a claim that comparing solutions is never useful. Begin by making the buyer's changing situation understandable.
Describe a real old-game to new-game shift
Raskin borrows a world-changing opening from movie structure and applies it to business. The narrative names what is changing and why a buyer might need a new approach. Do not treat a compelling change story as evidence that the asserted market shift is true.
Name the shift concisely
He favors short names for the old and new games rather than long lists of before-and-after bullets. Concision helps a team share the idea, but it can omit nuance. Check that the simplified language remains accurate for the customer and market.
Make the stakes concrete without false urgency
He recommends showing what matters about the shift, including examples of people already succeeding with a new approach. The interview acknowledges that some dramatic statistics can be misleading. Verify evidence rather than borrowing a life-and-death framing that the facts do not support.
Put obstacles before product capabilities
Raskin explains how a new desired state gives context to the obstacles a buyer faces. Capabilities then become ways to overcome those obstacles instead of a disconnected feature list. The selected summary omits his detailed category-design and Airbnb/Guild examples.
Build and revise with a small team and customers
He asks the CEO for a small narrative team and has it interview customers about the shift. A first version is expected to discard many ideas and attract criticism before it improves. Customer language and team feedback help refine the story; the first draft is not a final verdict.
The Conversation Breakdown
Use one story across the business
⏱ Untimed topicRaskin describes strategic narrative as a story the CEO uses across marketing, sales, product and other work. It can guide choices rather than merely decorate a deck. His account of business results is difficult to isolate, so the interview does not establish a measured causal return from narrative.
Avoid opening with self-congratulation
⏱ Untimed topicHe calls the familiar problem, solution and why-we-are-better pitch the arrogant doctor. His criticism is about a structure that can encourage bragging, not a claim that comparing solutions is never useful. Begin by making the buyer's changing situation understandable.
Describe a real old-game to new-game shift
⏱ Untimed topicRaskin borrows a world-changing opening from movie structure and applies it to business. The narrative names what is changing and why a buyer might need a new approach. Do not treat a compelling change story as evidence that the asserted market shift is true.
Name the shift concisely
⏱ Untimed topicHe favors short names for the old and new games rather than long lists of before-and-after bullets. Concision helps a team share the idea, but it can omit nuance. Check that the simplified language remains accurate for the customer and market.
Make the stakes concrete without false urgency
⏱ Untimed topicHe recommends showing what matters about the shift, including examples of people already succeeding with a new approach. The interview acknowledges that some dramatic statistics can be misleading. Verify evidence rather than borrowing a life-and-death framing that the facts do not support.
Put obstacles before product capabilities
⏱ Untimed topicRaskin explains how a new desired state gives context to the obstacles a buyer faces. Capabilities then become ways to overcome those obstacles instead of a disconnected feature list. The selected summary omits his detailed category-design and Airbnb/Guild examples.
Build and revise with a small team and customers
⏱ Untimed topicHe asks the CEO for a small narrative team and has it interview customers about the shift. A first version is expected to discard many ideas and attract criticism before it improves. Customer language and team feedback help refine the story; the first draft is not a final verdict.
Core Frameworks & Ideas
Old game to new game
Name a real market shift and explain why a buyer needs a different approach.
Stakes and obstacles
Connect evidence of the change to the desired state and the difficulties in reaching it.
Small narrative team
Develop a first draft with the CEO, interview customers and revise with a few relevant colleagues.
Actionable Next Steps
- ✓Name the old and new games in concise language and check accuracy.
- ✓Collect evidence for the shift and remove unsupported urgency.
- ✓List the obstacles between the customer and the desired state.
- ✓Interview customers and revise a first draft with a small cross-functional team.
Notable Quotes
“And I call this shift the shift from the old game to the new game.”
“This very, very concise naming is really key.”
“The second piece is what I call naming the stakes.”
The One Thing to Remember
Tell an accurate story about the buyer's changing world before explaining how your product helps them move through it.