Product Management and Design

Krug's web usability primer has stayed relevant for over two decades because its core argument — that good interfaces require no instruction — is timeless. The chapters on navigation conventions and usability testing with five users are still the most practical introduction to the discipline.

The Google Ventures five-day workshop format distilled into a repeatable method for answering critical design questions through rapid prototyping and targeted user testing. Less a design book than a process book — most valuable for teams that struggle to move from ideas to validated decisions quickly.

The foundational text of the modern PM role. Cagan's central argument — that most companies build the wrong things because they treat product as a delivery function rather than a discovery function — reframes everything that follows. The chapter on product discovery versus product delivery is worth the price of the book.

A four-step model for habit-forming products: trigger, action, reward, investment.

Short, sharp, and corrective. Fitzpatrick diagnoses why customer interviews so often produce false positives: people are polite and will validate almost any idea you present with sufficient enthusiasm. The fix is asking about past behavior, not hypothetical futures. A genuinely useful retraining of interview instincts.

Where most design books stay in the abstract, this one opens with specific visual decisions: spacing scales, type hierarchies, color palette construction, shadow systems. Written by developers who taught themselves visual design, it's unusually practical and works equally well for product designers who want stronger visual intuition.

Torres operationalizes what Cagan describes. Weekly customer touchpoints, opportunity-solution trees, assumption testing — this is the most practical account of how discovery actually becomes a habit rather than a quarterly exercise. Pairs directly with Inspired as the how to its what.

Cagan's follow-on to Inspired shifts from product craft to organizational conditions. The argument: you cannot have great products without empowered product teams, and empowered teams require managers who coach toward outcomes rather than manage toward outputs. Addresses the question Inspired leaves open — what do you change first?

The book that introduced affordances, signifiers, and feedback loops to a generation of designers. Norman's analysis of why doors, phones, and stoves confuse people is the clearest argument that bad design is a systems failure, not user error. Everything else on this list builds on this vocabulary.