Product Testing Ladder
Test personally, verify compliance, then recruit users with real context
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
Begin with direct use: the founder should put the product into the environment and tasks it claims to support. The guest gives examples such as carrying a backpack on a mountain, sleeping in outdoor gear, and repeatedly using a mug. Once the founder is satisfied, obtain any required legal, compliance, or technical testing from an appropriate third party. Then widen the evidence base to relevant users, such as members of an existing community, and to creators who genuinely use that product category. Ask for feedback before requesting promotion. Their real-use observations can guide a revision and, if they later choose to discuss the product, give them a truthful account of how their feedback affected it. The sequence combines founder scrutiny, specialist verification, and representative use without pretending that any one layer replaces the others.
Origin
Extracted from The Foundr Podcast
Core principles
- 01The founder should experience the product's real use case
- 02Personal testing does not replace required legal or technical testing
- 03Relevant users reveal context-specific problems
- 04Early contributors may explain improvements credibly at launch
How to run it
- 1
Test the promised use
Use the product repeatedly under the conditions customers will face. Record specific failures in fit, function, durability, or usability.
Pro tip Test the whole job, such as loading and carrying the backpack, not just one feature in isolation.
Watch out Do not perform unsafe tests without appropriate expertise or controls.
- 2
Verify formal requirements
Identify and commission required legal, product, or technical testing. Keep the evidence linked to the exact product version.
Watch out Founder use is not a substitute for required compliance testing.
- 3
Recruit representative testers
Offer the product to relevant community members and ask for concrete feedback. Select people whose normal context matches the intended customer.
Pro tip Ask what failed or felt awkward, not only whether they liked it.
- 4
Invite expert-user input
Approach a relevant creator or experienced user for development feedback before discussing promotion. Make participation and any later promotion separate decisions.
Pro tip Choose someone who would genuinely use the product.
Watch out Do not imply that feedback guarantees an endorsement.
- 5
Revise and retest
Prioritise material or repeated findings, update the sample, and run the relevant tests again. Preserve which feedback changed which version.
Watch out A changed product invalidates evidence that depended on the previous version.
In the wild
The guest suggests asking a travel creator to use an unreleased backpack and describe what works and what does not. If the creator reports that the shoulder straps are too thick, the brand can revise them and retest before launch rather than waiting for a promotional transaction.
→ Relevant pre-launch use informs the product, while any later promotion can accurately describe the contributor's role.
Common mistakes
Testing only at a desk
A product can appear sound without performing its complete customer job in realistic conditions.
Skipping formal testing
Personal satisfaction and beta feedback do not replace legal or specialist verification where required.
Making feedback transactional
Asking for a post before asking for honest use feedback can weaken the development value of the relationship.
Is it for you?
Best for
Pre-launch physical products that can be safely tested by the founder and representative users.
Not ideal for
Products where unqualified personal or beta testing would be unsafe, unethical, or legally insufficient.
From the transcript
“So, most important is test it yourself. You will be the toughest critic of your actual product.”
From the episode
585: The $100K Mistake Most Founders Make with Manufacturers (and How to Avoid It) (Best of Foundr)