AI PM Ready

Responsible AI

AI PMs are the last line of defence before a harmful or biased AI product reaches users. This isn't a compliance checkbox — it's a core product design discipline.

Six pillars — what a PM owns

Each pillar is a PM responsibility, not an engineering one. Click to see what you ship, what goes wrong, and your PM action.

PM Owns

Define the bias metric (demographic parity, equalized odds, or calibration), the threshold that blocks launch, the test population, and the sign-off owner — in the PRD before model training begins.

Real Example That Went Wrong

Amazon recruiting tool (2018): trained on historical hire decisions. Label = "did this person get hired" — which encoded a decade of biased hiring. Model systematically downgraded resumes mentioning "women's." Scrapped after 2 years.

PM Action

Audit the training label definition, not just the model output. Biased label = biased model regardless of algorithm. The PM should reject a biased label at PRD review, before training begins.

Human oversight patterns

Human-in-the-Loop

HITL

Human approves every model output before it takes effect.

When to use

High-stakes, irreversible decisions. Highest cost and latency.

Example

Loan approval: AI recommends, human approves before offer is sent.

Human-on-the-Loop

HOTL

Model acts autonomously. Human monitors and can intervene.

When to use

Medium-stakes, reversible decisions. Balances speed with oversight.

Example

Content moderation: AI removes, human can reinstate on appeal.

Human-out-of-the-Loop

Full Auto

Fully automated. Audit trail exists but no human reviews individual decisions.

When to use

Low-stakes, high-volume, reversible. Requires drift monitoring and alerts.

Example

Spam filtering: no human reviews individual spam classifications.

What a PM commissions — not builds

Model Cards

Standardised internal documentation for every production model. PM defines it as a launch gate — the model doesn't ship without one.

What goes in it

  • Training data provenance and quality criteria
  • Eval results broken down by demographic subgroup
  • Known limitations and out-of-scope uses
  • Intended use cases and foreseeable misuse risks

Red Teaming

Adversarial testing by a team separate from the builders. PM defines the threat model — the red team operationalises it.

PM delivers

  • Threat model: adversary, goal, blast radius
  • Top 3 threat priorities to scope the exercise
  • Severity thresholds: ship blocker vs. log-and-monitor
  • Findings enter regression eval set — not just fixed once
Responsible AI is not a separate workstream — it's embedded in every story. Every AI feature PRD needs: a bias metric with threshold, an explainability requirement or explicit waiver, a human review gate definition, and a data handling note. These are Definition of Done items, not compliance reviews.

Key Takeaways

Audit the label, not just the model

Biased training labels produce biased models regardless of algorithm. This is the PM's gate to catch at PRD review — before training begins.

Choose your fairness metric before building

Demographic parity and equalized odds conflict mathematically. The PM picks one based on use case before engineering starts — not after the model is trained.

Oversight pattern is a PM decision

HITL vs. HOTL vs. fully automated is a product design choice with cost, latency, and liability implications. It belongs in the PRD, not a post-launch config.

Transparency = product feature, not legal note

In-product AI disclosure is a legal requirement and a trust lever. It's copy and placement specced in the PRD — not a sentence buried in T&Cs.

Was this page useful?