Two-Audience Physical Product Validation Loop
Test the promise with buyers and the experience with users
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
Start by defining the experience the subscription or product must reliably promise. Test early concepts with the person who pays, because that buyer determines whether the offer appears valuable and distinctive. Separately, put prototypes in the hands of the actual user and observe engagement and usability rather than relying on stated preference. Convert every failure into a specific revision, then run another session. KiwiCo used SurveyMonkey to expose box concepts to parents and garage play dates to watch children interact with projects. Its first three crates each received about 15 testing sessions. The loop is especially important for physical products because launch inventory cannot be changed as quickly as software, and a recurring product must deliver consistently enough to retain customers.
Origin
Extracted from The Foundr Podcast
Core principles
- 01The buyer and user may judge different dimensions of value
- 02Physical products need more validation before launch than easily updated software
- 03A repeatable subscription promise must be both engaging and worth paying for
- 04Observed friction should trigger another test cycle
How to run it
- 1
Define the promise
Specify the recurring experience and quality bar customers should expect even when they do not know the exact item in advance.
Pro tip Separate child engagement from parent-perceived value.
Watch out Do not define the product only by its component list.
- 2
Test buyer appeal
Put alternative concepts in front of purchasers and learn which feel useful, distinctive, and worth paying for.
Pro tip Use lightweight surveys before committing to expensive tooling.
- 3
Observe end users
Let target users engage with prototypes in realistic conditions and watch where they struggle or disengage.
Pro tip Observe behaviour instead of asking users to predict it.
Watch out Buyer enthusiasm does not prove user usability.
- 4
Diagnose concrete failures
Translate observations into specific issues with materials, instructions, fun, or value.
Pro tip Name the failed dimension before changing the prototype.
- 5
Revise and retest
Change the affected element and run another buyer or user session until the product repeatedly clears the defined bar.
Pro tip Keep testing through the full journey from concept to final material choice.
Watch out Do not treat one successful session as validation.
In the wild
In one early crate, children struggled because certain clays were not malleable enough for little hands. The team treated that observation as a product failure, changed the material, and ran another testing session rather than accepting the original specification.
→ The material was iterated against observed child usability before launch.
Common mistakes
Testing only the purchaser
A parent may value the concept while a child cannot use or enjoy the product. Test both roles independently.
Treating hardware like software
Physical inventory is slower to revise after release, so shipping an under-tested version creates greater risk.
Is it for you?
Best for
It is best for physical products where the purchaser and end user are different people.
Not ideal for
It is not ideal for low-risk digital products that can be corrected immediately after release.
From the transcript
“And so we did quite a bit of I would say concepting and testing we would put different types of ideas around what would go…”
“And then the other thing that we did is we would have kids descend to my into my garage to actually engage with the project…”
“So I'd say in terms of the number of testing sessions for a given crate for the first three crates, each one probably had at…”
From the episode
687: I Broke Every DTC Rule and Built a $1 Billion Brand From My Garage