Concept Testing

Test product and messaging concepts with target users to learn appeal, clarity, and preference before heavy build investment. Use when evaluating early ideas, value propositions, or design directions with structured feedback.

itsual Updated

File contents

Concept Testing

Overview

Concept testing evaluates ideas while they are still cheap to change. It measures understanding, desirability, and relative preference — not final usability of a finished product.

When to Use

  • Early product or feature concepts
  • Value proposition and messaging tests
  • Comparing alternative directions
  • Go/no-go inputs before roadmap commitment

Core Practices

  • Present concepts consistently (fidelity matched to the question)
  • Test comprehension before preference
  • Ask about job relevance and differentiation from alternatives
  • Use both qualitative probes and structured ratings when useful
  • Avoid over-indexing on polite enthusiasm
  • Compare concepts against each other and against status quo

Principles

  • Stated intent ≠ future behavior — treat as directional
  • Higher fidelity is not always better for early concepts
  • Audience quality matters more than sample size theater
  • Kill weak concepts quickly; don’t “average” them into mediocrity

Verification

  • Concepts were understood as intended
  • Evaluation criteria match the decision needed
  • Results distinguish winners from polite nods

itsual/agent-skills-collection/tree/main/skills/research/concept-testing commit 551c020bfb

Frequently asked questions

npx skillmds@latest add itsual/concept-testing