GuideConcept TestingNew Product ResearchPurchase IntentProduct Decisions

How to Conduct Product Concept Testing: Top Purchase Intent Does Not Automatically Justify Development

Use equally informative concept cards, randomized single-concept designs, and pre-set comprehension/credibility thresholds to separate appeal from feasibility; a 900-person case with three air-monitoring concepts supports decisions to proceed, revise, or stop.

Updated September 2, 2026 34 min read

Among three home air-monitor concepts, C had the highest purchase consideration rate, and the team was ready to move straight to development. But open-ended responses showed that many respondents understood it as an “automatic purifier,” while the concept actually only monitors and alerts. C won on the expectation of a feature that does not exist; if developed based on the highest score, the actual product would most likely disappoint upon delivery.

Concept testing does not answer “which card is most appealing,” but rather whether the key assumptions of a value proposition hold simultaneously: the target audience understands what problem it solves, considers the problem relevant to themselves, believes the promise is substantiated, and is willing to continue consideration under specified price and usage conditions. When comprehension or credibility fails, purchase intent only indicates that the packaged promise is attractive, not that development approval is warranted.

Do Not Combine Concept, Prototype, Creative, and Market Forecasting into One Test

ObjectKey QuestionAppropriate Evidence
Product conceptWhat problem does it solve for whom, and are the benefit and reason valid?Concept comprehension, relevance, credibility, uniqueness, consideration, and barriers
Interactive prototypeCan users accomplish tasks in a near-realistic flow?Observation, success, errors, time, and explanations
Advertising/packaging creativeHow can the same value be expressed to be more noticeable and understandable?Message communication, brand attribution, creative evaluation, and behavioral experiments
Sales or adoption forecastingHow much behavior will occur under real market conditions?Price, channel, competition, supply, and real choice/test-market data

If the concept itself is not correctly understood, a prettier poster may temporarily raise scores but does not prove that the product value holds. Conversely, an early concept card does not require a production-grade interface; it only needs to be sufficient to test the current riskiest assumption. The GOV.UK prototype guide points out that prototype fidelity should match the question being answered: sketches suit explorative ideas, while realistic interaction questions require code-based prototypes closer to the real product.

First, List the Assumptions That Would Invalidate Development if Wrong

Before drafting the concepts for the home air monitor project, the team registered four assumptions:

  1. Those responsible for household environmental decisions can distinguish between “monitoring alert” and “active purification”;
  2. They actually face the problem of not knowing when to ventilate or turn on a device;
  3. The explanations of sensing results, alert rationale, and data processing are sufficient to establish basic credibility;
  4. Under the same illustrative price, installation, and maintenance conditions, enough people are willing to proceed to a prototype trial.

HM Treasury’s 2026 Test and Learn guidance recommends prioritizing high-risk assumptions with the strongest impact on outcomes and the weakest current evidence; basic concept scenarios and storyboards reveal problems early but do not generate final effectiveness evidence. The value of concept testing lies precisely in using modest resources to decide what to validate next, not in proving commercial success with a single survey.

Three Concept Cards Must Be Equally Informative, Not Written as the Same Slogan

The following concepts are illustrative fictional examples. Each card includes the same information slots: usage scenario, current problem, core solution, user benefit, working rationale, limitations/requirements, price, and data handling. The goal is not to make the text stiff but to avoid a situation where A has polished visuals and a full price while B only has a slogan.

ConceptCore PromiseRationale and ConditionsPrimary Risky Assumptions
A: Action Timing AlertsMonitors air changes in the bedroom and alerts when ventilation or an environment check is neededShows monitored parameters, alert rules, and the need for manual user action; illustrative price of 499 yuanWhether alerts are sufficient to change daily behavior
B: Automatic Device CoordinationAutomatically executes preset coordination among supported purification or ventilation devicesLists compatibility boundaries, user confirmation, and local/cloud data conditions; same priceWhether automation promises are credible and compatibility range is acceptable
C: At-a-Glance StatusUses simplified status to tell a household whether the current environment requires attentionClarifies that it only monitors and interprets, not purifies; same priceWhether minimal expression could be mistaken for automatic air improvement

