How to test ideas?
Common, structured, low-cost ways to test your ideas most critical assumptions.
Method
Customer Interview
Description
A one-on-one conversation with a real or potential customer, designed to understand their world, their challenges, priorities,
and what they currently do to solve problem — rather than to pitch your idea
Focus
Desirability, viability
Activities
Setup
1. Define interview objectives and success criteria
2. Develop interview script and question framework
3. Recruit target participants from customer segment
4. Prepare recording setup and consent process
Run
5. Conduct structured interviews with participants
6. Observe and document behavioral cues and reactions
7. Gather feedback on value proposition and cost sensitivity
Learn
8. Synthesize patterns and recurring themes
9. Validate assumptions and update product direction
Nuances
Common Mistakes
1. Asking hypothetical questions about future behavior ("Would you use this?") instead of past behavior.
2. Pitching your solution during the interview instead of listening.
3. Treating what customers say they want as ground truth, without probing deeper.
4. Not actively listening or paraphrasing to confirm your understanding.
5. Asking leading or close-ended questions that steer answers towards your preferred outcome.
Tips for Success
1. Ask open-ended questions about past behaviours and real experiences, not hypotheticals.
2. Focus entirely on understanding the customer's current problems and daily frustrations.
3. Talk to target customers before building anything, even a prototype.
4. Actively listen and summarize key points back to the interviewee to confirm accuracy.

