6 min
FOUNDATIONS · LESSON 01.03beginner

PM vs PdM vs Scrum Master vs TPM.

Four roles that share a syllable and almost nothing else.

↳ tl;dr

Project Manager owns the delivery. Product Manager owns the why. Scrum Master owns the process. Technical Program Manager owns coordination across deeply technical, multi-team systems. They're paid for different decisions, judged on different metrics, and often coexist on the same team.

Project Manager (PM)

The on-time / on-budget / on-scope owner. Cares about the schedule, the budget, the risk register, and stakeholder communication. Strongest where the work is well-defined and the constraints are tight (construction, regulated rollouts, large physical projects). Cert ladder: CAPM → PMP → PgMP → PfMP.

Product Manager (PdM)

The why-and-what owner. Cares about the customer problem, the roadmap, the metric that proves the work mattered, and the launch. Strongest where the right thing to build isn't obvious (consumer software, B2B SaaS). The PdM doesn't typically own a ship date the way a PM does — they own whether the right thing shipped.

Scrum Master (SM)

A facilitator-coach. Cares about the team's health, the ceremonies (standup, planning, retro), and removing blockers. The Scrum Guide is explicit that the Scrum Master is a servant-leader — they don't direct the team's work, they protect the team's ability to direct its own work. Cert ladder: CSM / PSM I → A-CSM / PSM II → CSP-SM / PSM III.

Technical Program Manager (TPM)

A program manager with deep technical literacy — common at large tech companies (Google, Meta, Amazon). Coordinates initiatives that span multiple engineering teams, often deep in architecture conversations. TPMs read RFCs, push back on technical trade-offs, and translate between engineering reality and product/business asks.

in the wild

The fastest way to spot which role someone is: ask what they're measured on this quarter. PM: schedule, budget, milestones. PdM: a product / business metric. SM: team velocity, ceremony health, blocker resolution time. TPM: cross-team delivery + technical health (incident rate, deprecation cadence).
RoleOwnsLoses sleep overCommon sectors
PMdeliveryschedule slip, budget, scope creepconstruction, healthcare, finance, defense
PdMthe right thingwrong thing built, missed markettech, B2B SaaS, consumer software
SMteam's processstuck team, broken ceremoniestech, agile transformations, large IT
TPMtechnical coordinationcross-team blockers, architecture trade-offsFAANG, large platform companies

They overlap. That's normal.

On a healthy team you'll often see two of these roles coexist (e.g. a PdM and an SM, or a TPM and a PM). The mistake is conflating them. A PdM running standups instead of the SM means the PdM isn't doing discovery. A PM acting as the SM means the team is being directed, not facilitated.

// practice this

Pick a role in the simulator

When you start a chapter, you choose a role track (PM / PdM / SM). The decisions and metrics shift accordingly — the same scenario plays differently for each.

// sources

Sources cited

  1. [01]
    What is Project Management?

    PMI · retrieved 2026-04

  2. [02]
    The Scrum Guide (2020 revision)

    Sutherland, J. & Schwaber, K. · Scrum.org / Scrum Alliance · 2020 · retrieved 2026-04

    The canonical Scrum definition. ~13 pages — short and dense.

  3. [03]
  4. [04]
    What is a Technical Program Manager?

    ServiceNow · retrieved 2026-04

// sources

Further reading

  1. [01]
    The Scrum Guide (2020 revision)

    Sutherland, J. & Schwaber, K. · Scrum.org / Scrum Alliance · 2020 · retrieved 2026-04

    The canonical Scrum definition. ~13 pages — short and dense.

  2. [02]