Phase 0: AI Product Management Foundations · 40 min · Feasibility/Desirability/Viability Triage · Python

When AI Is (and Isn't) the Right Solution

If the correct answer is a single fixed value derivable from a rule, you don't need a model — you need an if-statement.

Hiring signal: Deciding whether a feature should even use AI — versus a lookup table, a rules engine, or a simple heuristic — is one of the most common product-sense questions in an AI PM interview loop. Interviewers use it to separate candidates who reflexively reach for a model from ones who can reason about determinism, error tolerance, and cost, because that judgment call is exactly what separates a PM who ships reliable products from one who ships expensive demos.

What you will learn

Distinguish deterministic problems (fixed, rule-derivable answers) from probabilistic problems (pattern-matching over ambiguous or high-dimensional input)
Apply a feasibility/desirability/viability triage to decide whether a proposed feature is actually a good fit for AI
Identify concrete signals that a problem should be solved with a lookup table, rules engine, or heuristic instead of a model
Identify concrete signals that a problem's input space or judgment requirement genuinely calls for AI
Explain the real cost — engineering time, reliability, maintenance, user trust — of defaulting to AI on a deterministic problem

The Problem

A checkout team is asked to fix a recurring support complaint: customers are confused about why their shipping cost changes at checkout. Someone on the team proposes "let's train a model to predict shipping cost from the cart and address, so we can show an estimate earlier in the flow." It sounds reasonable in the meeting. It's also completely wrong, because shipping cost here isn't a prediction problem — it's a lookup. Weight, dimensions, destination zone, and carrier rate card are all known, and the exact cost is a deterministic function of those inputs. There is one correct number, and the business already has the formula.

The team builds the model anyway. Three sprints go into collecting training data (LTV of building a dataset from historical checkouts, most of which reflect a rate card that's since changed), tuning a gradient-boosted regressor, and standing up an inference endpoint. It ships. It's right most of the time and wrong in a way nobody can predict — off by $4 on international orders, off by $0.50 on some domestic ones, no clean pattern to the errors because the true relationship was never fuzzy in the first place; the model is just approximating an equation that already existed. Support tickets about shipping cost don't go down, they change shape: now customers see a number, get charged a different number, and conclude the site is buggy or dishonest. Engineering now maintains a model that has to be retrained every time the carrier changes rates, monitored for drift that shouldn't exist, and explained to a confused customer by a support rep who has no idea why the "estimate" was wrong. A fifteen-line function reading from the existing rate table would have been correct 100% of the time, shipped in a day, and never needed retraining.

This mistake is common because "use AI" has become a reflex rather than a decision. The fix isn't a rule against using AI — it's a habit of asking, before any design work starts, whether the problem is actually the kind of problem AI is good at.

Deterministic vs. Probabilistic Problems

The question underneath every "should this be AI" decision is whether the problem has a single correct answer that's derivable from known rules, or whether it requires pattern-matching over input that's ambiguous, high-dimensional, or genuinely disputed even among humans.

Deterministic problems have a fixed, knowable answer for a given input. "What's the sales tax for this ZIP code" has exactly one correct answer, and it's a lookup against a published rate table — not a pattern to be learned. Billing calculations, tax tables, unit conversions, eligibility rules with clear cutoffs (age >= 18), and inventory counts are all deterministic. If you can write the correct logic as an if/else chain or a table lookup, and two engineers implementing it independently would produce identical outputs, it's deterministic.

Probabilistic problems don't have one clean rule. "Is this support ticket urgent" depends on tone, context, implicit signals, and judgment that reasonable humans would disagree on — there's no lookup table for "urgent," because urgency isn't a fact about the ticket, it's an inference from ambiguous evidence. Fraud likelihood, image content, sentiment, "does this resume match the role" — all probabilistic. The input is unstructured or high-dimensional (free text, images, audio, behavioral sequences), and no finite set of hand-written rules covers it well.

AI earns its cost on probabilistic problems, where a rules engine would either be impossibly large or perpetually incomplete. On deterministic problems, AI adds three costs without adding value: it's less accurate than the rule it's approximating, it's opaque (nobody can point to why it gave a specific answer), and it's more expensive to build, run, and maintain than the logic it replaces.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers The Feasibility / Desirability / Viability Triage, Reading the Signals, Build It, What to Practice — plus a hands-on lab, quiz, and project artifact.

Create a free account to unlock Phase 0 and Phase 1 of every course — no credit card.