Review
This is a book for people who manage product managers, which is a much narrower audience than most product books aim at and is exactly why it's useful. Almost nothing else addresses that job directly.
Wille's position is that a product leader's main output is the capability of their people, not the quality of their own product decisions, and that most people promoted into the role keep doing the previous job with a larger title. The book is essentially a manual for making the switch deliberately.
The strongest section is on assessing where someone actually is. She separates the components of the craft in enough detail that you can say something more useful than that a person is doing well, which is the thing that makes development conversations concrete rather than encouraging and vague.
The coaching material is practical, particularly on asking rather than telling, which is easy to agree with and hard to do when you can see the answer and the deadline is close. It's a workbook more than a read, with prompts and exercises throughout, and that makes it slow going front to back. Use it as a reference when you have a specific person and a specific problem.
Key Takeaways
The parts worth keeping:
Your output is their capability
- A product leader is measured by how good their people become, not by the decisions they personally make well.
- The most common failure is continuing to do the individual contributor job with more authority attached.
- Deciding for someone is faster today and costs you the same decision every week afterwards.
Assess specifically
- Break the craft into components rather than judging overall performance. It's the only way to give feedback someone can act on.
- Strength in one area often masks a gap in another, particularly when someone is confident and articulate.
- Self-assessment alongside your assessment surfaces the difference in perception, which is usually the more useful conversation.
Coaching means asking
| Instinct | Better move |
|---|---|
| Give them the answer | Ask what they have considered and why |
| Fix the artefact yourself | Show what good looks like, then let them redo it |
| Step into the meeting | Prepare them beforehand, debrief afterwards |
- Every one of these is slower once and faster permanently, which is a trade most managers make in the wrong direction under pressure.
Make the development explicit
- Growth that isn't planned doesn't happen, it just gets discussed sympathetically at review time.
- One-to-ones default to status updates unless someone deliberately protects them for development.