Executive Summary
AI product discovery starts before AI
Successful AI products begin with understanding customer behavior, business outcomes, and measurable problems, not selecting a model. Customer Discovery protects teams from building impressive technology around weak demand. The system clarifies what users do today, why the current workflow fails, which outcome matters to the business, and whether AI is actually the right tool. Only after that evidence is visible should a team decide whether to prototype, automate, augment, or avoid AI entirely.
The Decision System
A repeatable path from problem to decision
Customer Problem
Name the real problem in the customer's language before naming a solution.
Current Behaviour
Observe what users do today, including workarounds, delays, and repeated handoffs.
Root Cause
Separate symptoms from the constraint that makes the problem persist.
Business Opportunity
Connect the customer problem to revenue, risk, adoption, retention, or operating leverage.
AI Suitability
Evaluate whether AI meaningfully improves judgment, automation, personalization, or speed.
Success Criteria
Define what must change in customer behavior and business outcomes.
Decision
Choose the smallest evidence-backed path: build, test, defer, or reject.
Decision Questions
Prompts for evidence-backed discovery
Common Mistakes
Where discovery loses decision quality
Starting with the model
Model choice is premature until the customer behavior, data quality, and success criteria are clear.
Confusing requests with needs
A requested feature may be only the customer's best guess at a deeper workflow constraint.
Ignoring business outcomes
Discovery becomes weak when it validates user interest without proving why the business should act.
Using AI unnecessarily
AI adds cost and trust risk when the problem is better solved through clearer workflows or simpler automation.
Framework in Practice
Two implementation examples
JoVE
Workflow adoption
Discovery reframed adoption from a content volume problem into a workflow-fit problem.
Open Decision JournalComviva
Payment reliability
Reliability work started with customer trust, transaction failure patterns, and business risk.
Open Decision JournalDecision Checkpoint
The question before solution design
If AI disappeared tomorrow, would this still be an important customer problem?
Key Takeaways
What this system should reinforce
Strong discovery starts with behavior, not stated preference.
Business outcomes make customer problems worth prioritizing.
AI suitability should be evaluated after the root cause is understood.
The best decision system makes trade-offs visible before build work starts.
Success criteria must describe measurable customer and business change.
Operating Principle
The principle behind the system
Start with the customer.
Let evidence determine whether AI belongs in the solution.
Continue from here
Explore the complete AI Product Operating System
Executive Brief
Start with the fastest overview of Product OS, evidence, and business impact.
OpenDecision Operating System
Return to the completed AI Product Operating System v1.
OpenRecruiter Tour
Follow the fastest guided path for hiring teams.
OpenAI Product Principles
Review the philosophy behind the decision systems.
OpenContinue Learning
Validation & Experimentation
The next Decision System will define how to validate the smallest useful version of a product decision before scaling the solution.
Next Decision System