Concept testing

When to run concept testing

Concept testing is the right call when you have a candidate solution and you need to learn how the audience reacts before you invest engineering, design, or campaign budget. The goal is to find out which concepts resonate, which fall flat, and who the concept is actually for, with enough specificity that you can either commit, kill, or refine.

The most common moments: pre-launch validation, stage-gate review, choosing between concept variants, refining a redesign before engineering scope is locked, deciding whether to greenlight a campaign or a feature. The pattern that fails most often: ship the concept that won the loudest internal vote and discover after launch that no segment actually wanted it.

How Candor runs it

You provide the concept (description, wireframes, copy, or a mix) and define the audience. Candor builds synthetic personas grounded in real evidence and runs the concept test against them. You can test up to twelve concepts at once, and the format follows the count: monadic for one (depth focus), comparative for two to four (head to head), and card sort at five or more, where personas sort and rank the concepts and the interviewer deep-dives the top of the pile rather than treating all twelve equally.

There is a second choice on the same screen: the concept test type. Everything above describes a standard test, where people meet whole concepts cold and react to them. The other three test a set of options for one concept you already have. A name test checks whether candidate names fit and connect to what the product does. A value proposition test checks which benefit is most compelling and believable. A messaging test checks which headline is clearest and most persuasive. All three expose the anchor concept first and then present the options inside that context, so nobody judges a name in a vacuum.

Sequence them the way the decision runs. Settle whether the concept lands with a standard test, then sharpen how you describe it with a follow-on test. Naming a concept nobody wants yet is effort spent on the wrong question.

Each interview probes resonance, comprehension, friction, and willingness to act. The persona’s prior conversation context stays loaded across questions, so reactions cohere instead of drifting. The critic agent validates each response against the persona’s prior statements before delivery, so a persona who praised something in turn three doesn’t silently contradict it in turn ten.

What you walk away with

A synthesis report that frames concept-specific findings: resonance points by archetype, friction points by archetype, audience-fit alignment, and the tensions where two segments disagreed. For comparative or card-sort studies, the report includes ranking patterns and the reasoning behind each persona’s preference. Every finding links back to the specific quotes, the personas who said them, and the evidence sources behind those personas.

The output is shaped to drive the next decision. Concepts that won across most archetypes move forward. Concepts that won only with a narrow segment become segmentation decisions: ship to that segment, or refine for a broader fit. Concepts that lost across the board get killed before they consume more cycles.

Where to go next

Before concept testing, validate that the underlying problem is real with problem validation. After concept testing, refine how you describe the winning concept with value-prop testing, and pressure-test the price with price testing. If you want to stress-test the strategic assumptions sitting behind the concept itself, layer in assumption validation.