"The Arrogant Doctor says: I have a solution to your problem. Strategic Narrative says: the world has shifted — here's the new game, and we'll help you win it."
The Framework
The 5-Part Strategic Narrative
Step 1 — Name the Shift
Declare the old game is over; a new game has begun. Name both concisely — you're overstating to make it stick. Salesforce: "Software is over. Welcome to the Cloud." Precision beats completeness. Two words on each side.
Step 2 — Name the Stakes
Show winners already playing the new game. Make the future split between a very bad outcome and a potentially great one. George Lucas killed Luke's aunt and uncle so the reluctant buyer couldn't say "maybe later." Kill the prospect's aunt and uncle — figuratively.
Step 3 — Name the Object
State the rallying cry — the mission of the movement. Often best as a question: "What would it take to turn every customer into a subscriber?" Asymptotically unachievable. Think Airbnb's "Belong Anywhere." This is your company's actual mission.
Step 4 — Name the Obstacles
If winning the new game were easy, you wouldn't need to exist. Surface the new challenges the shift creates — the monsters in Lord of the Rings. Not ordinary problems: emotionally loaded obstacles to a goal the buyer now believes in. Zuora asked: how do you measure lifetime value? How do you track changing preferences?
Step 5 — Show the Magic Gifts
Only now talk about your product. It's the hero's magic gifts for conquering the obstacles. Features are props that make the story come true — important props, but never the story itself.
The Salesforce blueprint
Benioff never led with features. He led with a movement: software is dead, cloud is the new game. Siebel and others were suddenly part of the old, losing game — no comparison needed.
Deep Dive Playbook
How to Build & Test Your Narrative
Assemble a 4-person narrative team — CEO plus leads of marketing, sales, and one critical function. The CEO must lead personally, not just sponsor it. Engagements where the CEO was fully in produced narratives that became true north stars.
Kickoff session: brainstorm all pieces — old game, new game, stakes, winners. The team will generate massive amounts of material. All of it is valuable as raw input, almost none of it survives.
Interview customers between sessions. They often hand you the exact words. Gong's "opinions to reality" framing came from buyers, not from the team's brainstorm.
CEO + consultant draft v1 alone. Expect to throw out 95% of the team's material. This is necessary — sharp narrative requires ruthless compression. You lose completeness, you gain power.
Plan for a painful second session. The team gave you gold; the draft tosses most of it. That's expected. A bad draft is a million times more useful than a list of great ideas. The CFO at one engagement said Andy should have warned her "exactly how bad" the second session would feel.
Test in live sales calls before rolling out. Watch buyer reaction when you name the shift. Do they lean in and say "yes, I'm seeing that too"? That's your signal. Train reps to ask: "Am I crazy, or are you seeing this shift?"
360Learning case study
CEO Nick Hernandez had a category name — "collaborative learning" — but no story behind it. Reps kept getting: "how are you different from X?" Andy reframed: old game = top-down training from a central learning guru. New game = upskill from within, where internal experts become champions. McDonald's had a recruiting poster that said exactly that. The question became: "What would it take to turn your experts into learning stars?" Result: the competitive comparison question disappeared from sales calls entirely.
Gong case study
At Series B, strong PMF but features-first pitch. The strategic narrative (opinions → reality) repositioned Gong from a sales ops tool to a mandate for sales leadership. CEO Amit Bendov: "Revenue Intelligence could have been called Strawberry Intelligence. It didn't matter. The story mattered." The narrative also became the product filter — feature requests that recorded opinions were declined. No committee needed.
Tactics
Pitch & Slide Tactics
Make every slide title a takeaway, not a label. "The Team" → "Our team are veterans of X." Every slide title = a complete thought. Zero cognitive work for the reader. This one change makes decks flow dramatically better.
Name the shift in two words per side. Opinions → Reality. Transactions → Subscriptions. Software → Cloud. Compression is credibility.
Prove stakes with winner logos. Don't claim the shift — show Airbnb, Spotify, Box already winning in the new game. The logos carry the argument.
Frame the object as a question. "What would it take to turn every customer into a subscriber?" pulls the buyer in as co-author. They're not passive recipients — they're explorers on the same journey.
Never template it. Copying the Zuora deck with your logo is the #1 mistake. The structure is principles, not slides. Some companies nail the shift in 1 slide; others need 4.
Best fit: B2B enterprise. Group buyers, complex products, high stakes. Consumer products with spec-comparison buying behavior are a weak fit.
Strategic narrative vs. category design
Category names are shorthand for movements, not the movements themselves. "Revenue Intelligence" worked because the story was there. Without the story, three magic words do nothing.
Contrarian
Strategic Narrative Myths
✗Lead with the problem you solveINSTEAD →✓ Lead with the world-shift that makes your problem life-or-death. "I solve your pain" puts you in Arrogant Doctor mode — bragging about your treatment. "The game has changed" puts you in movement-creator mode. Buyers don't follow products; they follow movements.
✗Category names create categoriesINSTEAD →✓ Stories create categories. "Revenue Intelligence" became a category because Gong had a compelling opinions-to-reality narrative — not because the words were magical. Gong's CEO said they could have called it "Strawberry Intelligence" and the outcome would have been the same.
✗Strategic narrative is a sales toolINSTEAD →✓ It's a product north star first. The best use is deciding what NOT to build — without a committee. "Does this feature help us upskill from within?" In → build it. No → deprioritize. The narrative makes the call faster than any roadmap meeting.
✗The first draft should be goodINSTEAD →✓ The first draft should exist, full stop. A bad draft is a million times more useful than a list of brilliant ideas. Expect the second session to hurt — the team gave you gold and the draft threw most of it out. That pain is the process working correctly.