📦Product Management
Deciding what to build and why · 25 terms
Product Management
4The job of deciding what a product does, the person who does it, and the document that hands a decision to the builders.
Deciding what a product should do and why. Then checking that it worked.
The person who decides what a product team builds next, and why.
A written plan of what a new feature must do, and why.
One way someone uses a product to reach a goal. It is written as steps.
Product Strategy
3Where a product is going, how it plans to win, and the stages its sales pass through.
The future a product wants to make, said in one or two lines.
The plan for how a product will reach its vision and win.
A product's sales path in four steps: start, growth, peak and fall.
Product Roadmap
4The shared plan of what comes now and later, and the ways of writing one.
A shared picture of what the team will work on, and roughly when.
A roadmap with three columns: now, next and later. No dates.
A roadmap that lists results to reach, not features to build.
A roadmap that lists features to ship, often with dates.
Product Discovery
5Learning what users need and testing ideas cheaply, before anything is built.
Find out what to build, and test ideas, before you build them.
People buy a product to get a job done. Study the job, not the product.
A need in one line: when this happens, I want this, so I can do that.
A tree that links one goal to user needs, ideas and tests.
What users tell you about your product, in their own words.
Feature Prioritization
5Choosing what to build first, the scoring methods behind the choice, and what happens when nobody says no.
Deciding which ideas to build first, and which to drop.
Rank ideas by reach, impact and how sure you are. Then divide by effort.
Some features are a must. Some get better the more you add. Some are a nice surprise.
A user asks for a thing your product cannot do yet.
A product that gets so many features it gets worse to use.
Product Analytics
4Measuring what users do inside a product: who uses which feature, and how often they come back.
What people really do in your product, click by click.
How many users try a new feature and come back to it.
How many people use your product on one day.
How many people use your product at least once a month.