Internal Virality for Alignment
Get a big org aligned by making a prototype go viral inside the company instead of grinding stakeholder meetings
- Difficulty
- Advanced
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
In a large organization, alignment is normally created by a PM talking to stakeholders one by one — slow and laborious. The alternative: build a real, interactive prototype baked into the actual product, share the build internally, and let it spread on its own. If it's genuinely interesting, employees share it with each other exactly like consumers do, and excitement climbs from engineers to managers to VPs to the CEO — creating instant, organic alignment.
Origin
Developed by Gaurav Misra as head of the design-engineering function at Snap, as the company scaled past thousands of engineers.
Core principles
- 01A company large enough behaves like a consumer network: interesting things get shared person to person
- 02Working prototypes create belief in a way documents and specs cannot
- 03Alignment that spreads organically is faster and stickier than alignment negotiated stakeholder by stakeholder
- 04Prototypes also de-risk big bets: test a rough version in a limited market before committing hundreds of engineers
How to run it
- 1
Build a real prototype, not a deck
Have a small team of people who can do the whole design-engineering process in their head assemble an interactive prototype baked into the real app.
Pro tip Staff this with 'design engineers' — people who can conceive the UX, design it, and build it themselves.
- 2
Optionally test it in the wild first
Run the prototype with a limited real audience (e.g. a couple of high schools or one country) to gather real-world behavior data before broad internal sharing.
- 3
Share the build internally and let it spread
Release the build inside the company and let employees pass it around. Track the excitement climbing the org.
- 4
Ride the alignment to commitment
Once leadership is asking 'why am I the last to hear about this?', the org is aligned and eager — now commit the full engineering investment to build it at scale.
Pro tip Only put hundreds of engineers on a six-month build after the prototype has proven the product's dynamics.
In the wild
Misra's design-engineering team would rebuild an area of Snapchat as a working prototype and simply share the build. It would explode internally — engineers, then managers, then VPs, then Evan Spiegel asking why he was the last to hear about it.
→ Instant company-wide alignment and enthusiasm around the new direction, without the usual stakeholder-by-stakeholder alignment grind.
Common mistakes
Relying on specs and meetings to align a big org
Documents don't create belief; people need to touch a working thing to get excited and aligned.
Committing the full team before prototyping
Spending 500 engineers for a year on an unproven idea is a catastrophic bet; prototype and test first.
Is it for you?
Best for
Design/product leaders inside large organizations who need to move a slow-moving org toward a new, innovative direction
Not ideal for
Small teams already aligned by proximity, or cultures where shipping unpolished internal prototypes is politically risky
From the transcript
“as the company gets bigger you can actually create alignment by causing internal virality”
“we would create these prototype products right we would just go into an area redo a bunch of stuff create these prototype products that didn't…”
“day after day we would hear from you know engineers then managers then VPS then eventually from Evan being like Oh my God like everyone's…”
“once we understand the product and the Dynamics then it makes sense to put on 500 Engineers for six months to build it”
From the episode
How to win in the AI era: Ship a feature every week, embrace technical debt, ruthlessly cut scope, and create magic your competitors can't copy
Gaurav Misra (CEO and co-founder of Captions)