Major·Fluent

№ 20 · 8 modules × roughly 3 hours

Product Management

Decide what to build and why — discover real problems, prioritize ruthlessly, and ship outcomes, not features.

In 24 hours you will become conversant in Product Management's vocabulary, mental models, discovery and prioritization frameworks, methods, canonical cases, and live debates—enough to think like a PM, critique a roadmap, write a sharp product brief, and judge whether the craft fits you, without pretending to confer a PM role, a universal playbook, or the judgment that only ships with real reps.

Time
8 modules × roughly 3 hours
Difficulty
Introductory but serious
Adjacent fields
Business Administration · Marketing · Data Science · Communications · Computer Science · Design / UX

Contents

8 modules · ~3h each · ~24h total
01
Field Orientation

Establish what product management actually is — owning problems and outcomes, not features — and calibrate what fluency in this field gives you versus what only shipping real product can teach.

02
Vocabulary Immersion

Build the shared operating language of product management so every term you encounter — and every conversation you enter — becomes a precise instrument for better decisions rather than a source of fog.

03
Mental Models

Build the thinking reflexes a PM runs continuously — problem love, outcome orientation, cheap risk reduction, ruthless prioritization, and evidence-first user empathy — so judgment arrives in the moment, not after the meeting.

04
Frameworks and Theories

Teach product managers to use canonical frameworks as decision-organizing lenses — not formulas — so they can reason clearly about trade-offs without being seduced by framework theater.

05
Methods and Tools

Equip learners to recognize and apply the core methods PMs use to gather real evidence, run valid experiments, read analytics honestly, and translate findings into roadmaps and specs — while staying clear-eyed about the gap between knowing a method and having built genuine product judgment.

06
Canonical Cases and Debates

Develop field judgment by reading the real stories — pivots, flops, and live disagreements — that define how product actually works, while guarding against survivorship bias and context-blindness.

07
Applied Project Studio

Produce a one-page Product Opportunity Brief that forces you to articulate a specific user, an evidenced problem, a testable solution hypothesis, a cheap validation experiment, an outcome metric, and explicit non-goals — treating the whole artifact as a thinking exercise to stress-test, not a plan to execute blindly.

08
Synthesis and Fit

Integrate the field's core reflexes into a coherent personal framework, honestly assess your own fit and Dunning-Kruger risk, understand where AI helps and fails, and leave with a concrete 30-day plan — whether you pursue the title or simply carry the thinking.

After this sprint, you can…

Fluency, not mastery
  • Use Product Management's core vocabulary without bluffing.
  • Recognize the field’s major debates and the tradeoffs behind them.
  • Ask sharper questions of practitioners, books, courses, and AI tools.
  • Read entry-level sources with enough context to judge them.
  • Spot common beginner overclaims — including ones an AI might make.
  • Decide whether deeper study, expert help, or formal training is worth it.

Canonical frameworks

  • Continuous discovery and dual-track agile (discovery alongside delivery)
  • Jobs to be Done (the demand-side, progress-focused lens)
  • RICE prioritization (Reach, Impact, Confidence, Effort)
  • Build-Measure-Learn and the MVP (Lean Startup)
  • AARRR pirate metrics (acquisition, activation, retention, referral, revenue)
  • North Star metric plus input metrics
  • Objectives and Key Results (OKRs)
  • The Kano model of feature satisfaction

Live debates

  • Empowered outcome teams vs the feature factory
    It determines whether PMs actually decide what to build or merely manage a backlog handed down to them, and whether teams are measured by value created or features shipped — a choice that reshapes the whole role.
  • Data-driven vs vision-led product decisions
    Over-indexing on data produces timid local optimization and misses breakthroughs, while ignoring data produces confident, expensive failures; knowing when each applies is core product judgment.
  • 'PM as CEO of the product' — useful myth or harmful misconception?
    How a PM understands their power shapes every interaction with their team; the CEO framing can inspire ownership or poison collaboration, and most product failures are failures of influence, not of authority.
  • Roadmaps as commitments vs roadmaps as evolving bets
    Roadmap philosophy decides whether a team can adapt to what it learns or is locked into yesterday's plan, and whether trust with stakeholders is built on honest direction or broken date promises.
  • Agile discipline vs agile dogma
    Teams routinely adopt agile's rituals while missing its purpose — fast feedback and adaptation — so the debate separates genuinely iterative teams from those performing agility while still shipping the wrong things.

Source trail

7 notes
  1. Marty Cagan, Inspired, and Empowered (SVPG) — empowered product teams, discovery, and the role of the PM.
  2. Teresa Torres, Continuous Discovery Habits — opportunity solution trees and ongoing user contact.
  3. Melissa Perri, Escaping the Build Trap — outcomes over outputs and the product operating model.
  4. Eric Ries, The Lean Startup, and Dan Olsen, The Lean Product Playbook — build-measure-learn, MVPs, product-market fit.
  5. Clayton Christensen et al., Competing Against Luck — jobs to be done as the demand-side lens.
  6. Rob Fitzpatrick, The Mom Test, and Steve Blank, The Four Steps to the Epiphany — customer development and honest research.
  7. Public university and Reforge/SVPG intro product syllabi for canonical cases, metrics, and ethics topics.

Watch the field

3 curated videos · included

This field includes a curated shelf of 3 hand-picked free explainer videos — vetted from trusted educators and embedded so you can watch them in context, without falling down the YouTube rabbit hole. A small bonus on top of the eight-module sprint; it unlocks with the field.

Ask better questions of AI

Fluency is leverage

Fluency in Product Management makes AI far more useful: you know what to ask, you can judge the answer, and you know when to check a primary source or a practitioner instead. Once you've done this sprint, prompts like these get real work done — using the field's own frameworks and debates:

  • I'm new to Product Management. Define <term> the way a practitioner would, give one realistic example, and flag where beginners misuse it.
  • Apply Continuous discovery and dual-track agile (discovery alongside delivery) to <my situation> and show your reasoning — then list what could make this analysis wrong.
  • Lay out both sides of: Empowered outcome teams vs the feature factory Give the strongest evidence for each, and say where practitioners still disagree.
  • Critique my plan using Jobs to be Done (the demand-side, progress-focused lens). What assumptions would a Product Management practitioner question?
  • What primary sources or practitioners should I check before trusting your answer on <topic> in Product Management?

Expert · AI · Source. Use AI to orient and draft, primary sources to verify claims that matter, and a practitioner when judgment, liability, or nuance is on the line. Fluency is what lets you tell which is which.

What this sprint does not do

This is field fluency, not mastery — and not credit, licensure, or professional authority. It does not qualify you to practice Product Management where supervision, certification, or a license is required. It gives you the operating language and judgment to learn faster, ask better questions, work with AI and experts, and decide your next move.