The Four Types of Product Work
Feature, growth, PMF-expansion, and scaling work — the portfolio a product leader must learn to balance.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
Fareed and Casey Winters map product work into four categories: feature work, growth work, product-market-fit expansion, and scaling work. Most PMs become expert in one; the leap to product leadership is owning a balanced portfolio across all four without over-applying the lens you know best. The framework's value isn't in labeling work but in forcing leaders to allocate across types they've never personally done.
Origin
Developed by Fareed Mosavat with Casey Winters; part of Reforge's product strategy program (Fareed credits much of it to Casey).
Core principles
- 01A framework's usefulness is in guiding portfolio allocation, not in categorizing for its own sake.
- 02Every leadership scope contains some mix of all four types of work.
- 03The biggest risk is a specialist turning every problem into their favorite type (e.g. a growth leader treating everything as an experiment).
- 04You must build enough baseline understanding of each type to lead work you can't do yourself well.
How to run it
- 1
Feature work
Add new features and product experiences to drive engagement with your existing customer base and solve a wider range of their problems.
- 2
Growth work
Help existing or broader customers connect with experiences you already have, driving top-line growth or monetization or whatever the key metric is.
- 3
Product-market-fit expansion
Attract whole new sub-segments — either the same product to a new audience (internationalization, a new vertical) or a different product to the same audience (bundling, adding new tools to a suite).
Pro tip Distinguish this from feature work: it's about reaching new market segments, not deepening use for current ones.
- 4
Scaling work
Handle the new problems created because you're growing — technical scaling plus 'user scaling' like trust and safety (e.g. problems that appear when Airbnb goes from 10 hosts to 10,000).
Pro tip Include trust, safety, and other user-scaling problems here, not just technical debt.
Watch out This category is 'always forgotten' by PMs who reduce scaling to pure technical work.
In the wild
Fareed uses Airbnb going from 10 hosts to 10,000 hosts, and volume-driven problems at Twitter and Facebook, to illustrate scaling work — problems that exist purely as a function of growth rather than new features.
→ Illustrates why scaling work is a distinct category a leader must resource, separate from feature or growth work.
Common mistakes
Over-applying your specialist lens
A growth leader who makes everything an experiment to be measured mis-serves feature, PMF-expansion, and scaling work, which don't all respond to the same playbook.
Forgetting scaling (especially user scaling)
PMs routinely omit the fourth category or shrink it to technical debt, ignoring trust, safety, and other problems that arise simply because the product is growing.
Is it for you?
Best for
Product leaders taking on a broad portfolio who need to allocate attention across unfamiliar types of work.
Not ideal for
An IC focused on executing a single well-defined project who doesn't yet own a portfolio.
From the transcript
“Casey Winters and I worked on this framework together a lot of it comes from him”
“first feature work adding new features product experiences Etc”
“we want to attract whole new sub-segments of markets to the product by adding something”
“the fourth that is always forgotten by a lot of PMS which is so what is the stuff we're doing that is because we are…”
From the episode
How to build trust and grow as a product leader
Fareed Mosavat (Reforge, Slack, Instacart, Zynga, Pixar)