AI PM Ready

AI opportunity spotting

The first PM skill in any AI initiative: telling a real opportunity from hype. Interviewers test whether you evaluate before you build.

Four conditions for AI readiness

"Add AI to it" is not a strategy. Every AI opportunity must pass these conditions before it becomes a product requirement. All four must be met — not three.

1.Learnable pattern exists

The task has a repeatable structure that historical data can encode. Ask: "If I showed 10,000 examples to a smart person, could they learn to do this consistently?"

Real example — condition met

Stripe fraud detection: historical transaction patterns are learnable — velocity, merchant category, geolocation, device fingerprint. 15 years of transaction data gives 99M+ labeled examples.

Common failure — condition not met

"Make our search smarter" — no learnable pattern because success is undefined. What does "smarter" mean in data terms? Until that is answered, no model can be trained.

2.Labeled data exists or is feasible

For supervised learning you need correct-answer examples. Labeling cost is the most underestimated variable in AI project planning — most estimates are off by 3–5x.

Real example — condition met

GitHub Copilot training data: millions of public code repositories with implicit labels (code that runs vs. code with errors). No manual labeling required — the feedback loop is built in.

Common failure — condition not met

A legal contract summary tool: 500 historical contracts exist, but they were summarized by 8 different lawyers with different styles. Labels are noisy and inconsistent — model trained on this data learns inconsistency.

3.Human baseline is beatable and known

Measure the human baseline first. AI must beat it meaningfully — not by 2% in perfect test conditions. If you do not know the baseline, you cannot evaluate whether AI is ready.

Real example — condition met

Google's speech recognition: human transcription accuracy is 95% at the word level. Google Speech-to-Text reached 95.1% in 2017 — that is the moment it became a deployable product, not before.

Common failure — condition not met

A PM pitching an AI resume screener without knowing how accurately human recruiters currently make decisions. If the baseline is 72% quality-of-hire, AI needs to beat 72% — not just exceed random.

4.Production feedback loop exists

Without a mechanism for real-world feedback to flow back into evaluation and retraining, the model silently degrades. Design for the flywheel from day 1.

Real example — condition met

Gmail Smart Reply: user sends or dismisses suggestions — both signals feed the training pipeline. The model improves every day without additional labeling cost.

Common failure — condition not met

A batch-report AI that generates weekly business summaries. Users read the reports but never indicate which parts were useful vs. wrong. No feedback signal — model cannot improve.

The 10x test

Will AI make this 10x better — in speed, scale, or accuracy — or 10% better with 10x the risk? A good AI opportunity has asymmetric upside: the AI does the task at a scale or speed humans structurally cannot match.

10x case
  • Personalisation at scale (50M users)
  • Real-time fraud detection (10ms decision)
  • Document extraction (10,000/day)
  • Anomaly detection in telemetry streams
10% case — solve differently
  • Meeting summaries (2 min vs 5 min)
  • Drafting emails (saves 3 min/email)
  • Improving search by 2% on CTR
  • Dashboard reports nobody reads
Was this page useful?