What is product management?

Key terms

Product

Something a company offers that people use or buy to get something done: an app, a website, a physical item, a service, or one feature inside a bigger product.

Product management

Deciding what a product should do and why, and organizing the work so it gets built, reaches customers, and keeps getting better.

Outcome

The change you want to see, like more shoppers finishing checkout. Compare output: the feature you shipped.

Stakeholder

Anyone with a stake in the product: leaders, sales, support, legal, finance, and others.

Roadmap

A plan of what the team intends to work on and why, in order of priority.

MVP

Minimum viable product: the version of a new product that lets a team learn the most about customers with the least effort. It’s about learning, not about being small.

The idea

Ask five people what a product manager does and you’ll get five answers. “The CEO of the product.” “The person who writes the requirements.” “The one who runs the meetings.” None of them is quite right.

So let’s build a clear answer, one piece at a time, with a source for every outside idea. You’ll see what the job is, what it isn’t, and what a product manager actually does all week. One made-up example runs through the whole lesson: a product manager at an online furniture store.

The lesson, in seven parts

1. 1What a product is, and what product management is.

   Start with the two words. A product is anything a company offers that people use or buy to get something done. An app. A website. A sofa. A bank account. Even one feature inside something bigger, like the cart on a store’s website. Management is planning and organizing work to reach a goal.

   Put them together and you get a working definition: product management is deciding what a product should do and why, then organizing the work so it gets built, reaches customers, and keeps getting better. Not once. For as long as the product is around.

   In 2011, Martin Eriksson, a co-founder of Mind the Product, described it as the place where three things meet: business, technology, and user experience. In plain words: does it work for the company, can we build it, and will people want it and be able to use it? That’s the drawing at the top of this page.

   In his words, a good product manager must be “experienced in at least one, passionate about all three, and conversant with practitioners in all.” Notice what that doesn’t say. You don’t have to be the expert in all three. You have to understand each one well enough to weigh it against the other two. Google’s Cloud team puts the job in one line: “A product manager helps teams decide what to develop and how to succeed.” Each word in that line is part of the work, as the drawing below shows.

2. 2What a product manager is responsible for.

   Here’s a more useful way to see the job. Marty Cagan of the Silicon Valley Product Group says every product idea carries four big risks, and each one has an owner:

   Risk	The question	Usually owned by
   Value	Will customers buy it, or choose to use it?	Product manager
   Usability	Can people figure out how to use it?	Product designer
   Feasibility	Can engineers build it with the time, skills, and technology they have?	Lead engineer
   Business viability	Does it work for the rest of the business: sales, legal, finance, brand?	Product manager

   From Marty Cagan, “The Four Big Risks”, SVPG. In his words, the product manager is “responsible for the value and viability risks, and overall accountable for the product’s outcomes.”

   So what does that look like in a normal week? A product manager:

   • Understands customers and the problems they face.
   • Decides what the team works on next (the roadmap), and just as important, what it doesn’t.
   • Explains the why, so the team can make good decisions without waiting for the product manager.
   • Tests ideas with the team before committing to build them.
   • Checks after launch whether the change actually helped, and adjusts.

3. 3Is a product manager the “CEO of the product”?

   Someone will tell you a product manager is “the CEO of the product”. The line is usually traced to Ben Horowitz’s well-known memo “Good Product Manager/Bad Product Manager”, which says “a good product manager is the CEO of the product.” He meant ownership: a good product manager “takes full responsibility and measures themselves in terms of the success of the product.”

   Keep the ownership. Drop the power. In most product teams, the engineers and designers you work with don’t report to you. You can’t order anyone to do anything. You lead with evidence, clear reasons, and trust. That’s why communication isn’t a side skill in this job. It’s at the center of it.

4. 4Product manager, project manager, product owner, product marketing manager.

   These four titles sound alike, and people mix them up all the time, even inside companies. The quickest way to tell them apart is the question each one owns:

   Role	Main focus	The question they own
   Product manager	The product’s outcomes for customers and the business	Are we building the right thing?
   Project manager	Delivering a defined piece of work: scope, schedule, budget	Will it be done on time, on budget, and in scope?
   Product owner	In Scrum (a common way for teams to work in short cycles), maximizing the value of the product the team builds, and managing the product backlog (the ordered list of what the team could work on)	What should the team do next, and why?
   Product marketing manager	Positioning (who it’s for and why it’s different), messaging, and launch	How do we explain it, and bring it to market?

   The product owner description follows the Scrum Guide. Titles vary by company: in many teams, the product manager also acts as the product owner.

