All Tracks

AI Product Manager

Shape trustworthy AI products around real user outcomes

A product-management path for AI systems: validate a service problem, document data, model, and UX constraints, write testable requirements, establish governance, evaluate quality and harm, and make an owned launch decision.

7200 planned XP~48 hoursIntermediate–Professional

Prerequisites

  • Experience defining products, services, or operational improvements
  • Familiarity with user research, prioritization, and measurable success criteria
  • Working literacy in AI-system boundaries, data dependence, probabilistic behavior, human oversight, and failure modes; complete the mandatory prework if these are new
  • Quantitative evaluation literacy covering baselines, rates, thresholds, uncertainty, experiment comparisons, and guardrail metrics; complete the mandatory prework if needed
  • Ability to collaborate with design, data, engineering, legal, and operations stakeholders
Lab 1900 planned XP

AI Product Foundations

Understand why AI products need different product decisions, quality definitions, and user expectations.

You will learn:
  • Map the proposed product as a system of users, workflow, data, model or rules, interface, human decision, operations, feedback, and fallback
  • Write an opportunity brief with the user outcome, current baseline, product boundary, AI role, decision owner, non-AI option, assumptions, and exclusions
  • Define an initial quality frame with task, model, safety, service, adoption, cost, and harm measures plus variable-output and failure expectations
You'll build:AI product opportunity brief

Lab assessment

80% pass threshold

Frame one product opportunity without assuming AI is the answer. Use the mandatory prework concepts to make data dependence, probabilistic behavior, human authority, and failure visible.

Submission

Submit the opportunity brief, system and decision map, AI-versus-non-AI comparison, baseline evidence, initial quality frame, assumption log, and bilingual one-page summary.

Assessment rubric
Product-system model20%

The map connects user need, workflow, data, probabilistic or deterministic component, interface, human decision, operations, feedback, and fallback with clear ownership.

Opportunity and boundary evidence25%

The brief uses a sourced baseline, names a specific user outcome and owner, defines in- and out-of-scope behavior, and compares a credible non-AI option.

AI behavior accuracy20%

Data dependence, output variability, uncertainty, evaluation needs, failure modes, human authority, and update effects are stated without anthropomorphic or deterministic claims.

Initial quality and risk frame25%

Measures cover user task, model behavior, safety, service, adoption, cost, and harm, with baseline, direction, owner, and an initial stop guardrail.

Bilingual product clarity10%

Arabic and English summaries describe the same user outcome, AI role, limitations, measures, and ownership using precise product language.

Lab 2900 planned XP

User Problems and Discovery

Discover a real service problem and validate that an AI product bet is worth pursuing.

You will learn:
  • Collect approved discovery evidence from representative users, workflow observation, service data, support records, and existing alternatives
  • Synthesize jobs, friction, exceptions, unequal impacts, unmet needs, current workarounds, and evidence strength without treating feature requests as validated problems
  • Issue a continue, reframe, investigate, or stop recommendation with a testable problem statement, target users, baseline, assumptions, and next evidence question
You'll build:User problem and discovery evidence pack

Lab assessment

80% pass threshold

Use an approved course case or authorized research. Separate observed behavior, participant statements, service data, interpretation, and product assumption in the evidence pack.

Submission

Submit the research plan and safeguards, participant and source profile, anonymized notes, workflow evidence, synthesis, problem statement, opportunity and risk frame, and discovery decision.

Assessment rubric
Discovery evidence quality25%

Evidence combines suitable users, workflow and service sources, documents selection and method, and is sufficient to challenge rather than confirm the initial idea.

Problem synthesis25%

The synthesis distinguishes needs, behaviors, workarounds, causes, exceptions, segments, and feature requests, and traces each material finding to evidence.

Problem and opportunity framing20%

The problem statement names user, context, task, obstacle, consequence, baseline, and desired outcome without embedding AI or a chosen feature.

Research safety and inclusion20%

Consent or notification, data minimization, de-identification, access, retention, vulnerable participants, accessibility, and unequal impacts are addressed.

Discovery decision clarity10%

The bilingual decision states continue, reframe, investigate, or stop, with evidence strength, contradictory findings, assumptions, owner, and next question.

Lab 3900 planned XP

Data, Model, and UX Constraints

Make product decisions that respect what data and models can support and what users can safely understand.

You will learn:
  • Document data availability, provenance, quality, permission, representativeness, freshness, retention, and feedback constraints that shape the product boundary
  • Translate model capability, variability, uncertainty, latency, cost, context, language, and failure limits into supported and prohibited product behavior
  • Prototype user controls for disclosure, evidence, review, correction, override, refusal, fallback, escalation, feedback, and appeal in Arabic and English
You'll build:AI constraints and user-control design brief

Lab assessment

80% pass threshold

Complete this constraints brief before writing the PRD. Validate material constraints with data, engineering, design, operations, and risk representatives; label unverified assumptions.

Submission

Submit the data constraint inventory, model capability and failure matrix, supported and prohibited behavior table, bilingual control prototype, scenario walkthroughs, and stakeholder validation record.

