Last reviewed

Learn Growth Product Management: From Zero to Expert

Growth product management is the craft of improving how users find value in a product, stay and pay. This path takes you from zero to job-ready in four stages, with over 100 resources, a project at each stage and lessons from people who run growth teams.

  • 132resources
  • 4stages
  • 8 to 12 monthsto job-ready
Time to job-ready8 to 12 months at 6 to 10 hours a week
DifficultyMedium to high: data, statistics and people skills
First job titleAssociate Growth PM, Growth Analyst or Product Analyst
You needBasic spreadsheet skills, curiosity about data and a free analytics account
Learn firstFunnels, activation and retention, then A/B testing
Cost to learnFree; paid courses and books are optional

What is growth product management?

Growth product management is the work of improving how people discover, start using, keep using and pay for a product. A growth product manager owns a number, such as activation or retention, and uses data, experiments and the skills of engineers, designers and analysts to move it. The aim is lasting growth that comes from the product itself, not one-off tricks.

The role sits between product, data and marketing. It differs from a core product manager, who often owns a feature area, and from a growth marketer, who works mostly on channels. Growth product managers work inside the product: onboarding, upgrade moments, notifications and the loops that bring users back or bring in new ones. This path teaches the craft step by step, from metrics to leading a team.

  1. 1MeasureTrack events, funnels and cohorts so you can see how users move.
  2. 2DiagnoseFind where users drop out and which behaviours predict they will stay.
  3. 3PrioritiseScore ideas by impact, confidence and effort and pick the next tests.
  4. 4ExperimentRun clean tests with engineers and designers and read the results with care.
  5. 5ScaleTurn wins into loops, shared practice and a team that keeps learning.

What does a growth product manager do?

What a growth product management specialist doesYour product and its users goes in. Define the metrics, Diagnose the funnel, Build the backlog, Run experiments, Touch the money moments, Share learning. Activated, retained, paying users comes out, and results feed back into the next round.DATA AND RESULTS FEED THE NEXT ROUNDYOUR PRODUCT ANDITS USERSACTIVATED,RETAINED, PAYINGUSERSGROWTHPRODUCTMANAGEMENT1Define themetrics2Diagnose thefunnel3Build thebacklog4Run experiments5Touch the moneymoments6Share learning
The work flows clockwise from 1 to 6. Each step is explained below.
  1. 1Define the metricsAgree a North Star metric and a metric tree so the team knows which numbers matter.
  2. 2Diagnose the funnelFind where new users drop out and which early actions predict retention.
  3. 3Build the backlogCollect ideas, score them and keep a ranked list of tests.
  4. 4Run experimentsWrite specs, work with engineers and read results without fooling yourself.
  5. 5Touch the money momentsShape free limits, paywalls and upgrade prompts with guardrails.
  6. 6Share learningWrite readouts and report to leaders so wins and failures both teach the team.

How to learn growth product management: a step-by-step roadmap

Work through the four stages in order. Each stage mixes videos, guides and tools, then proves the skill with a checklist and a project. The hours are a rough guide for someone starting from zero. Use the filter to show only videos, only courses or only free resources.

Learning roadmap for Growth Product Management4 stages and 132 resources from beginner to job-ready.YOUR ROADMAPGrowth Product Management4 stages, 132 resources, one project per stageBEGINNER10 TO 20Basics30 to 40 hours220 TO 50Core skills45 to 60 hours350 TO 80Practice45 to 60 hours480 TO 100Mastery40 to 55 hoursJob-ready: AssociateGrowth PM, GrowthAnalyst or Product
Your route through this learning path. Select a stage to jump to it.
Show
1

0 to 20About 30 to 40 hours

Stage 1: Growth product basics

Understand what a growth product manager does, the numbers that describe the user journey, how product data is read and why people keep using products.

What a growth product manager does

See where growth sits in a company, how the role differs from a classic product manager and what the daily work looks like.

Key concepts
  • Growth product manager
  • Product manager versus growth PM
  • Growth team mission
  • Owning a metric
  • Cross-functional squads
  • Growth hacking versus growth product work

Growth metrics and the user journey

Learn the vocabulary of growth: the stages of the user journey, a North Star metric and how a big number breaks into inputs a team can move.

Key concepts
  • AARRR pirate metrics
  • North Star metric
  • Input and output metrics
  • Metric trees
  • Leading and lagging indicators
  • Consumer and B2B benchmarks

Product analytics and SQL basics

Learn how product data is captured and read: events, funnels, cohorts and the basic SQL you need to ask your own questions.

Key concepts
  • Events and properties
  • Funnels
  • Cohorts
  • Retention curves
  • Segmentation
  • Basic SQL queries
  • Dashboards

