Concept Testing
“The evaluation of product or feature concepts with target users before significant investment.”
You've got an idea the team loves. Someone mocked it up. You showed a few people and they said it looked great. Now you're wondering whether that actually means anything.
Concept testing is an early-stage validation technique. You present product or feature concepts to target users — through descriptions, sketches, wireframes, or prototypes — and evaluate whether the idea resonates before committing to development.
Its strength is catching bad ideas when changes are still cheap. Reach for it once you have a concept clear enough to show but before you've invested enough to feel committed. The critical discipline is separating stated interest from genuine intent — people are polite, and "I'd use that" costs nothing to say.
Comparative testing and commitment measures (would you pay? would you switch?) cut closer to truth. The failure mode is treating positive reactions as market validation. Controlled enthusiasm in a research session doesn't predict real-world adoption, and teams that conflate the two build confidently in the wrong direction.
Your next move: When users said they'd love your concept, did anyone ask them what they'd give up to have it — or did you take 'yes' as the answer to a question you didn't ask?
What it looked like for them
Sergio Schuler, Teamometer, early 2010s. Schuler had an idea for a team management tool. Before writing a line of code, he built a two-page website: a landing page with an explainer video, a "try it free" button, and a second page that captured the visitor's email.
He spent a few dollars on Google AdWords to drive cold traffic and measured how many people clicked. Not enough did. Schuler shelved the project before he'd built anything he'd have to shut down.
The test didn't measure whether the product was good. It didn't measure whether he could build it. It measured whether the words on the landing page, against ads running to a cold audience, produced enough interest to justify the engineering work. The answer was no, and the answer cost less than a week's groceries. The move that mattered wasn't the landing page. It was deciding what "enough interest" meant before the test ran.
“A stakeholder keeps changing their mind and I can't lock the scope.”