Product management sits at the intersection of business, technology, and user experience. Marty Cagan's framing: a PM is responsible for discovering a product that is valuable, usable, feasible, and viable — the PM owns the "why" and "what"; engineering owns the "how"; design owns the experience. The job runs on two tracks. Discovery means talking to users every week to find problems worth solving. Delivery means writing specs, working with engineering and design, and handling trade-offs at launch. Strategy turns the vision into a roadmap that communicates direction. Prioritization is mostly deciding what not to build. PMs carry responsibility without authority, so they lead through influence.
What a PM actually does
- Discovery — talking to users, running interviews and tests to find problems worth solving (Teresa Torres' continuous discovery: weekly touchpoints with users).
- Delivery — writing specs/PRDs, working with engineering and design through build and launch, handling trade-offs.
- Strategy — owning the product vision (where the product is going) and translating it into a roadmap, which is a communication artifact of strategy, not a fixed feature list.
- Prioritization — deciding what NOT to build; sequencing work against goals and constraints.
- Stakeholder alignment — keeping leadership, sales, marketing, support, and engineering pointed at the same outcomes.
- Metrics — defining success measures and being accountable for outcomes, not output (shipping features is output; moving a metric is outcome).
Prioritization frameworks
- RICE — (Reach × Impact × Confidence) / Effort; good for expected-value ranking.
- ICE — Impact × Confidence × Ease; a lighter version for faster scoring.
- Kano — classifies features as basic, performance, or delighter; useful for customer satisfaction trade-offs.
- Jobs-to-be-Done (JTBD) — frame demand around the "job" a user hires the product for, not personas or features.
- Opportunity Solution Trees (Teresa Torres) — map business outcome → opportunities → solutions → experiments, keeping discovery tied to a measurable outcome.
PM vs related roles
| Role | Owns | Analogy (Evelyn Hartz) |
|---|---|---|
| Product Manager | What gets built and why: vision, strategy, roadmap, discovery | The cereal is ON the shelf |
| Product Marketing Manager (PMM) | Go-to-market: positioning, messaging, launch, sales enablement | The cereal is OFF the shelf |
| Product Owner | Scrum-team-level backlog executor; in many orgs the same person as PM with a narrower scope | — |
| Growth PM | Short-horizon experiments on a business metric anywhere in the funnel | See Growth Management |
Brett Byron's analogy: PM and PMM are driver and navigator — PM drives product direction, PMM navigates positioning and messaging; neither works without the other.
A common myth: "PM is the CEO of the product." Cagan and others push back — PMs have responsibility without authority and must lead through influence.
Career ladder (typical big-tech shape)
- APM — executes scoped features with guidance.
- PM — owns a product area end to end.
- Senior PM — owns a complex area, mentors, handles ambiguity.
- Principal / Group PM — owns a product group or leads PMs on one large surface.
- Director → VP → CPO — owns a portfolio, org design, and the connection between product strategy and company strategy.
How the job changes by company stage
- Startup (pre-PMF) — everything is discovery; PM wears GTM, support, and analytics hats.
- Scale-up — process, prioritization, and stakeholder management dominate; roadmaps matter.
- Big tech — deep specialization (platform PM, growth PM, API PM), heavy cross-functional coordination.
Key reading
- Marty Cagan — Inspired, Empowered (SVPG).
- Lenny Rachitsky's newsletter and podcast (lennysnewsletter.com).
- Teresa Torres — Continuous Discovery Habits.
- Reforge — growth and product strategy programs.
See also: Growth Management
Sources: SVPG — Product Manager vs Product Owner, Ant Murphy — PM vs PMM vs Growth PM, Lenny's Newsletter, Product Plan — What is Product Management. Verified 2026-10-29.