Review
LeMay's book is the one I'd hand to someone who has just become a product manager and is quietly panicking, because it's honest about how much of the job is unglamorous communication work.
The framing I liked is that product management is a connective role rather than a decisive one. The skills that matter are the ones nobody puts on a job description: writing clearly, asking obvious questions in rooms where everyone is pretending to understand, and being willing to look uninformed in order to get to a shared answer.
His treatment of process is refreshingly unideological. Rather than advocating a framework, he argues that any framework will be adapted beyond recognition by the organisation using it, and that the interesting question is what your team's adaptation reveals about its real constraints. That matches everything I've seen and almost nothing I've read.
The caveat is that the honesty cuts both ways. It's very good on what the job feels like and lighter on the technical craft of the work, discovery, prioritisation, measurement. Pair it with something more methodical. On its own it will make you feel understood without making you more effective.
Key Takeaways
The parts worth keeping:
The job is connective, not decisive
- The core skills are communication, organisation and research, not vision or invention. Job descriptions describe the second set and the work is the first.
- The role has responsibility without authority by design, so every mechanism you have is a soft one.
- Being the person willing to ask the obvious question is a bigger contribution than it looks, because everyone else is also unsure and less willing to say so.
Clarity beats cleverness
- Ambiguity is comfortable in the moment and expensive later. Most of a product manager's value is converting vague agreement into something specific enough to disagree with.
- Write things down. Verbal alignment evaporates and reconstructs itself differently in each person's memory.
- If a document needs you present to be understood, it hasn't done its job.
Frameworks get adapted, always
- No process survives contact with a real organisation intact. Insisting on orthodoxy wastes effort that should go into the work.
- Where your team bends the process tells you where its real constraints are. That is diagnostic information, not a compliance failure.
- Pick the lightest process that addresses your actual problem, and expect to change it.
Seniority does not remove the discomfort
- The uncertainty does not resolve with experience. You get better at working inside it, which is a different thing from it going away.
- Much of the anxiety of the role comes from being accountable for outcomes produced by people who do not report to you, and no amount of process removes that.