New Product Development: Concept & Validation
From idea to validated concept
This domain covers the front end of development: generating ideas, screening them, shaping a concept, and testing whether it deserves investment. Candidates should know the stage-gate and fuzzy front end concepts, idea screening criteria, and the difference between a concept (a described solution to a customer need) and a product (a buildable, launchable offering).
Concepts a candidate must understand
- Voice of the customer (VOC) and jobs-to-be-done: capture needs in the customer's language, not the team's.
- Opportunity assessment: market size, competitive landscape, strategic fit, and capability fit.
- Concept testing: present the concept (not the product) to target users and measure comprehension, appeal, and purchase intent.
- Prototyping fidelity: low-fidelity prototypes test desirability and usability cheaply; high-fidelity prototypes test feasibility and detailed interaction.
- Assumption mapping and experiments: identify the riskiest assumptions (desirability, viability, feasibility) and design the cheapest test that could invalidate them.
- Business case: revenue model, cost structure, and risk, feeding the go/no-go gate.
Traps in exam questions
Common traps: treating a single enthusiastic customer as market validation; confusing concept testing with usability testing; assuming a survey of purchase intent equals demand; and skipping the viability (business model) test while only testing desirability.
Worked example
A team has a concept for a scheduling tool. The riskiest assumption is not whether users find it appealing but whether they will pay. A landing-page test with a price and a waitlist measures willingness to pay far more cheaply than building the product.
Rule of thumb
Test the assumption most likely to kill the business, and test it with the cheapest experiment that produces a credible signal.