In search of stupidity

About the book

In Search of Stupidity is a business study of failure in the software and computer industries. Chapman builds the book around case studies of companies that lost ground through poor decisions rather than bad luck alone. The subject is technology's limits and the human and organizational choices that surround it: marketing, management, competitive positioning, and the confidence that leads firms to misread their own markets.

Chapman looks at the computer industry as a place where smart people repeatedly made avoidable errors, and he treats those errors as patterns worth naming rather than isolated accidents. Readers should expect an argument built from examples, with attention to how marketing and management decisions interact with a fast-moving technical market.

The title signals the book's tone: skeptical, sometimes blunt, and interested in the gap between what companies believed and what their customers or competitors were actually doing. The value lies in the accumulation of cases and the attempt to draw lessons from them. Chapman does not offer a single unified theory of business failure.

How to read it

Approach the book as a collection of arguments anchored in specific cases rather than as a step-by-step manual. Chapman's claims are strongest when the example is concrete and the decision chain is visible; test each lesson against what the case actually shows. Some readers will want to read the cases selectively, following the industries or companies they know, then return to the broader framing.

The prose is direct and opinionated, which makes the book accessible but also means readers should separate description from judgment. Watch for moments where hindsight shapes the verdict. The difficulty is not technical jargon but the discipline of asking whether a failure was truly avoidable or only looks that way after the fact.

Who it suits

This book suits readers interested in business history, marketing strategy, and the software industry's formative decades. Managers who want cautionary examples rather than success stories will find useful material, as will students of organizational decision-making. Readers who enjoy case-based business writing and are comfortable with a skeptical tone will get the most from it.

Reading considerations

The book's examples and framing stop well before the later shifts in the software and computer markets. Treat its lessons as historical analysis rather than current guidance. Readers should also check which edition they have, since later printings may differ in coverage or framing, and should test the author's verdicts against other accounts of the same companies.