Users, product-market fit and behaviour

Understand why people choose and keep using a product: product-market fit, the jobs users hire it for and the psychology of habits.

Key concepts
  • Product-market fit
  • The 40 percent survey
  • Jobs to be done
  • Habit loop and the Hook model
  • Fogg behaviour model
  • Motivation, ability and prompts

Check yourself: you are ready for the next stage when you can

Project

Map one product growth system

Pick a self-serve product you can use for free. Sign up and record every step to first value. Draw its user journey using the AARRR stages, choose a North Star metric and sketch a metric tree with three inputs. Say which stage looks weakest and why, using only what you can see as a user.

Deliver
A three-page note with screenshots: the journey, the North Star metric, the metric tree and your view of the weakest stage.
Done when
A reader who has never used the product can follow your note and see which metric you would try to move first and why.
2

20 to 50About 45 to 60 hours

Stage 2: Core growth skills

Diagnose activation and retention, design clean A/B tests, prioritise ideas and model how growth compounds.

Activation and onboarding

Find the early action that predicts retention, measure how many new users reach it and shorten the path to first value.

Key concepts
  • Aha moment
  • Activation event
  • Time to value
  • Onboarding flows
  • Empty states and tours
  • Activation funnel diagnosis

Retention, engagement and habits

Read retention curves, learn what keeps people coming back and see how strong products turn use into habit.

Key concepts
  • Retention curve shapes
  • Cohort retention
  • Engagement hierarchy
  • Churn and resurrection
  • Streaks and habit loops
  • Retention benchmarks

Experimentation fundamentals

Learn how a clean A/B test works: hypotheses, metrics, sample size and the statistics you need to read a result without fooling yourself.

Key concepts
  • Hypothesis
  • Control and variant
  • Primary and guardrail metrics
  • Statistical significance
  • Sample size and power
  • Minimum detectable effect
  • Randomisation

Prioritisation and the growth process

Choose what to test first, size opportunities and run a steady weekly rhythm of ideas, tests and decisions.

Key concepts
  • ICE and RICE scoring
  • Opportunity sizing
  • Experiment backlog
  • Weekly growth meeting
  • Evidence-guided decisions
  • Opportunity solution trees

Growth models, loops and unit economics

Model how users and revenue flow, replace linear funnels with loops where they fit and check that the economics work.

Key concepts
  • Growth model
  • Growth loops
  • Funnel versus loop
  • Viral coefficient
  • Lifetime value and CAC
  • Payback period

Check yourself: you are ready for the next stage when you can

Project

Diagnose a product and plan the first tests

Use a public events dataset, such as an online store log, or a demo project in a free analytics tool. Define activation, build the activation funnel and a retention table, and find the biggest drop. Write three test hypotheses, size one test, score all ideas in a backlog and draw a simple growth model or loop.

Deliver
A diagnosis memo of up to four pages with charts, a scored backlog of at least eight ideas and one test plan with a sample size.
Done when
Another growth person could run your first test from the plan without asking you a question.
3

50 to 80About 45 to 60 hours

Stage 3: Practise the work

Do the work: track clean data, run a test from brief to decision, work with engineers and designers and handle the money moments in a product.

Instrument, track and analyse

Turn product behaviour into trustworthy data: name events, track them, check quality and build the funnels and cohorts you will use in experiments.

Key concepts
  • Event taxonomy
  • Tracking plan
  • Identity and user properties
  • Data quality checks
  • Funnel and cohort builds
  • Segments and breakdowns
  • Dashboards

Run an experiment end to end

Take one idea from brief to decision: write the test plan, flag the change, run it, read the result and decide to ship, iterate or stop.

Key concepts
  • Experiment brief
  • Feature flags
  • Rollout and ramp-up
  • Sample ratio mismatch
  • Reading a result
  • Ship, iterate or stop

Work with engineering, design and data

Learn how a growth squad actually ships: specs engineers can build, designers who understand behaviour and data partners you can trust.

Key concepts
  • Growth squad roles
  • Writing experiment specs
  • Estimating effort
  • Growth engineers
  • Growth design
  • Data partnership
  • Continuous discovery

Monetisation touchpoints

Learn where growth work meets revenue: free and paid limits, paywalls, upgrade prompts and how to research price.

Key concepts
  • Free and paid limits
  • Paywalls
  • Upgrade prompts
  • Pricing research
  • Value metrics
  • Trial design

Check yourself: you are ready for the next stage when you can

Project

Run and read one experiment end to end

Choose a product or page you can change, such as a side project, a newsletter sign-up page or a demo app. Instrument the key events, define the goal, write a spec, ship one test behind a feature flag, run it to the planned sample size and write the readout. If you cannot get real traffic, run the full process on a public dataset and say clearly that it is a simulation.