5. 5Who a product manager works with.

   You’ll rarely build anything yourself. Your job is to get the right people, your team and your stakeholders, looking at the same problem:

   Who	What they bring
   Engineers	Build and run the product; judge what’s feasible and what it will cost
   Designers	Shape how it works and feels; test whether people can use it
   Data analysts	Measure what’s happening, and help explain why
   Marketing and sales	Bring it to customers; hear what customers ask for
   Customer support	Hear about problems first, in customers’ own words
   Legal, finance, operations	Keep it safe, legal, and affordable to run
   Leaders	Set the goals, and make the biggest calls

   Here’s what that can look like in one week at the made-up furniture store. Monday, you read customer questions with support. Tuesday, you sketch ideas with a designer. Wednesday, an engineer tells you a full 3D room planner would take months, so together you agree to test a simple doorway-size check first. Thursday, you explain to sales why the chatbot they asked for isn’t first. Friday, you check whether last month’s launch changed what customers actually did.

6. 6A product’s life, and the product manager’s job at each stage.

   Products have a life, and the job changes as they age. The classic model, which Theodore Levitt wrote about in Harvard Business Review in 1965, has four stages, today usually called introduction, growth, maturity, and decline:

   Stage	What’s happening	What the product manager focuses on
   Introduction	The product is new; few people know it	Find the customers it truly helps; fix what stops them; learn fast
   Growth	More customers arrive	Remove what slows customers down or makes them give up; scale what works; keep quality up
   Maturity	Growth slows; competitors are close	Improve and stand out; keep the customers you have
   Decline	Demand falls	Decide whether to renew it, fold it into another product, or retire it, and help customers move to something that works for them

   Inside every stage, each piece of work follows roughly the same loop. Understand the problem. Explore ideas and make a rough prototype. Test it with customers. Refine it. Build and launch it with the team. Then measure, and improve. The next lessons teach the skills you’ll use at each step of that loop.

7. 7The skills, the kinds of product roles, and the kinds of products.

   The skills follow straight from the work you’ve just seen:

   • Structured thinking: break a messy problem into parts, and take them one at a time.
   • Decision-making with trade-offs: choose within real limits of time, money, and people.
   • Customer understanding: talk to customers, read the data, find where they get stuck.
   • Communication: write and speak clearly, and always explain the why.
   • Influence without authority: get people who don’t report to you to agree on a direction.
   • Technical understanding: enough to discuss trade-offs with engineers.
   • Business sense: understand how the product makes money or saves it.

   Common kinds of product roles	What they focus on
   Core or feature product manager	A product area or part of the customer journey
   Growth product manager	Experiments that help more people find, start using, and stay with the product
   Technical or platform product manager	Tools and services other teams build on, like APIs (the connections other software uses to talk to a product) and internal platforms
   Data or AI product manager	Products built on data or machine-learning models, where quality has to be measured and checked

   Titles and scopes differ a lot between companies. Product marketing and product operations are related roles that work closely with product managers.

   You’ll also meet very different kinds of products: software sold to other businesses (B2B, short for business to business), often delivered online as a subscription (SaaS, software as a service), consumer apps, marketplaces that connect buyers and sellers, platforms other developers build on, physical and connected devices, AI products, and internal tools for a company’s own staff. The customer changes. How you learn from them changes. The job underneath stays the same.

With AI: AI is changing the tools of this job fast. You can draft a document, sort a thousand customer comments, or build a working prototype in a fraction of the time it used to take. It doesn’t change the hard part: deciding what’s worth building, and why. As building gets cheaper, choosing well matters even more.

PRODUCT:

Who it's for:
The problem it solves for them:
Life-cycle stage (introduction, growth, maturity, decline), and why:

THE FOUR BIG RISKS: what's still uncertain?
  Value (will they buy or use it?):
  Usability (can they figure it out?):
  Feasibility (can we build it?):
  Business viability (does it work for the business?):

WHO I'D WORK WITH, AND WHAT EACH BRINGS:

HOW WE'D KNOW IT'S WORKING (an outcome, not a feature):

Ask AI about this lesson

All lessons