The Manager's Path
Source: https://www.oreilly.com/library/view/the-managers-path/9781491973882/ ↗
The standard book for the individual contributor-to-manager transition in technology companies, structured as a progression from mentoring an intern through managing a team, managing managers, and eventually running an engineering organisation.
Fournier, who was CTO of Rent the Runway, writes from direct experience and avoids the abstract leadership platitudes that plague most management books.
The chapter on managing managers is particularly valuable because it addresses a transition that most engineering organisations handle badly — the moment when your job stops being about technical decisions and becomes about building the system that makes good technical decisions possible.
It has become the de facto onboarding text for new engineering managers across the industry.
Central argument
Fournier argues that engineering management is not a single role but a sequence of distinct jobs, each requiring a fundamentally different operating model. The book's core thesis is that failure at each transition — from individual contributor to manager, from manager to manager-of-managers, from director to executive — stems not from incompetence but from applying the mental model of the previous role to the new one. A senior engineer who becomes a manager still optimizing for personal technical output will fail; a manager-of-managers who keeps solving their teams' technical problems instead of building decision-making systems will fail for the same structural reason at a higher level.
Critique
The book is grounded almost entirely in the context of well-resourced, venture-backed technology companies with substantial engineering headcount — Fournier's frame of reference is Rent the Runway-scale organizations, not the majority of product teams where management layers are thin, roles bleed into each other, and the clean progression she describes rarely exists. This creates a structural blind spot: the advice on managing managers or running an engineering organization presupposes organizational conditions that many readers will never work in, and the book offers little guidance for the more common situation of managing up, sideways, or in resource-constrained environments where formal authority is weak.
Why it matters for product
For a CPO, the book's most operationally useful argument is that the manager-of-managers transition — the point at which you stop making decisions and start designing the system that produces decisions — is precisely the transition that governs whether product and engineering can scale together or will fracture under growth. A CPO who has not made this shift will become the bottleneck in discovery and prioritization, personally arbitrating trade-offs that should be resolved by well-designed team structures, clear product principles, and delegated authority. Fournier's framework for what 'good technical judgment at scale' looks like gives product leaders a concrete vocabulary for evaluating whether their engineering counterparts are operating at the right level — which directly affects delivery predictability and strategic alignment.