The Strategy-Isn't-Done-Without-Wireframes Rule
Treat a strategy doc like a house blueprint: it isn't complete until wireframes show what the product looks like when the strategy is built.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 85%
A discipline that forces strategic alignment by requiring wireframes as part of any strategy document. Words alone leave everyone with a different interpretation of the strategy; wireframes make it concrete and expose the trade-offs, because there are only ever a limited number of pixels on screen. Mehta institutes it as a hard bar: the strategy doc isn't complete without wireframes.
Origin
Originated when Ravi Mehta led the trip-planning strategy at TripAdvisor — the first time he made wireframes a required part of a strategy doc, working top-down rather than getting to strategy experimentally from the bottom up.
Core principles
- 01Strategy described in words alone leaves everyone with a different interpretation.
- 02You'd never hire an architect who wouldn't give you a blueprint — a strategy doc needs the same.
- 03Wireframes needn't be high-fidelity; a conceptual layout is enough to create alignment.
- 04A limited number of nav-bar slots forces the real trade-offs to the surface.
How to run it
- 1
Set wireframes as a completion bar for strategy
Declare that the strategy doc isn't complete without wireframes. Work top-down: define what you want to achieve, how, and the incremental steps, then render it visually.
- 2
Keep the fidelity conceptual
Produce low-fidelity, conceptual wireframes — like an architect's blueprint that shows how the pieces come together, not a finished rendering. This is enough to align people.
Pro tip No designer? Sketch on paper or use Balsamiq — in an afternoon you can produce high-level conceptual wireframes that beat a words-only spec.
Watch out Don't use lack of a designer as an excuse; learn to sketch and learn Balsamiq so you're not dependent on a designer every time.
- 3
Apply the nav-bar litmus test
Ask: a mobile app can only have four or five items on its nav bar — what are they? Forcing this choice exposes where team members secretly disagree about what's valuable.
Watch out If you only describe strategy in words, people arrive at implementation with completely different nav bars and clash over what matters.
In the wild
Trip planning was a valuable but intractable problem that multiple startups and even Google had failed to nail. Rather than work bottoms-up and hope to ladder up to a clear strategy, Mehta's team worked top-down and put a stake in the ground: the strategy doc wouldn't be complete without wireframes, because words alone produced divergent interpretations.
→ Wireframes created far more alignment on what the product would look like when the strategy was implemented, and forced the team to confront the trade-offs of a limited screen up front.
Common mistakes
Shipping a words-only strategy doc
When strategy is described in words alone, everyone takes away a different interpretation — and the conflict only surfaces at implementation, when the team discovers wildly different perceptions of what's valuable and how the app should be organized.
Outsourcing all visual thinking to designers
PMs who can't wireframe feel they must depend on a designer every time, slowing everything down. Mehta argues UX/UI thinking is a core PM skill; sketching or Balsamiq makes a PM more empowered and self-sufficient.
Is it for you?
Best for
PMs and product leaders writing strategy for a new, ambiguous product surface where alignment is at risk.
Not ideal for
Non-visual products or infrastructure work where a screen layout isn't the meaningful artifact of the strategy.
From the transcript
“one of the things that we said with steak that we put in the ground was the strategy doc wouldn't be complete without wire friends”
“when you actually can show people wireframes of what the product will look like when that strategy is implemented it creates much more alignment”
“it's a little bit like working with an architect you would never work with an architect that didn't provide you a blueprint of the house”
“in a lot of mobile apps can only have four or five things on their nav bar what are the four or five things”
From the episode
Building your product strategy stack
Ravi Mehta (Tinder, Facebook, Tripadvisor, Outpace)