Assessment rubric
Data-constraint evidence20%

The inventory traces each required input and outcome to provenance, owner, permission, quality, coverage, representativeness, freshness, retention, and unresolved gaps.

Model-boundary accuracy25%

Capabilities and limits are supported by technical evidence and cover variability, uncertainty, language, context, latency, cost, updates, and known failure patterns.

Constraint-to-product decisions25%

Each material constraint produces an explicit requirement, exclusion, fallback, dependency, test, or no-go decision rather than remaining a background note.

User control and safety20%

The prototype gives users meaningful disclosure, evidence, review, correction, override, refusal, fallback, feedback, and recourse at the right decision points.

Bilingual control parity10%

Arabic RTL and English LTR controls preserve meaning, prominence, sequence, warning strength, and access to fallback and appeal.

Lab 4900 planned XP

AI Product Requirements

Write requirements that align user outcomes, data, model behavior, quality, and human escalation.

You will learn:
  • Write outcome and workflow requirements that define users, context, task, product boundary, human decision rights, fallback, and excluded use
  • Specify testable data and model requirements for provenance, quality, permissions, input and output contracts, language, latency, cost, variability, and version change
  • Define acceptance criteria and escalation scenarios for normal, uncertain, unsupported, unsafe, inaccessible, unavailable, and contested outcomes
You'll build:AI-aware product requirements document

Lab assessment

80% pass threshold

Use the approved discovery and constraints artifacts as mandatory inputs. Every material constraint must become a requirement, test, exclusion, dependency, fallback, or explicit no-go condition.

Submission

Submit the PRD, requirement traceability matrix, data and model contracts, user and operational flows, acceptance scenario set, escalation matrix, open-decision log, and review approvals.

Assessment rubric
Outcome and scope requirements20%

The PRD defines users, service outcome, baseline, task, in- and out-of-scope behavior, human authority, fallback, success, and exclusions without solution ambiguity.

Data and model requirement precision25%

Requirements specify measurable contracts for provenance, permission, quality, timing, variability, language, performance, latency, cost, updates, and failure.

Acceptance and escalation correctness25%

Scenario-based criteria are observable and cover normal, boundary, uncertain, unsupported, unsafe, unavailable, inaccessible, appealed, and recovery states with named owners.

Traceability and feasibility20%

Each requirement traces to discovery evidence or a constraint and onward to an owner and planned verification; dependencies and unresolved decisions are visible.

Bilingual requirement consistency10%

User-facing Arabic and English requirements, examples, acceptance criteria, warnings, and escalation preserve equivalent behavior and priority.

Lab 5900 planned XP

Responsible Product Decisions

Evaluate product impact, define oversight, and make governance visible in AI product decisions.

You will learn:
  • Assess intended and foreseeable impacts by affected group, decision significance, scale, data sensitivity, autonomy, reversibility, and unequal access or error
  • Specify preventive, detective, and responsive product controls with human authority, evidence, test owner, residual risk, complaint, appeal, and incident route
  • Record an approve, approve with conditions, redesign, defer, or stop decision with rationale, dissent, prohibited use, review trigger, and accountable authority
You'll build:Responsible product decision record

Lab assessment

80% pass threshold

Complete this governance decision before evaluation planning or rollout. Use concrete product scenarios and obtain review from the named risk, legal, operations, design, data, and service representatives.

Submission

Submit the impact and affected-group assessment, scenario risk register, control map and test evidence, oversight and appeal flow, residual-risk statement, and signed product governance record.

Assessment rubric
Impact and affected-group evidence25%

The assessment covers intended benefit and foreseeable harm across representative and vulnerable groups, including access, error, exclusion, contestability, and cumulative effects.

Risk and control quality25%

Material scenarios have causes, consequences, likelihood, severity, prevention, detection, response, evidence, owner, and residual-risk assessment.

Human product oversight and recourse20%

Qualified people have timely context and authority to review, correct, override, pause, explain, handle complaints and appeals, and avoid automation bias.

Decision integrity and limits20%

The final decision follows evidence and authority, records conditions and dissent, names prohibited use and residual uncertainty, and defines review and stop triggers.

Governance transparency10%

Arabic and English decision summaries accurately communicate product purpose, AI role, human responsibility, main risks, controls, recourse, and owner.

Lab 6900 planned XP

Evaluation and Experimentation

Measure whether an AI product helps users while detecting quality, risk, and adoption regressions.

You will learn:
  • Build a product quality rubric that operationalizes task success, output correctness, groundedness where relevant, safety, fairness, latency, cost, adoption, and human effort
  • Create a representative evaluation set with labeled normal, edge, unsafe, bilingual, accessibility, refusal, fallback, and affected-group scenarios
  • Design a governed experiment with baseline, comparison, assignment or selection method, sample-size rationale, outcome and guardrail thresholds, analysis, feedback, and rollout decision rules
You'll build:Product quality rubric and experiment plan

Lab assessment

80% pass threshold