Price, warranty, installation, subscription, compatibility, and privacy must be equally disclosed across concepts if they are likely to alter choice. Deliberately providing implementation evidence only for a favored solution conflates “better information” with “better product.” Uncertain facts should be labeled as assumptions, and concept research must not be used to endorse unverified performance claims.

First Ask for Reproduction, Then Use Rating Scales to Teach the Intended Answer

The first core question after concept exposure should be as unaided as possible—for example: “In your own words, what will this product do or not do for you?” If you first ask, in sequence, “How useful are its alerts?” and “Would it help with ventilation?”, the questions have already taught respondents the benefits the designer wants to convey, and any subsequent reproduction is no longer spontaneous comprehension.

Open-ended reproductions should be coded against a pre-defined codebook as correct, partial, incorrect, or unclassifiable, with original text preserved. In the air monitor case, “monitors and alerts, requiring my action” is correct; “automatically improves air quality” is a critical misunderstanding. Two coders can independently code a subset of the text, discussing rules rather than forcing agreement to reach a certain impressive percentage.

After that, measure separately:

  • Problem relevance: Does the scenario occur in their lives?
  • Appeal of the benefit: Is the promised outcome worth it?
  • Credibility: Do they believe it can be delivered given the rationale and conditions?
  • Uniqueness: How is it different from current alternatives?
  • Consideration: Would they be willing to learn more or try it under an explicit price, maintenance, and privacy condition?
  • Strongest reason and biggest barrier: Explain their scores in their own words.

These dimensions cannot simply be summed into a single “concept index.” High appeal with low credibility calls for added evidence or a narrower promise; high uniqueness with low relevance may indicate the wrong audience; high consideration with low comprehension may be a false positive driven by misunderstanding.

Choosing Between Monadic, Sequential-Monadic, and Comparative Designs

Monadic testing shows each respondent only one concept, reducing direct comparison and fatigue, and better simulates independent market exposure; the cost is that each concept needs a sufficient sample. Sequential monadic testing lets the same person rate several concepts independently in sequence, making more efficient use of the sample, but the preceding concept sets a reference point, and respondents may tire. Independent ratings followed by comparison provides absolute reactions to each concept as well as final trade-offs, but comparison questions are influenced by the shown set.

When materials are complex, differences are subtle, or a real-world setting would only show one concept, prefer a monadic design. When the number of versions is limited, the materials are short, and a direct trade-off decision is required, a sequential-monadic design can be used, balancing the order of presentation. For any design, report precision based on the actual sample size per concept, not the total sample treated as a single-arm sample.

A 900-Person Monadic Case Study: Do Not Just Look at the Last Column

The team recruited 900 qualified participants from those actually responsible for choosing household environmental devices and whose homes matched the intended scenarios. They were stratified by key household contexts and randomly assigned to A, B, or C, with 300 per group. The results below are illustrative; the percentages do not represent real product or industry benchmarks:

MetricABC
Unaided correct comprehension246/300 (82%)264/300 (88%)210/300 (70%)
High top-two consideration189/300 (63%)174/300 (58%)201/300 (67%)
High top-two credibility213/300 (71%)156/300 (52%)234/300 (78%)
Perceived clear difference165/300 (55%)216/300 (72%)180/300 (60%)

The project gate established before the research was: correct comprehension above 75%, high top-two credibility above 60%, and no unresolved privacy or safety promises. Gates reflect this project’s resource and risk decisions, not a general industry standard.

A passes all four gates and moves to a more realistic prototype task; B, despite the highest uniqueness, is sent back for revision because of its 52% credibility, requiring a narrowed automation promise and clear compatibility evidence; C has the highest consideration at 67%, but with only 70% correct comprehension, the boundary of “monitoring, not purifying” must be revised and retested first. At present, C cannot be declared the winner.

A Lead in the Point Estimate Does Not Prove a Difference

