Annoyance-to-Prototype Loop
Turn a repeated irritation into a tested physical solution
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 90%
The Annoyance-to-Prototype Loop begins with a recurring, concrete inconvenience rather than a broad ambition to invent something. Describe the frustrating moment and look for independent confirmation from another person experiencing the same constraint. Search the market immediately; the purpose is to test whether the solution truly does not exist, not to protect the excitement of the idea. If the gap remains, build a rough physical model that demonstrates the missing function with whatever is available. Take that model to someone who understands manufacturing or the relevant industry and ask for a functional prototype. Test whether it solves the original moment before expanding the vision. Finally, separate product quality from execution quality so operational setbacks do not automatically invalidate a useful invention.
Origin
Hutt and her sister could not use reading glasses while having their hair colored. They confirmed the shared problem, searched for a solution, made a chopstick model, and brought it to an eyewear contact who returned from China with a prototype.
Core principles
- 01A specific lived irritation is a useful discovery signal
- 02Independent confirmation strengthens the problem
- 03Search before assuming a solution is missing
- 04A crude model communicates function better than explanation
- 05Domain expertise can rapidly convert a concept into a prototype
How to run it
- 1
Capture the irritation
Define the exact situation, user, and constraint that makes an existing product fail.
Pro tip Describe the moment behaviorally rather than saying only that the product is annoying.
Watch out A broad complaint is too vague to guide a prototype.
- 2
Confirm the problem
Ask another plausible user whether the same situation causes the same frustration.
Pro tip Independent spontaneous frustration is stronger than agreement after a sales pitch.
Watch out One person's preference is not yet a market.
- 3
Search the existing market
Look for products that already perform the required function before investing in development.
Pro tip Search by the job to be done as well as by familiar product names.
Watch out Do not treat a poor first search as proof that nothing exists.
- 4
Model the function
Build a crude representation that shows how the product would behave, even if it is made from improvised materials.
Pro tip Prioritize movement and function over appearance.
Watch out Do not spend on polish before the core mechanism is understandable.
- 5
Recruit domain expertise
Show the model to a relevant industry or manufacturing expert who can translate it into a working prototype.
Pro tip Bring the model and the original use case to keep the conversation concrete.
Watch out Expert help cannot compensate for an undefined user problem.
- 6
Test the original moment
Use the functional prototype in the exact situation that exposed the problem and refine it from observed failures.
Pro tip Test the primary function before adding secondary features.
Watch out Operational mistakes after launch do not necessarily mean the underlying product failed.
In the wild
Hutt and her sister both found that ordinary reading glasses interfered with hair coloring. They searched and found no suitable product, made a model with chopsticks, and showed it to an eyewear-industry contact. The contact returned from China with a prototype of wearable, tiltable, flippable reading glasses.
→ A shared salon irritation became a patented consumer product that later generated millions in gross sales.
Common mistakes
Falling in love before searching
Skipping the market search risks spending time recreating a solution that is already available.
Explaining without modeling
A purely verbal idea leaves the mechanism ambiguous; even a crude physical model can reveal and communicate the intended function.
Blaming the product for execution
Supply, focus, or operating failures should be diagnosed separately from whether the product solves the original problem.
Is it for you?
Best for
It is best for specific recurring consumer problems whose desired function can be represented with a simple physical model.
Not ideal for
It is not ideal when the apparent gap has not been searched, the problem is unique to one person, or prototyping would create material safety risk.
From the transcript
“we start googling we look them up they don't exist”
“I bring glasses that I made with chopsticks that look like this”
“Andrea our our partner was going to China like a week later she ended up going to China and coming back with a prototype”
From the episode
Episode 329: Jenny Hutt: Growing Up In The Music Industry, Entrepreneurship & Partnering with Shark Tank
Jenny Hutt