Concept Testing Template for User Research

Concept testing evaluates whether users want something. Usability testing evaluates whether users can use something. In concept testing, you show an idea and measure comprehension, desirability, and intent. In usability testing, you give users a task and measure completion rate, errors, and time. Run concept tests first (to validate the idea), then usability tests (to validate the implementation). Both are part of the discovery process described in the [Product Discovery Handbook](/discovery-guide).

Match fidelity to the risk you are trying to reduce. Use low fidelity (description or sketch) when testing whether the idea itself has value. Use medium fidelity (wireframe or clickable mockup) when testing interaction patterns. Use high fidelity only when visual design is the value proposition (e.g., a design tool or consumer app). Higher fidelity costs more to produce but reduces the risk that participants reject the concept because they cannot visualize it.

Three rules. First, show the concept without explaining it. If you say "We built this to help you collaborate better," you have primed them. Instead say "Take a look at this and tell me what you think it is." Second, ask neutral questions. "What stands out to you?" not "Do you like this?" Third, probe negative signals. When a participant says "This is interesting," follow up with "What concerns you about it?" not "What do you like about it?"

This is a common result. High desirability with low purchase intent means the concept is appealing but not essential. Your options: reduce scope to lower development cost (making the ROI work even at low conversion), bundle it with existing paid features to increase perceived package value, or test different pricing and packaging. Use the [RICE Calculator](/tools/rice-calculator) to score the opportunity against alternatives on your roadmap.

Test one concept if you want depth. Test 2-3 concepts if you want comparison. Testing multiple concepts reveals relative preferences ("I prefer A to B because...") that single-concept tests miss. Keep the total session under 30 minutes regardless. If testing multiple concepts, randomize the presentation order across participants to avoid order bias. ---