Begin from the approved responsible product decision and its controls. Do not design a rollout that bypasses a condition, prohibited use, human gate, or stop trigger in that record.

Submission

Submit the quality rubric and scoring guide, labeled evaluation set specification, baseline and targets, experiment protocol, sample-size rationale, metric dictionary, feedback plan, and rollout decision table.

Assessment rubric
Quality-rubric validity25%

Dimensions map to user, model, safety, service, cost, and human outcomes; scoring anchors are observable, non-overlapping, and reliable enough for reviewers.

Evaluation-set evidence20%

The set reflects real task frequency and material risks, covers languages and affected groups, has traceable labels, and reserves a protected final portion.

Quantitative experiment design25%

Baseline, hypothesis, unit, comparison, assignment or selection, sample size, duration, denominators, analysis, uncertainty, and missing data are technically coherent.

Governance, guardrails, and limitations20%

The plan preserves prior controls, defines harm and operational guardrails, human review, complaints, pause, rollback, stop, and limits causal and generalization claims.

Bilingual and accessibility evaluation10%

Arabic and English quality, RTL and LTR behavior, language switching, assistive use, errors, fallback, and feedback are evaluated with equivalent criteria.

Lab 7900 planned XP

Delivery, Operations, and Change

Ship AI product changes with clear ownership, operational readiness, communications, and support.

You will learn:
  • Sequence cross-functional delivery across product, design, data, engineering, assurance, legal, security, operations, support, and service ownership with explicit dependencies and decisions
  • Complete an operational readiness plan for ownership, access, support, monitoring, incidents, complaints, model or content changes, capacity, continuity, rollback, and retirement
  • Create a staged launch and change plan with audience-specific communication, training, accessible alternatives, feedback, adoption measures, release gates, and stop criteria
You'll build:AI product launch and operations plan

Lab assessment

80% pass threshold

Build the plan only from approved requirements, governance controls, and evaluation gates. Treat launch as a reversible operating change, not a feature-completion date.

Submission

Submit the integrated delivery plan, responsibility and dependency maps, readiness checklist with evidence, service and support model, launch stages and gates, runbooks, change and communication pack, and rollback exercise.

Assessment rubric
Cross-functional delivery integrity20%

Work, dependencies, decisions, evidence, owners, capacity, dates, and escalation align across functions with no hidden critical path or unowned gate.

Operational readiness evidence25%

Readiness covers people, process, technology, data, controls, support, monitoring, capacity, continuity, incidents, complaints, changes, rollback, and retirement with verifiable evidence.

Release and rollback correctness25%

Stages have entry, quality, safety, adoption, pause, stop, and rollback criteria, and the exercise demonstrates restoration of a safe service state.

Change, support, and limitations20%

The plan addresses workload, training, resistance, support, feedback, complaints, accessibility, non-digital alternatives, known limits, and accountable contacts.

Launch communication quality10%

Arabic and English materials accurately explain scope, AI role, human responsibility, data use, limitations, recourse, support, and change timing for each audience.

Lab 8900 planned XP

AI Product Capstone

Bring discovery, requirements, governance, evaluation, and launch thinking into one product recommendation.

You will learn:
  • Deliver a traceable PRD that reconciles discovery evidence, data and model constraints, user controls, governance conditions, measurable acceptance, and operating ownership
  • Produce a quality and learning plan with representative evaluations, baselines, thresholds, experiments, affected-group checks, monitoring, feedback, and decision rules
  • Issue and defend a bilingual launch, conditional launch, redesign, defer, or stop decision with evidence, residual risk, staged gates, rollback, owner, and next review
You'll build:AI product capstone: PRD, quality plan, and launch decision

Lab assessment

80% pass threshold

Reconcile all prior artifacts into one product recommendation. A launch recommendation is valid only if constraints precede requirements, governance precedes evaluation and rollout, and every open critical condition has an owner and gate.

Submission

Submit the capstone PRD and traceability matrix, product roadmap, quality and experiment plan, governance and residual-risk record, operating and launch plan, bilingual decision deck, decision log, and handover.

Assessment rubric
Product coherence and traceability25%

User outcome, evidence, constraints, requirements, controls, evaluations, operating model, roadmap, and decision align, and material claims trace in both directions.

PRD and product-method quality25%

The PRD defines a feasible bounded product with precise data, model, UX, human, operational, accessibility, and failure requirements and observable acceptance.

Quality and decision evidence25%

Representative evaluation, quantitative baselines and thresholds, experiments, guardrails, affected-group analysis, monitoring, and feedback support the stated decision without selective evidence.

Governance, delivery, and limitations15%

Human authority, controls, residual risk, complaints, appeal, operations, staged gates, pause, rollback, stop, unsupported use, and review ownership are complete.

Bilingual executive decision10%

Arabic and English materials request and justify the same decision with consistent evidence, figures, limitations, user controls, responsibility, and next action.

Target Competencies

📋 AI Product Strategy🎯 Outcome and Service Design📐 Testable AI Requirements🛡️ Responsible Launch Decisions