Rflct

How to evaluate concepts

Concept evaluation is not about asking consumers whether they like a concept. It is about understanding which attributes drive preference, what separates the concept from alternatives, and whether enough people accept the price point.

Most concept tests centre on general appeal — 'do you like this concept?'. The problem is that general appeal rarely predicts market success. A concept everyone finds 'somewhat good' can lose to one that a defined target audience loves.

Reflect evaluates concepts by decomposing the decision: which attributes drive choice? Where does the concept differ most from existing alternatives? And crucially — is there a price level at which the concept is accepted without eroding perceived value?

This approach ties concept testing directly to business decisions, not just appeal scores.

Upcoming visual
Concept evaluation flow — from screening to final prioritization

Key takeaways

  • General appeal rarely predicts success
  • Decompose into attribute drivers, differentiation and price acceptance
  • Avoid binary yes/no tests, measure trade-offs
  • Conjoint provides better decision support than top-box scales
  • Always tie the test to a specific decision context

Example

A food manufacturer tested three new concept variants using top-box scales. All three scored similarly. When we used conjoint analysis instead, one concept showed significantly higher price elasticity margin — customers were willing to pay 12% more without volume loss.

Related articles

Product development starts with the decision context

A new product does not succeed because it is technically superior. It succeeds when it solves a decision problem better than existing alternatives, in the context where the purchase actually happens.

From insight to concept prioritization

Insights without a prioritization framework rarely lead to action. Reflect connects consumer insights to a quantified ranking of concept alternatives, based on expected market potential, not just appeal.

See related service

Discuss concept evaluation with us

Contact us
Back to Product development with data, not guesswork