Startups, product and software teams

A novel in which an IT manager rescues a failing project using lessons from The Goal.

Owner-operator economics: labour efficiency and the four keys.

Fadell built the iPod, the iPhone, and Nest. Build is structured as a book of advice organized by career stage and product phase. It is unusually honest about failure, about the texture of executive dysfunction, and about what it actually takes to ship physical products at Apple-level quality. The section on storytelling for products is particularly strong.

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?

Perri names the organizational failure mode precisely: companies that measure success by shipping features rather than producing outcomes. The book is a diagnosis of product management dysfunction at the company level and a structural argument for why PM must own outcomes, not output, to function at all.

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

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.

Which metric actually governs each business-model type.

Singer's alternative to continuous sprints: fixed time, variable scope, with shaping work done in advance to reduce ambiguity before building begins. Whether or not the specific Basecamp process translates, the argument against infinite backlogs and the emphasis on appetite over estimation are worth wrestling with.

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.

Subtitled 'Building a Business When There Are No Easy Answers'

Olsen's product-market fit pyramid — target customer, underserved needs, value proposition, feature set, UX — is the clearest structural framework for thinking about fit. Where Ries describes validated learning as a philosophy, Olsen gives it a repeatable shape. Particularly strong on how to prioritize which hypotheses to test first.

Build, measure, learn: test what customers want with small experiments.

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.

Lessons from IBM's OS/360: why adding people to a late software project slows it.

Small firms fail when technicians run them; build systems that run the business.

Fourteen companies, such as Anchor Brewing and Zingerman's, that chose to stay small.

Customer development: how startups find customers before building the full product.

The Business Model Canvas: nine blocks for how a firm creates and captures value.

A step-by-step playbook for growing a small business, from Ramsey's own company.

Data on 10,000 founders: co-founders, hiring, investors, control and succession.

How leaders turn a founder-driven startup into a company that lasts.

When and how to put speed before efficiency to capture a market before rivals.

Operating manual for scaling a company from fifty to thousands

Why a business can stay small on purpose instead of chasing growth.

An operating manual for founders scaling from a few people to a few hundred.

Expanded edition of the 1992 book

An operating framework for growing firms: priorities, data and meeting rhythm.

Value pricing for solo and boutique consultancies.

A step-by-step guide to finding customers, a market and product-market fit.

Why startups should build something new and own a small market before growing.