Getting Real: The Smarter, Faster, Easier Way to Build a Successful Web Application
37signals' original book, released free in 2006, that codified the early philosophy of the company: small teams, short cycles, simple products, no meetings, shipped software over polished presentations.
The book predates Shape Up and is less systematic, but several of its arguments were ahead of their time and became mainstream — the distinction between features and overhead, the critique of requirements documents, the emphasis on real software over mockups.
For product direction it is a short, opinionated read; much of it has been absorbed into common practice without attribution.
Use it as historical grounding for the contemporary 37signals output (Rework, Shape Up) that continues the argument in sharper form.
Central argument
37signals argues that building successful web applications requires radical reduction: fewer features, smaller teams, shorter cycles, and a relentless preference for shipped software over specifications, mockups, and process. The core thesis is that complexity is not a sign of seriousness but a source of failure — that constraints imposed by small teams and limited scope produce better products, not compromises. The book explicitly attacks the apparatus of traditional software development: requirements documents, meetings, feature requests, and the instinct to add rather than cut.
Critique
The book's central limitation is that its prescriptions are inseparable from its context: a small, bootstrapped, B2B SaaS company with a homogeneous founding team, no external stakeholders, and the luxury of treating opinionated reduction as a differentiator rather than a risk. For a CPO navigating a larger organization — with regulatory requirements, enterprise customers who contractually require documentation, or product portfolios with genuine interdependencies — the 'just ship it and ignore the rest' posture is not a strategy but an abdication. The book also conflates the discipline of scope management with a broader anti-process ideology that doesn't scale beyond the conditions that produced it.
Why it matters for product
For a product leader, the most durable argument in the book is the distinction between features as value and features as overhead — the idea that every addition to a product creates permanent maintenance, support, and cognitive cost that compounds invisibly until it dominates the roadmap. This reframes prioritization not as a question of what customers want, but as a question of what the organization can sustain, which is a more honest foundation for roadmap decisions under resource constraints. It also provides historical grounding for understanding why Shape Up's betting model and appetite-based scoping are not arbitrary — they are the systematized descendants of intuitions that 37signals had been operating on since 2006.