The Product Manager's Four Areas of Homework
The four knowledge domains a PM must own because nobody else on the team can bring them
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 95%
Cagan defines the PM's contribution to an empowered team not as a set of ceremonies but as a set of knowledge the designer and engineers cannot supply: users and customers, product data, the business, and the industry. A PM who lacks these has nothing to bring to solution discovery, which Cagan names as the single biggest cause of empowered-team failure. The homework is finite — typically two to three months of deliberate work.
Origin
Marty Cagan / SVPG, taught since his own transition from engineer to PM; the '30 customers before you decide anything' rule came from the manager who coached him.
Core principles
- 01Your value to the team is knowledge the team doesn't otherwise have.
- 02You are never as close to the customer as you think, even if you are the customer.
- 03Business knowledge is the hardest area and the one stakeholders judge you on.
- 04Homework earns you the right to make decisions — it is not a nice-to-have.
How to run it
- 1
Become an expert on users and customers
Get in front of real users and customers at volume until you are regarded as one of the company's experts on them. Cagan's own coach set a hard bar: no decisions for the team until 30 customer visits were complete.
Pro tip Set an explicit, countable target (Cagan's coach used 30, split across two geographies) rather than 'talk to more users'.
Watch out Being a former user of the product you build is not the same as knowing your customers — Cagan believed he knew developers because he had been one, and was wrong.
- 2
Become an expert on the data
Know how the product is actually used and how that has changed over time: user analytics, sales analytics, usage patterns. This is another way of knowing the customer, but through behaviour rather than conversation.
Watch out Don't outsource this to a product-ops analyst who filters the data and tells you what they think you should hear.
- 3
Become an expert on the business
Learn how the product is marketed, sold, paid for, and monetised, plus every compliance, regulatory, privacy, and security constraint. Then convince each stakeholder that you understand their issues and that you'll bring them a prototype to check whenever there's doubt.
Pro tip Explicitly promise stakeholders a prototype review whenever their constraint is in play — that promise is what buys you the trust to run without them in the room.
Watch out This is the hardest of the four and the one stakeholders will judge you on; underinvesting here is why stakeholders reclaim decision rights.
- 4
Become an expert on the industry
Know the competitive landscape, the industry, and the trends. Cagan considers this the fun one and suggests following credible industry people.
In the wild
When Cagan moved from engineering to product management, his coach ruled he could make no decisions for the team until he had visited 30 customers — 15 in the US, 15 in Europe — and arranged a three-week trip to make it happen. Cagan protested that as a developer building developer products he already knew the customer; the coach replied that this is never true.
→ Cagan completed the visits and now teaches customer expertise as the first homework area, treating self-assessed customer knowledge as unreliable.
A PM who has learned the compliance, privacy, and security constraints goes to those stakeholders, demonstrates they understand what to look for, and commits to bringing a prototype whenever a question arises.
→ Stakeholders grant the team latitude to discover solutions instead of pre-specifying them, because they trust the PM will surface anything that touches their area.
Common mistakes
Assuming you know your customer because you are one
Cagan's coach: 'all i know for sure is that's never true.' Being a member of the user population produces confident, unrepresentative intuitions and skips the very research that would correct them.
Treating homework as optional prep rather than the job
The designer and engineers cannot bring this knowledge. A PM without it contributes nothing to solution discovery, which is why Cagan calls an ill-equipped PM the single biggest reason empowered teams fail.
Is it for you?
Best for
A new or self-taught PM — especially one promoted from engineering, design, or a product-owner role — who wants a concrete curriculum for becoming credible to their team and stakeholders
Not ideal for
A PM whose organisation blocks direct access to customers or stakeholders — that access has to be won first
From the transcript
“the first thing that product manager needs to do is get themselves prepared to contribute to their team the way they need to in general…”
“the person coaching me said explicitly that i was not allowed to make any decisions for the team until after i visited 30 customers his…”
“the second thing is they have to be an expert in the data how is your product used how is that change over time what's…”
“the third thing is and this is usually the hardest one and it's the one that your stakeholders will judge you on is you have…”
“the fourth area is you have to know the competitive landscape you have to know the industry you have to know the trends”
“that is the single biggest area empowered teams fall down the product manager is ill-equipped”
From the episode
The nature of product
Marty Cagan, Silicon Valley Product Group