Use caseValidate a product concept
Have likely buyers judge a product idea, read its appeal score beside their reasons, and decide whether to build it, change it or stop, before engineering time is committed.
The concept is judged by the people who would pay for it, in the words they would use, before a single sprint is planned around it.
The concept is written as a short card, the way a buyer would describe the problem, with the benefit, how it works and the reason to believe it. When several concepts are compared, every card is equally finished, so none wins by its writing.
The audience is the people who would choose and pay, such as the operations manager who buys the tool, as well as the enthusiasts who like new things, since the buyer's doubts are the ones that stop a sale.
Pulse runs a short survey on appeal, clarity and purchase intent, and the team treats the intent figure as the most the idea could achieve, since people overstate what they will buy.
The world's most ambitious teams research with Pulse.
GrowwThe decision rarely turns on the average score, and more often on who loved the idea, who could not follow it and what would have changed their mind.
Video insights record the moment each participant takes in the concept, interest rising at the benefit or doubt at the price, which the team can set beside the score that person gave.
The objections that would stop someone buying, such as switching effort or a missing integration, become the questions engineering and design must answer before the build starts, or the reasons to stop.
Participants say what they would add, remove or explain differently, and a revised concept can go back to the same kind of buyer for a second round before anything is built.
Understand how people interpret, value and respond to a new product, service or feature concept, before you invest in building it.
Concept validation belongs to the family of concept testing methods, used before significant investment to check that an idea is worth pursuing. A concept is described in a consistent format, with the need it meets, the main benefit and the reasons to believe, and tested with people in the target market. Quantitative measures such as appeal, relevance, uniqueness and purchase intent show how strong the idea is. Qualitative questions reveal what people understood, what they valued and what raised doubts. Stated intent overstates real demand, so scores are best used to compare ideas and to spot weaknesses, and a sales forecast needs other inputs. Teams often run validation in rounds, revising the concept after each one, until the idea is clear and compelling or the evidence says to stop.
Panel regulars who approve of everything would inflate the ceiling the team already treats with caution. Screening against the target profile and a fraud check on every participant keep the appeal score to people who buy in the category.
An appeal score on a slide invites a debate about whether it is good enough. A recording of the buyer who would sign off the purchase, explaining what stops them, placed beside the score, moves the review to the objection.
Engineering capacity for next quarter is allocated at planning. With the brief framed around build, change or stop, the concept's verdict is due before that allocation, while stopping still costs no more than the study.
Buyers see each concept on screen during the interview and say, in their own words, what it would do for them, so the team can tell a weak idea from a card that was misread before anyone drops it.