Deliver
A tracking plan, an experiment spec, a readout and a short note on what you would test next.
Done when
A sceptical reviewer can see your hypothesis, sample size reasoning, result and decision, and finds no step that depends on guesswork.
4

80 to 100About 40 to 55 hours

Stage 4: Growth mastery

Set growth strategy, handle advanced experimentation, lead a team and make ethical decisions under pressure.

Growth strategy and systems

Move from single tests to a strategy: how loops, channels, product and model fit together, and when to change course.

Key concepts
  • Product, market, channel and model fit
  • Growth strategy narrative
  • Loops at scale
  • Reading growth advice critically
  • Channel and platform risk
  • What does not work

Advanced experimentation

Handle the traps that fool experienced teams: peeking, bad metrics, Simpsons paradox and weak trust in results.

Key concepts
  • Peeking and sequential testing
  • Metric pitfalls
  • Simpsons paradox
  • Novelty effects
  • Experiment platforms
  • Trust in results

Leading a growth team

Learn how growth teams are built and run: structure, hiring, rituals, goal setting and how to prove your readiness in an interview.

Key concepts
  • Team structures
  • Hiring growth roles
  • Growth reviews and rituals
  • Weekly growth reviews
  • Reporting to executives
  • Interview and portfolio readiness

Ethics, dark patterns and responsible growth

Know where persuasion becomes manipulation, how to spot deceptive design and how to build guardrails into your experiments.

Key concepts
  • Deceptive patterns
  • Consent and transparency
  • Persuasion versus manipulation
  • Legal risk (check your own country)
  • Long-term trust metrics
  • Experiment guardrails

Check yourself: you are ready for the next stage when you can

Project

90-day growth plan for a real product

Choose a real product. Using public information and a free trial, audit its activation, retention and monetisation touchpoints. Write a 90-day growth plan with a growth model, three loops or levers, a prioritised backlog of at least ten tests, the team you would need, a measurement plan with guardrails and an ethics review of each idea.

Deliver
A portfolio-grade case study of 8 to 12 pages or a slide deck, with a one-page summary for executives and a public write-up you can share.
Done when
The plan could be handed to a real team on Monday: every test has a metric, an owner and a decision rule, and the ethics review explains what you chose not to do.

Growth product management tools to learn

Is growth product management a good career?

Yes, if you enjoy mixing data, psychology, product design and people skills. Growth product skills apply wherever a product has users and a business model: software, marketplaces, consumer apps, fintech, media and AI products. The craft is also changing as teams automate analysis, so people who can judge evidence and ask good questions stay valuable.

You own a number that matters

Activation, retention and revenue are clear measures, so your impact is easy to show.

Data and creativity both count

You read cohorts and p-values, then design experiments and messages that people actually respond to.

The skills travel

Metrics, experiments and prioritisation help in any product role and in any country or industry.

You learn faster than most

Every test teaches something, so a growth team builds knowledge about users every week.

Growth product management career path and jobs

  1. Entry

    Growth Analyst or Product Analyst

    Builds funnels, cohorts and dashboards, checks data quality and supports tests.

  2. Junior

    Associate Growth Product Manager

    Writes experiment specs, runs small tests and owns a part of onboarding or retention.

  3. Mid

    Growth Product Manager

    Owns a metric such as activation, runs the backlog and works with a growth squad.

  4. Senior

    Senior Growth Product Manager

    Sets strategy for a growth area, links loops and monetisation and coaches others.

  5. Leadership

    Director or Head of Growth

    Builds teams, sets goals, reports to executives and guards the ethics of growth work.

  6. Independent

    Independent growth advisor

    Audits activation and retention for several products and runs experiment programmes for clients.

Common growth product management mistakes beginners make

MistakeChasing sign-ups instead of retained users.

Do thisTrack activation and retention first. A sign-up that never returns adds cost, not growth.

MistakeRunning tests without a hypothesis.

Do thisWrite the user problem, the change, the metric and the expected effect before you build anything.

MistakeStopping a test as soon as it looks good.

Do thisSet the sample size in advance and wait for it. Early peeking inflates false wins.

MistakeOptimising a single metric and ignoring guardrails.

Do thisAdd guardrails such as refunds, support tickets and long-term retention to every test.

MistakeCopying another product growth tactic.

Do thisCheck the idea against your own data and users. What suits one product can harm another.

MistakeUsing tricks that mislead users.

Do thisChoose honest design. Deceptive patterns may lift a number now and cost trust, refunds and legal risk later.

How to get a growth product management job

Employers hiring for a first growth role look for proof that you can read product data, find a problem and propose a sound test. A portfolio of real analysis and experiments matters more than a certificate.

