Open this lesson in your favourite AI. It'll walk you through the why, explain the demo, and quiz you on the try-it list.
Three titles people confuse. Product Manager, Product Owner, Program Manager — different jobs, different scope, often coexist on same team. Conflating them muddies expectations + ownership.
Disambiguating the three.
Use these three in order. Each builds on the one before.
Explain in one paragraph the difference between PM, PO, and Program Manager.
Walk me through when a company needs each role.
Given a Series B SaaS where one 'PM' is doing all three jobs, what's the right next hire?
PRODUCT MANAGER (PM):
Owns: what to build + why.
Time horizon: weeks to quarters.
Tools: customer research, strategy, PRDs, metrics.
Reports to: VP/CPO or founder.
PRODUCT OWNER (PO):
Scrum-specific role.
Owns: backlog for ONE scrum team.
Time horizon: sprint to sprint.
Tools: user stories, sprint planning, acceptance criteria.
Reports to: usually PM or eng manager.
In smaller companies: PM and PO are the same person.
In larger companies: PO is more tactical, PM is more strategic.
PROGRAM MANAGER:
Owns: cross-team coordination + execution.
Time horizon: project lifecycle.
Tools: schedules, dependencies, status reports, risk registers.
Reports to: VP Engineering or PMO.
Different from PM: doesn't decide what to build. Coordinates how.
WHEN EACH IS NEEDED:
Just PM:
Small startup. PM does it all.
PM + PO:
Mid-size. PM thinks strategy + market; PO runs sprint mechanics.
PM + PgM:
Multi-team initiatives. PgM handles cross-team execution.
PM stays product-strategic.
PM + PO + PgM:
Large enterprise. Each role has clear lane.
CONFUSION SIGNS:
- PM running standups + writing acceptance criteria (PO work).
- PM tracking Gantt charts + cross-team dependencies (PgM work).
- PM has no time for customer interviews or strategy. (Drift.)
THE FIX:
- If you're a PM doing PO work all day: ask for a PO.
- If you're a PM doing PgM work: ask for a PgM.
- If neither: time-box those activities to <20% of the week.
OPENPED / RUNCOACH STAFFING:
Early-stage (10 people): 1 PM does all three roles.
Series A (30 people): PM + part-time PgM for hardware coordination.
Series B+ (60 people): PM + PO + PgM clearly split.
PM JOB:
Know which role you're playing.
Communicate role boundaries to stakeholders.
Don't drift toward whatever's missing.