C’s 67% is 4 percentage points higher than A’s 63%. For independent proportions of 300 per group, a rough conventional 95% interval for this difference is about -3.6 to 11.6 percentage points—spanning from nearly no difference to a business-meaningful advantage. Sample size should be determined by the minimum important difference defined before the study, not by deciding “that’s close enough to count as winning” after seeing a 4-point gap.

The ASA’s P-value statement emphasizes that scientific and business decisions should not rest solely on whether a significance threshold is crossed, and a P-value does not measure the size or importance of an effect. Concept decisions should combine effect size, uncertainty, comprehension and credibility gates, implementation cost, risks, and open-ended evidence.

Random Assignment Only Isolates Version Differences, Not Population Representativeness

Pew Research Center’s survey experiment explainer demonstrates how randomly assigning different question wording or response options to respondents allows the observed group differences to be attributed to the manipulated presentation. Concept testing is analogous: assignment must occur after qualification and before rating, and the version cannot be determined by channel, date, or prior answers.

At the same time, random assignment only makes the three groups in the study more comparable. If the sample comes from voluntarily participating smart-home enthusiasts, the relative comparisons among A, B, and C retain internal validity, but the overall consideration rates cannot be automatically extrapolated to all households. Reports must state the target population, sample source, eligibility, assignment, per-arm sample sizes, and any weighting—not merely “a random sample of 900.”

Current Alternatives Have More Explanatory Power than Abstract Uniqueness

Without revealing the concept’s intended answer beforehand, record how participants currently judge indoor air: by feeling, checking a weather app, using an existing sensor, turning on a purifier, or doing nothing. After concept evaluation, ask, “Compared with your current method, what does this solve or add as a hassle?”

“Unique in the market” is a researcher claim; “I no longer have to guess when to ventilate” is a respondent’s value statement. If high uniqueness comes from “never seen but not needed,” it is not worth developing; if low uniqueness comes from “I already solved it with an alternative,” the team should compare switching costs rather than continue stacking features.

Open-Ended Responses and Interviews Should Explain the Mechanism of Gate Failures

Quantitative results determine where to probe further: sample B respondents with high uniqueness and low credibility to understand whether they doubt the sensor, device compatibility, or automatic control; sample C respondents with incorrect comprehension to see whether the name, visual, or benefit statement implies purification. Do not only interview high scorers—include borderline, rejecters, and those who misunderstood.

AI or human interviews can be used for follow-up, but research goals must be fixed, appropriate consent obtained, and verifiable original quotes preserved. The role of interviews is to explain mechanisms and generate revised language—not to let a few vivid quotes override the distribution across 900 respondents.

Purchase Intent Cannot Be Simply Multiplied by Market Size

“Would consider” in a survey occurs under full attention, complete concept information, and an assumed price; real markets also involve availability, competition, budget timing, channel, brand trust, installation friction, and actual performance. Multiplying 67% by the target number of households to arrive at sales assumes full conversion and ignores these constraints.

The next evidence after a concept passes a gate could be a clickable prototype task, waitlist behavior, price experiments, controlled trials, or small-scale real-channel tests. The strength of validation should be proportional to the investment and the consequences of failure; early surveys serve to reduce uncertainty, not to issue sales promises.

In a Survey Panel, Link Version, Comprehension, and Follow-Up Probes into an Evidence Chain

The team can use a survey panel to first randomize concept versions according to a randomization plan, then collect unaided comprehension, diagnostic scales, and open-ended reasons separately; for key hesitations, subsequent AI or human interviews can deepen the findings. Exports must retain the concept card version, assignment arm, actual exposure, materials, display time, and quality flags.

A report eligible for approval is not just a leaderboard of total scores but answers, per concept: Who correctly understood what, in which scenario the value holds, what the most fragile credibility assumption is, how uncertain the point estimates are, and which type of more realistic evidence should be generated next. The highest purchase intent can be a clue; only when comprehension, credibility, relevance, boundary conditions, and a validation path are all clear does it become a product decision.

Foundations for Prototyping, Experimentation, and Product Decisions