Concept Testing
Putting an idea in front of the people it is for, before it is built, to find out whether it is worth building.
Process & MethodsConcept testing asks whether an idea is worth pursuing, not whether an interface works. The stimulus is deliberately rough — a description, a sketch, a landing page, a storyboard — because polish invites feedback on the polish. What you are listening for is whether people recognise the problem, whether they already have a way of solving it, and what they would give up to use this instead.
The reliable signals are behavioural, not verbal. Enthusiasm is free. Asking to be told when it launches, agreeing to a follow-up, giving up an email address, naming a budget, or describing the workaround they would abandon — those cost something and mean something. “That's interesting” means nothing and is the most common result.
Concept testing is not usability testing
Concept testing asks “is this worth building”. Usability testing asks “can people use what we built”. Running usability tasks on a concept produces feedback about a prototype's rough edges and no information about demand.
In practice
A team tested two concepts for an automated reconciliation feature with nine finance managers. Both got warm reactions. Asked what they would stop doing if it existed, seven could not name anything for concept A and all nine named a specific weekly spreadsheet for concept B. The enthusiasm had been identical; only one concept displaced real work.
Where teams get it wrong
- Testing a polished prototype, which collects feedback on visual details instead of the idea.
- Treating stated enthusiasm as demand.
- Testing with people who are not the intended user because they are easier to recruit.
- Presenting one concept, which gives people nothing to compare against.
- Asking whether they would pay, instead of what they would stop doing.
Learn more
You may ask
Frequently Asked Questions
What is the difference between concept testing and usability testing?
Concept testing asks whether an idea is worth building; usability testing asks whether a built thing can be used. Concept tests use rough stimuli on purpose, because polish shifts the conversation to the polish.
What signals show a concept is worth building?
Behavioural ones — people naming the workaround they would abandon, asking to be notified at launch, giving contact details, or stating a budget. Verbal enthusiasm costs nothing and predicts nothing.
Related terms
All terms- Preference TestingShowing people two or more designs and asking which they prefer and why — useful for direction, unreliable as a decision.
- Usability TestingWatching real users attempt real tasks in a product or prototype to find where they struggle, without steering them.
- MVP (Minimum Viable Product)The smallest version of a product that delivers real value to real users and produces evidence about whether the idea works.
- Product-Market FitThe point at which a product satisfies a real market demand strongly enough that usage and revenue grow without being pushed.
Defined by Mara Last reviewed .
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us