Job-ready checklist

  • You can define activation and justify it with data
  • You can build a funnel and a retention curve in an analytics tool
  • You can write a hypothesis, size a test and read the result
  • You can prioritise a backlog and explain the trade-offs
  • You can write a spec an engineer can build from
  • You can explain where persuasion becomes manipulation and where you draw the line

Portfolio pieces that get interviews

  1. A funnel and retention diagnosis of a real or public product, with charts
  2. An experiment spec and readout with sample size and decision rule
  3. A scored growth backlog with a growth model or loop diagram
  4. A 90-day growth plan with an ethics review

Growth product management interview questions

How would you improve activation for a new product?

A strong answer covers: Define activation from data first, by comparing retained and churned users. Then map the funnel to that event, find the biggest drop, interview users who stalled, and test one change at a time with guardrail metrics.

A test shows a 5 percent lift after three days. What do you do?

A strong answer covers: Check the planned sample size, the sample ratio and the run length. Do not stop early. If the plan allows, wait for the full sample, check segments and guardrails, then decide and record the result.

How do you choose a North Star metric?

A strong answer covers: Pick a measure of value delivered to users that also predicts revenue, such as weekly active teams for a work tool. Break it into inputs teams can influence, and check it is not easy to game.

How would you decide between two ideas with similar scores?

A strong answer covers: Look at confidence, cost of being wrong and learning value. Prefer the cheaper test that answers a bigger question, and run a quick user check or data pull before building.

Tell me about a growth tactic you would refuse to use.

A strong answer covers: Name a deceptive pattern, such as hidden cancellation steps or fake urgency, and explain the harm. Then offer an honest alternative that tests the same goal, such as clearer value and easy cancellation.

Growth product management glossary

Growth product management
The practice of improving activation, retention and monetisation inside a product using data and experiments.
Growth product manager
A product role that owns a user metric and runs a programme of experiments to improve it.
AARRR
The pirate metrics framework: acquisition, activation, retention, referral and revenue.
North Star metric
A single measure of the value users get that also predicts business success.
Metric tree
A diagram that breaks a top metric into the inputs that drive it.
Activation
The point where a new user first experiences the core value of the product.
Aha moment
The moment a user sees why the product is useful, often linked to a specific early action.
Time to value
How long it takes a new user to reach first value.
Retention
The share of users who keep coming back over time.
Cohort
A group of users who started in the same period or share a trait, tracked together.
Churn
The share of users or customers who stop using or paying in a period.
Funnel
A series of steps toward a goal, with the share of users who complete each step.
Growth loop
A system where the output of one cycle, such as new users or content, becomes input for the next.
A/B test
An experiment that compares two versions with randomly assigned users.
Guardrail metric
A metric you protect during a test, such as refunds or support contacts.
Statistical power
The chance that a test detects a real effect of a given size.
Sample ratio mismatch
A test fault where group sizes differ from the planned split, which signals a setup problem.
ICE and RICE
Scoring methods that rank ideas by impact, confidence, ease or effort, and sometimes reach.
Paywall
A point where the product asks the user to pay or upgrade to continue.
Deceptive pattern
A design choice that tricks users into actions they did not intend, also called a dark pattern.

Growth product management FAQs

What does a growth product manager do?

A growth product manager owns a user-facing metric such as activation, retention or conversion. They study data, write hypotheses, prioritise ideas and work with engineers, designers and analysts to run experiments. They also report results and share what the team learned with the rest of the company.

Do I need to code to become a growth product manager?

Not to start. You need to read events and funnels, write clear specs and talk to engineers. Basic SQL helps a great deal and many roles expect it. Growth engineers write code, but many growth managers and analysts do not, so focus on data skills first.

How is growth product management different from growth marketing?

Growth marketers focus mostly on channels and campaigns that bring people to a product. Growth product managers work inside the product, on onboarding, retention, upgrade moments and loops. The two roles overlap and work closely, and the best teams share data and test ideas together.

How much maths and statistics do I need?

You need to understand averages, rates, p-values, power and sample size, and how to avoid common traps such as peeking. You do not need advanced theory to start. Calculators and analytics tools handle the arithmetic, but you must know what the numbers mean.

Can I learn growth product management for free?

Yes. Free analytics tools, documentation, talks and guides cover most of the craft, and this path uses them. Paid courses and books can add depth and community, but they are optional. What counts most is running real experiments and writing up what you learn.

How do I get experience without a growth job?

Use a side project, a newsletter, a volunteer product or a public dataset. Track events, find a drop, write a hypothesis and run a test or simulate one. Document the process clearly. A small real experiment with honest results impresses more than a long certificate list.