Working-Prototype Frame Breaker
Build a tangible demonstration that replaces analogy with direct experience
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
The Working-Prototype Frame Breaker addresses a basic barrier to radical innovation: people map unfamiliar proposals into things they already know. Descriptions of Square sounded like conventional card processing, while descriptions of an electric car evoked a slow golf cart. The remedy is to build the smallest functional artifact that makes the novel behavior directly observable. Rehearse the essential interaction, demonstrate it without excessive explanation, and allow the experience to challenge the stakeholder's inherited assumptions. The prototype can unlock regulatory conversations, investment, customer understanding, and meaningful validation. It does not eliminate uncertainty; a product that works in a meeting may still fail in the market. Nor does it excuse permanent noncompliance—temporary prototype constraints must be resolved before broad release.
Origin
Square built a functional payment system before it knew whether the market wanted it. A polished demonstration showed a senior card-industry executive what words could not, prompting support for changing operating rules.
Core principles
- 01People interpret unfamiliar ideas through familiar categories
- 02Verbal descriptions cannot reliably convey a truly novel experience
- 03A working prototype can break an observer's existing frame of reference
- 04Prototype before seeking definitive validation
- 05Use the demonstration to enable informed decisions
How to run it
- 1
Diagnose the inherited frame
Determine what familiar but inaccurate comparison stakeholders make when they hear the idea described.
Pro tip Ask listeners to explain what they imagine before showing the product.
Watch out Do not assume your verbal explanation has created the same mental picture you hold.
- 2
Build the critical behavior
Create the smallest functional prototype that lets someone experience the product's defining difference.
Pro tip Prioritize the transformative interaction over visual completeness.
Watch out A static mock-up may preserve rather than break the old frame.
- 3
Rehearse the demonstration
Practice the interaction until it works reliably and communicates the value in a few moments.
Pro tip Remove features and commentary that distract from the central effect.
Watch out A fragile demo can reinforce skepticism.
- 4
Demonstrate, then pause
Let the stakeholder experience the prototype and leave room for the implication to register before arguing your case.
Pro tip Use silence to let decision-makers formulate their own conclusion.
Watch out Do not talk over the moment of recognition.
- 5
Validate and regularize
Use stakeholder and market reactions to improve the product, then obtain required approvals and compliance before scaling.
Pro tip Separate permission to continue testing from proof of customer demand.
Watch out A successful demonstration is not a guarantee of market adoption.
In the wild
Square demonstrated a working phone-based payment product to Ed McLoughlin even though the concept conflicted with existing operating regulations. After seeing the transaction work, he concluded that the rules would have to change. The demo made the new model concrete in a way a conceptual pitch could not.
→ The demonstration opened a path for Square to operate, although customer demand remained unproven until release.
People hearing 'electric car' imagined a weak golf cart. Elon Musk reportedly put people in an early Tesla, invited them to reach for the radio, and accelerated hard enough to press them into the seat. The physical experience instantly replaced the inaccurate analogy.
→ Observers directly understood that electric propulsion could provide exceptional acceleration.
Common mistakes
Pitching an abstraction
Slides and verbal descriptions allow stakeholders to force the idea into an old category, obscuring what is genuinely new.
Treating a demo as demand proof
A stakeholder's surprise or regulatory approval does not establish that enough customers will adopt the finished product.
Leaving violations unresolved
A prototype may expose outdated rules, but the business must still become compliant or secure formal rule changes before scaling.
Is it for you?
Best for
It is best for genuinely novel products whose core value becomes obvious only through direct use.
Not ideal for
It is not ideal when a cheap mock-up or established market evidence already communicates the proposition adequately.
From the transcript
“when you're building something new that somebody has never seen before, if you don't have a working prototype, people can't visualize it.”
“if you're gonna break that frame of reference, you better do it with a product that actually physically exists and works.”
“You don't get to test your product, if it's truly new, until it's built and working”
From the episode
Jim McKelvey on 'The Innovation Stack' (Podcast)