Empowered: Ordinary People, Extraordinary Products
Source: https://www.svpg.com/books/empowered-ordinary-people-extraordinary-products/ ↗
Cagan's sequel to Inspired — where Inspired describes what strong product teams do, Empowered describes what product leadership does to produce them.
The book is organised around coaching, recruiting, product vision, and team topology, with specific attention to the leader's failure modes.
For product direction this is the more useful of the two Cagan books if you are already directing teams: Inspired is for PMs, Empowered is for heads of product.
Read alongside Skelton and Pais's Team Topologies for a complementary structural argument.
Cagan's prose is not elegant but it is clear; this book is argument rather than memoir.
Central argument
Cagan and Jones argue that the root cause of weak product outcomes is weak product leadership, not weak product managers or processes. The central thesis is that 'empowered' product teams — given real problems to solve rather than features to build — can only exist when leaders actively coach PMs, recruit for character over credentials, and translate business strategy into coherent product vision. The book inverts the usual framing: instead of asking what teams should do differently, it asks what leaders must stop doing — primarily, the proxy management and output-obsessed roadmapping that prevents genuine product thinking from taking hold.
Critique
The model Cagan prescribes assumes a degree of organizational autonomy and executive alignment that is structurally unavailable in many real contexts — large enterprises with entrenched governance, heavily regulated industries, or product functions embedded inside sales-led or engineering-led companies. The book names these environments as failure modes to escape rather than systems to operate within, which limits its prescriptive value precisely where the leadership challenge is hardest. A thoughtful reader might find the framework more useful as a diagnostic than as a roadmap, since the gap between the described ideal and most practitioners' actual constraints is treated as a character problem rather than an institutional one.
Why it matters for product
For a CPO already directing teams, the book's most actionable contribution is its taxonomy of leader failure modes — specifically the patterns by which product leaders inadvertently recreate the feature-factory dynamic they claim to oppose, through how they set context, run reviews, and define success metrics. The argument about team topology — that coaching investment must be calibrated to team scope and that product vision must be specific enough to constrain discovery — connects directly to the practical problem of why adjacent teams duplicate work or pursue contradictory bets. Read against Skelton and Pais, it supplies the human and strategic layer that Team Topologies deliberately omits.