The same story told the same way falls flat in half the rooms you bring it into. Your executive team wants the shift and the stakes. Your product team wants the problem and the proof. A nervous team in the middle of a re-org wants to know what it means for them on Monday. Go-to-market isn't a launch, a pitch deck, or a campaign. It's an end-to-end journey that connects how you work inside with what customers experience outside — and storytelling is the thread that carries it from strategy to sales. The thread stays the same. The shape of the story changes in every room.
We remember stories, not slides. In a Stanford class experiment described in Made to Stick (Chip Heath and Dan Heath, 2007), 63% of students remembered the stories from classmates' speeches, while only 5% remembered a single statistic. So before you open a blank deck, get clear on four things: why you're telling this story, who it's for, the arc it needs, and the one message you want them to leave with.
Here's how I structure the arc for each moment.
1. The Strategy Story: Name the shift before the plan
Use it for: Annual planning, leadership offsites, company kickoffs, executive updates.
The shift: What changed in the market, the customer, or the business.
The stakes: What it costs to stand still.
The choice: Where you'll play — and what you'll explicitly stop doing.
The path: Three to five objectives with measurable key results.
The roles: What each team owns in making it real.
The ask: The commitment you need before everyone leaves the room.
Salesforce named the "end of software" — the move from on-premise software to the cloud — before it ever pitched a product. Watch out for a list of priorities with no trade-offs. If nothing is off the table, nothing is a strategy.
2. The Product Story: Start with the customer's every day
Use it for: Product visions, roadmap reviews, funding asks, pitch decks.
Every day: What your customer's world looks like now.
One day: The moment it breaks — the friction, cost, or unmet need.
Because of that: The insight you saw that others missed.
The solution: How the product solves it, in three pillars or fewer.
The evidence: Signals of market fit — pilots, usage, waitlists, quotes.
Until finally: The future it unlocks and the roadmap to get there.
The ask: Build it, fund it, or pilot it.
Slack built its micro-copy, onboarding, and integrations around one idea — eliminating friction — so every feature told the same story. Watch out for opening with features. Nobody cares about the how until they believe the why.
3. The Leadership Story: Lead with the solution
Use it for: Decision meetings, project updates, budget requests, promotion asks.
The headline: Your recommendation in 12 words or less.
The context: Only what the room needs to judge it.
The options: Two or three paths and the trade-off of each.
The recommendation: Which path and why.
The unlock: What happens the moment it's approved.
The decision: Exactly what you need, from whom, by when.
I once watched 22 product squads present their key metric to leadership. The readouts that used a consistent one-page shape got decisions in minutes; the rest got follow-up meetings. Watch out for the status update disguised as a story. If someone asks "so what do you need from me?", you buried the headline.
4. The Change Story: Make the employee the hero
Use it for: Reorganizations, AI and technology rollouts, new processes, culture shifts.
The catalyst: Why change, and why now.
The anchor: What's not changing — values, people, purpose.
The bridge: What stops, what starts, and what stays.
The destination: What a good day looks like once the change takes hold.
The support: Training, tools, and who to ask.
The first step: One action people can take this week, and the early wins you'll celebrate.
Microsoft shifted its culture from "know-it-all" to "learn-it-all" before it asked teams to innovate in the cloud. Culture moved first; execution followed. Watch out for announcing without context. Teams rarely resist change. They resist ambiguity.
5. The Brand Story: Your customer is the hero, not you
Use it for: Brand statements, websites, campaigns, keynotes, founder stories, events.
The hero: Who your customer is and what they want.
The obstacle: What stands in their way.
The guide: Why you understand — and why you're credible.
The promise: What you'll help them do, in plain language.
The transformation: Who they become on the other side.
The proof: Real people, real stories, real results.
Airbnb's "Belong Anywhere" told host stories instead of selling filters and property specs. And remember that a brand story isn't only told in words: how your brand sounds, looks, and feels in every interaction should carry the same arc. Watch out for casting your company as the hero. If your brand story starts with "we," start again.
6. The Sales Story: Walk the journey together
Use it for: Discovery calls, executive pitches, proposals, quarterly business reviews.
Their world: What you heard in discovery, in their words.
The hidden cost: The problem they hadn't fully sized.
What could be: The future state, in their terms.
How we get there: The approach on one visual.
The proof: A customer like them who made the leap.
The next step: A mutual plan with dates and owners.
Gong led discovery with real conversation data that revealed hidden revenue risk, so buyers saw the problem for themselves. I've seen a single, simple visual reset an entire enterprise sales conversation when 50 slides of architecture diagrams couldn't. Watch out for clicking through the whole deck. That signals a vendor closing quota, not a partner solving a problem.
One thread, six shapes
The arcs change. The core story shouldn't. Your strategy, product, leadership, change, brand, and sales stories should all echo the same short statement of who you are and why you matter. You'll know it's working when heads nod instead of multitasking, people ask "what's next?" instead of "where is this going?", and the room moves straight to action.
So, do you know the story you're shaping?
If you're shaping one of these stories right now, I'd love to hear what you're working on. Sometimes a 30-minute conversation is all it takes to find the arc. Grab time to chat →