“Let the speaker speak truly and the judge decide justly.”
— Socrates, in Plato’s Apology
Method
Expert Interview
Description
A targeted conversation with a domain expert, industry specialist, potential partner, or internal stakeholder to quickly stress-test your assumptions about a market, technology, or business model.
Focus
Desirability, viability, feasibility
Activities
Setup
1. Identify required expert profiles and domain focus
2. Source and reach out to relevant domain experts
3. Prepare context brief and interview guide
4. Schedule interviews and establish recording protocols
Run
5. Conduct expert conversations on technical and market feasibility
6. Capture expert opinions on competitive landscape and challenges
7. Gather advice on go-to-market strategy and partnerships
Learn
8. Cross-reference expert opinions for consensus and disagreement
9. Inform product roadmap and strategic decisions
Nuances
Common Mistakes
1. Asking leading questions that nudge the expert toward confirming your existing beliefs.
2. Treating expert interviews the same as customer interviews — the goals and questions are different.
3. Failing to clearly define what you need to learn before the conversation.
4. Talking more than the expert, rather than listening and probing.
5. Relying on a single expert's perspective without seeking diverse viewpoints.
Tips for Success
1. Clearly define your research objectives and the specific uncertainties you need to resolve.
2. Prepare open-ended, well-researched questions that invite honest, unbiased responses.
3. Actively listen and ask follow-up questions to go beyond surface-level answers.
4. Recruit experts with different backgrounds and viewpoints to avoid confirmation bias.
5. Focus on understanding the broader context — trends, history, and known failure modes — not just validation.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Online Ad
Description
An online advertisement that clearly communicates a value proposition to a targeted audience with a simple call to action, used to measure whether real people respond to your message before you build anything.
Focus
Desirability
Activities
Setup
1. Define advertisement testing objectives and target audience
2. Create multiple ad creative variations and copy
3. Set up campaign infrastructure and landing page
4. Establish tracking and measurement systems
Run
5. Launch targeted ad campaigns across selected platforms
6. Monitor real-time performance and audience engagement
7. Optimize campaigns based on performance data
Learn
8. Analyze campaign performance across all variations
9. Quantify customer acquisition costs and demand signals
Nuances
Common Mistakes
1. Testing too many variables, such as headline, image, and audience, at the same time, making results unreadable.
2. Not defining clear success metrics upfront — knowing what “good” looks like before you launch.
3. Ignoring audience segmentation and running ads to a broad, untargeted group.
4. Ending the campaign too early before collecting statistically meaningful data.
5. Optimizing for vanity metrics like impressions or clicks rather than meaningful actions like sign-ups.
Tips for Success
1. Formulate a clear, falsifiable hypothesis before launching — for example, “10% of our target audience will click through.”
2. Test one key assumption per ad set to keep results clean and actionable.
3. Define specific, measurable success criteria in advance.
4. You can use A/B testing with a control group to isolate what is actually driving results.
5. Iterate quickly based on data — pause underperforming ads and double down on what works.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Data Sheet
Description
A single-page document listing key specifications, features, and performance data about your product or service, shared with technically sophisticated customers or partners to gauge their interest and validate your value proposition.
Focus
Desirability, viability, feasibility
Activities
Setup
1. Develop comprehensive technical specification document
2. Design clear information hierarchy and visual elements
3. Identify technical prospects and distribution strategy
Run
4. Distribute data sheet to technical prospects
5. Track engagement and download metrics
6. Follow up with comprehension and interest assessment
7. Collect detailed feedback on technical positioning
Learn
8. Analyze technical comprehension and information gaps
9. Refine technical documentation and sales enablement
Nuances
Common Mistakes
1. Collecting feedback without a clear hypothesis about what you are trying to learn.
2. Over-analyzing responses to the point of inaction — analysis paralysis.
3. Ignoring qualitative feedback and focusing only on download numbers.
4. Not defining what a successful response looks like before distributing the sheet.
5. Drawing firm conclusions from too small or unrepresentative a sample.
Tips for Success
1. Define clear, testable hypotheses before distributing — know what you are trying to prove or disprove.
2. Focus on actionable metrics that will directly inform a decision.
3. Combine quantitative engagement data with qualitative follow-up conversations.
4. Move quickly — do not wait for perfect data before drawing initial conclusions.
5. Use the minimum amount of information needed to validate the core assumption.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Stroyboard
Description
A visual sequence of illustrated panels — like a comic strip — that walks a customer through the experience of discovering, using, and benefiting from your product, used to test whether the story resonates before anything is built.
Focus
Desirability, viability
Activities
Setup
1. Map customer journey and identify key story moments
2. Create visual storyboard panels with clear narrative flow
3. Prepare testing protocol and participant recruitment
Run
4. Present storyboard to target participants
5. Facilitate narrative comprehension testing
6. Identify confusion points and emotional reactions
7. Test motivational impact and action intent
Learn
8. Analyze narrative clarity and emotional resonance
9. Refine customer experience flow and messaging
Nuances
Common Mistakes
1. Spending too much time on visual polish instead of focusing on the core idea and story.
2. Cramming too much text into panels, making the narrative hard to follow at a glance.
3. Starting without a clear hypothesis or a specific assumption you are trying to test.
4. Collecting general impressions rather than actionable feedback tied to specific assumptions.
5. Overcomplicating the narrative with too many steps, losing the clarity of the core message.
Tips for Success
1. Keep it simple and visual — focus on the key moments in the user journey, not every detail.
2. Define the specific hypothesis you are testing before you draw the first panel.
3. Center the story on the user's emotional experience, not the product's features.
4. Use it as a fast, low-cost way to gather early qualitative feedback from real people.
5. Iterate the story rapidly based on what resonates and what confuses — do not aim for perfection.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Test on Existing Product
Description
A structured session where you observe real users completing tasks on a competitor's or analogous product, in order to uncover unmet needs, frustrations, and opportunities that your solution could address.
Focus
Desirability
Activities
Setup
1. Select relevant competitor products for testing
2. Recruit target participants and prepare testing protocol
3. Design structured testing sessions and analysis framework
Run
4. Facilitate competitor product testing sessions
5. Document user behavior and interaction patterns
6. Conduct post-test interviews about experience
7. Observe emotional responses and satisfaction levels
Learn
8. Identify unmet needs and competitive gaps
9. Inform unique value proposition and feature prioritization
Nuances
Common Mistakes
1. Testing too many variables at once, making it hard to identify the true source of friction.
2. Asking users what they think rather than observing what they actually do.
3. Not defining a clear learning objective before the session begins.
4. Treating qualitative observations as if they were statistically validated findings.
5. Failing to establish measurable success criteria before running the sessions.
Tips for Success
1. Formulate a single, focused hypothesis for each testing session.
2. Define clear, measurable success metrics before you begin observing.
3. Watch behavior directly — what users do is far more revealing than what they say.
4. Keep tasks realistic and grounded in how users would naturally encounter the product.
5. Use findings to iterate quickly on your own value proposition and feature priorities.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Product Box
Description
A physical or digital mock-up of the packaging for your product — including name, tagline, key benefits, and a call to action — used to test whether your value proposition is compelling and clearly communicated at a glance.
Focus
Desirability
Activities
Setup
1. Design comprehensive product packaging concept
2. Develop testing methodology for first impressions
3. Create physical or digital mockup for testing
Run
4. Present product packaging to target users
5. Gather initial reactions and product assumptions
6. Assess shelf appeal and purchase intent
Learn
7. Analyze perceived value and target audience alignment
8. Assess brand positioning and competitive differentiation
9. Refine branding and packaging design strategy
Nuances
Common Mistakes
1. Listing product features instead of communicating clear, customer-centric benefits.
2. Designing the box for internal stakeholders rather than the actual target customer.
3. Over-complicating the design with too much information, diluting the core message.
4. Using internal jargon or technical language that customers will not immediately understand.
5. Failing to articulate a single, memorable value proposition on the front of the box.
Tips for Success
1. Lead with customer benefits and the core value proposition — not a feature list.
2. Keep all messaging concise and immediately understandable to a first-time viewer.
3. Involve diverse team members in the exercise to surface different perspectives.
4. Time-box the design activity to maintain focus and prevent over-engineering.
5. Practice “selling” the box out loud to a colleague — it quickly reveals gaps in the narrative.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Clickable Prototype
Description
An interactive, screen-by-screen simulation of your product — built in a design tool without writing real code — that allows real users to navigate and interact with it, revealing usability issues and validating the core experience.
Focus
Desirability, viability, feasibility
Activities
Setup
1. Define prototype scope and key user flows
2. Create interactive prototype using design tools
3. Recruit participants and prepare usability testing protocol
Run
4. Facilitate task-based usability testing sessions
5. Document navigation patterns and friction points
6. Measure task completion rates and efficiency
7. Gather qualitative feedback on user experience
Learn
8. Analyze usability issues and navigation problems
9. Prioritize design improvements and development efforts
Nuances
Common Mistakes
1. Skipping the discovery and research phase before jumping into prototyping.
2. Rushing straight to a high-fidelity, polished prototype before validating the basic concept.
3. Spending excessive time perfecting visual details before the core flows are validated.
4. Adding too many features to the prototype, obscuring what you are actually trying to learn.
5. Testing only with friends, family, or colleagues rather than actual target customers.
Tips for Success
1. Clearly define the purpose of the prototype and what specific questions it needs to answer.
2. Start with a low-fidelity version and iterate — fidelity should increase as confidence grows.
3. Agree on a “good enough” standard for the prototype before you start building it.
4. Focus the prototype on solving one core problem or testing one primary user flow.
5. Recruit participants who match your ideal customer profile and test with a diverse group.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Concierge
Description
A method where you manually deliver the core service to a small number of real customers — using people and manual effort instead of technology — to deeply understand what value is actually being created and whether customers will pay for it.
Focus
Desirability, viability, feasibility
Activities
Setup
1. Define manual service delivery process
2. Recruit early customers and establish service expectations
3. Create manual workflow and time tracking systems
Run
4. Deliver personalized service to early customers
5. Track time investment and service delivery costs
6. Maintain ongoing customer communication and support
7. Collect detailed feedback on service value and experience
Learn
8. Analyze service delivery economics and customer satisfaction
9. Inform automation strategy and scalable service design
Nuances
Common Mistakes
1. Automating steps too early, before you have deeply understood the customer's needs and pain points.
2. Trying to scale the service before the core value has been validated with a small group.
3. Not defining the specific problem you are solving before you start delivering the service.
4. Failing to capture structured qualitative feedback from every customer interaction.
5. Over-delivering to the point of setting expectations that a scaled product could never meet.
Tips for Success
1. Treat every delivery as a learning opportunity, not just a service transaction.
2. Do the work manually to discover which steps are truly valuable and which are unnecessary.
3. Document every customer interaction, decision, and piece of feedback systematically.
4. Look for repeating patterns in what customers ask for, struggle with, or value most.
5. Validate willingness to pay at a real price point before investing in building the technology.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Letter of Intent
Description
A simple, non-binding document that a potential customer or partner signs to formally express their intent to purchase or collaborate once the solution is built — providing a concrete signal of genuine market interest, particularly in B2B contexts.
Focus
Desirability, viability, feasibility
Activities
Setup
1. Draft professional Letter of Intent document
2. Identify and research qualified prospects
3. Develop personalized outreach strategy
Run
4. Execute targeted outreach to qualified prospects
5. Conduct LOI discussions and address concerns
6. Negotiate LOI terms and secure commitments
7. Track commitment quality and decision factors
Learn
8. Analyze commitment patterns and market interest
9. Inform sales strategy and partnership development
Nuances
Common Mistakes
1. Treating a signed LOI as a guaranteed sale — it is a signal of intent, not a binding contract.
2. Failing to articulate the value proposition clearly enough for the prospect to commit.
3. Not defining what a successful LOI campaign looks like before you start outreach.
4. Collecting LOIs from contacts who are not representative of your actual target customer.
5. Making the document so long or complex that prospects hesitate to sign it.
Tips for Success
1. Describe the product or service being validated clearly and specifically in the document.
2. Set measurable objectives — for example, a target number of signed LOIs within a defined timeframe.
3. Target early adopters who have a strong, immediate need for the solution.
4. Keep the LOI short, simple, and easy to sign — remove any friction from the process.
5. Use the conversations and objections during outreach to refine and improve your offering.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Programming Spike
Description
A short, time-boxed technical investigation where a developer explores a specific technology, API, or architectural approach to determine whether a proposed solution is actually buildable — before committing to a full development effort.
Focus
Feasibility
Activities
Setup
1. Define technical risk and spike objectives
2. Scope minimal proof-of-concept requirements
3. Set up development environment and documentation framework
Run
4. Build lightweight technical prototype
5. Test technical feasibility and performance
6. Explore integration challenges and system compatibility
7. Document technical findings and limitations
Learn
8. Analyze technical feasibility and implementation complexity
9. Inform technical architecture and development decisions
Nuances
Common Mistakes
1. Not setting a strict time limit, allowing the spike to expand indefinitely.
2. Starting without a clearly defined question that the spike is meant to answer.
3. Writing production-quality code during the spike, which defeats its exploratory purpose.
4. Using a spike for minor, low-risk uncertainties that do not justify the time investment.
5. Keeping the findings within the individual developer rather than sharing them with the team.
Tips for Success
1. Set a strict time box before you begin — typically one to three days — and stick to it.
2. Write down the specific technical question the spike must answer before writing a single line of code.
3. Focus entirely on learning and generating knowledge, not on building a shippable product.
4. Share all findings, code, and conclusions with the broader team immediately after the spike.
5. Reserve spikes for areas of genuine high uncertainty, where the technical risk could derail the project.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Method
Landing Page
Description
A single web page that communicates your value proposition, describes the problem you solve, and invites visitors to take a specific action — such as signing up or requesting access — used to measure real market interest before the product exists.
Focus
Desirability, viability, feasibility
Activities
Setup
1. Create compelling landing page content and structure
2. Build responsive landing page with analytics tracking
3. Establish traffic generation and conversion tracking
Run
4. Launch landing page and drive targeted traffic
5. Monitor real-time user behavior and engagement
6. Track conversion rates and user actions
7. Test different headlines, CTAs, and page elements
Learn
8. Analyze conversion data and user behavior patterns
9. Optimize messaging and page design for conversion
Nuances
Common Mistakes
1. Treating the landing page like a homepage with multiple goals, rather than a single focused experiment.
2. Testing low-risk assumptions instead of focusing on the riskiest ones first.
3. Writing copy that speaks to investors rather than directly to the target customer.
4. Ending the experiment too early, before enough data has been collected to draw valid conclusions.
5. Measuring page visits rather than meaningful conversion actions like sign-ups or pre-orders.
Tips for Success
1. Measure real customer behavior — sign-ups, clicks, and form completions — not hypothetical reactions.
2. Define specific, measurable success criteria before you launch, such as a target conversion rate.
3. Write in your customer's language — use the words and phrases they use to describe their problem.
4. Drive targeted traffic through focused channels, such as email, ads, and communities, rather than hoping for organic discovery.
5. Map each element of the page to a specific assumption you are testing, so every result is actionable.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
Interested?
Join Private Beta
Book Your Free Strategy Session Now
180 Strand, London
WC2R 1EA, United Kingdom