Product Management Basics
Level 1 Β· The job
What product management is, and what a product manager owns. The job is to pick problems, not to run a long list of features.
Course contentsLesson 1 of 13
Level 1 Β· The job
Level 2 Β· Where the product is going
Level 3 Β· Finding the right problem
Level 4 Β· Choosing what goes first
Level 5 Β· Shipping and measuring
After this lesson you can
- Say what a product manager decides
- Tell a product manager from a project lead
- Explain why most ideas get a no
10 mincovers 3 glossary entries
What a product manager actually decides
Product management is the job of deciding what a product should do next, and why. A product manager talks to users, reads the numbers and weighs up ideas. Then they pick the few worth building. A team might hold 50 ideas and have room for 4 this quarter. Choosing those 4 is the job.
The product manager owns the why. Designers own how it looks and works. Engineers own how it is built. None of them report to the product manager in most firms. So the job runs on reasons and evidence, not on rank. A product manager who gives orders soon finds that nobody follows them.
The work runs in two loops side by side. The first loop finds out what to build: talk to users, test an idea cheaply, decide. The second loop builds it: build, release, measure. A product manager spends most of their week in the first loop, so the second loop builds things worth building.
People often mix this job up with a project manager. A project manager makes sure a piece of work lands on time and on budget. A product manager decides which work is worth doing in the first place. A project ends when it is delivered. A product goes on for years, and so does the job.
Most of the job is saying no. Every idea sounds good on its own. A sales team wants one feature for a big client. A boss wants another. Users ask for a third. Saying yes to all of them makes a product slow and confusing, so the product manager picks the one that solves the biggest problem.
The result is what counts, not the output. Shipping ten features in a quarter means the team was busy. It does not mean anyone was helped. A product manager is judged by what changed for users and for the business: more people using the product, fewer leaving, more paying.
This course stops at the product decision. How the team then plans its weeks and ships in short rounds is a subject of its own. So is marketing a launch to buyers, with its message and its press. Both sit right next to this job, and a product manager works closely with the people who do each one.
Worked example
Emma says no to a big client
Emma is the product manager for a booking app. A client worth 8% of revenue asks for a custom report. The same week, data shows 30% of new users quit at the payment screen.
Fixing payment touches every new user. The report touches one client. Emma puts payment first and offers the client a plain export in the meantime.
The words for this lesson3
Check yourself
What does a product manager own on a product team?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.