How do you decide whether a problem is a good fit for AI?
AI product management · Intermediate 1
Short answer
Start from the user problem, not the technology. A good fit is a task that is frequent and valuable, tolerates some errors or lets a person check the output, has data or examples to learn from, and is hard to solve with simple rules. If a rule, a better form or a search box solves it, do that instead.
Deeper answer
Ask: what does a wrong answer cost, and who catches it? Drafting a reply that an agent edits tolerates errors; approving a loan does not. Check feasibility with a quick prototype on real examples before committing a roadmap.
Also weigh the four classic product risks: value, usability, feasibility and viability. AI adds a fifth in practice: trust, meaning whether users will rely on output that is sometimes wrong.
What a strong answer covers
- Starts from the user problem
- Frequent and valuable task
- Tolerates errors or has human checking
- Has data or examples
- Simpler non-AI solutions first; prototype to test
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- What would make you say no to an AI feature request?
- How would you test feasibility in a week?
Common mistakes
- Starting from 'we need AI'
- Ignoring the cost of wrong answers
Learn it
- Should we build our own AI feature or buy a vendor product?
- What does a good data strategy for an AI product look like?
- Your AI feature launched, usage is high, but customer satisfaction dropped. What do you do?
- How would you measure the success of an AI feature?
- How do you design a product experience when the AI is sometimes wrong?
- You launched an AI tool internally and nobody uses it. What do you do?
- As a PM, how do you work with engineers on evals?
- How would you price an AI feature whose cost grows with usage?
- When should a product keep a human in the loop?