AI for New Product Development Research: Test Each Decision
New product development contains decisions about opportunity, concept, positioning, pricing, and launch. If research appears only after months of development, the team learns when changing course is most expensive.
The often-cited 70-90% new-product failure range is not a Subconscious benchmark. The structural point: concentrating research into one or two checkpoints leaves long stretches of product work driven by assumptions.
Find the missing decisions
Map where customer evidence enters the process:
- opportunity identification;
- concept generation and screening;
- concept validation;
- positioning and pricing;
- launch planning.
In many workflows, formal concept testing begins 3-6 months into the process. Early opportunity choices and late launch choices receive less direct customer evidence.
Test actions at each stage
Opportunity and ideation
Explore customer problems, workarounds, and unmet needs before generating solutions. Use simulation to form hypotheses, then validate the important ones with people and observed behavior.
Concept screening
A planning exercise might reduce twenty rough ideas to five candidates. Compare the same dimensions across each concept. Survival means a concept earned more research, not that the market validated it.
Concept validation
Compare shortlisted concepts on comprehension, relevance, objections, and directional preference.
Positioning and pricing
Compare “save time,” “reduce risk,” and “increase revenue” as distinct frames. Pricing work should remain decision-specific scenario testing unless a current study supports a stronger output.
Launch planning
Test messages, audience definitions, and adoption triggers before day one. Ask how a buyer would describe the product and what objection would stop the next action.
Use repeated small studies carefully
One workflow uses three capabilities: audience definitions for each phase, rapid iteration, and comparison across five customer types. These are study-design examples, not universal product limits.
For CPG, the decision may involve a concept, claim, or package. For software, it may involve feature bundles or onboarding. For services, it may involve packaging and buyer language. In every case, the experiment should name the action and outcome.
Start with the first live decision where customer input is missing. Use simulated evidence to narrow options, then spend human-research budget on the questions that require real-world validation, the split that matters because model outputs on choice-style tasks stay sensitive to prompting and struggle with segmentation and individual-level heterogeneity (Can large language models assist choice modelling? Insights into prompting strategies and current models capabilities, arXiv, checked 2026-07-27). See a worked example in a published case study.