Product Manager
A product manager (PM) is the person responsible for deciding what a product team should build and why, so that the result is valuable to customers and works for the business. Product managers combine knowledge of customers, data, the business and the market to set direction, prioritize work and guide the team toward outcomes, not just shipped features.
What a Product Manager Does
Marty Cagan of Silicon Valley Product Group (SVPG) describes the product manager as explicitly responsible for ensuring both value and viability: customers must want the product, and it must work for the business. To do that, he argues, a PM needs deep knowledge of four areas: users and customers, data, the business, and the industry.
The day-to-day work spans several activities:
- Running product discovery with design and engineering to test ideas before building them.
- Connecting work to the product strategy and business goals.
- Prioritizing problems and maintaining a product roadmap.
- Writing or shaping requirements so the team understands the problem and the expected result.
- Measuring whether shipped work changed customer behavior or business results.
- Explaining decisions to stakeholders, executives and customers.
PMs work in close partnership with designers and engineers, who bring expertise in usability and technical feasibility.
Why the Role Matters
Teams always have more ideas and requests than capacity. Someone has to decide which problems are worth solving, and that person needs both customer and business context. Without a PM, priorities tend to follow whoever is loudest, the largest customer, or the most recent request.
The role is demanding because PMs are measured on results they do not fully control. Cagan compares it to a CEO, with the obvious difference that nobody reports to the product manager. Influence comes from evidence and trust rather than authority. Strong PMs replace opinion with evidence at every decision. For more on that, read about turning discovery evidence into strategic product choices.
Product Manager Example
A PM at a business invoicing company receives repeated requests from sales for custom invoice templates. Before agreeing, she checks the data and finds that almost no customers who left mentioned templates. Interviews show the real pain is late payment. The team builds automatic payment reminders instead and tracks the average number of days until an invoice is paid.
Product Manager vs. Product Owner
The two titles are often mixed up.
| Product manager | Product owner | |
|---|---|---|
| Origin | A job title used across the industry | An accountability defined in the Scrum Guide |
| Main focus | Customer value, business viability, strategy and discovery | Maximizing the value the Scrum team delivers through the Product Backlog |
| Typical scope | Market, customers, roadmap and outcomes | Product goal, backlog ordering and clarity |
The Scrum Guide does not mention product managers at all. In many companies one person holds both: the PM fills the product owner accountability on a Scrum team. Cagan argues that splitting the work between two people usually weakens the product, because neither ends up with the full picture of customers and technology.