loading...
Some businesses sell software or services. Others sell the experience of being a customer of this particular company. The latter category is smaller, harder to copy, and significantly more valuable.
The authors of this book are the founders of Basecamp.
## Notes
We build and evolve products. More precisely, our company builds and evolves products – and the company itself is something we also build and evolve. For the company to produce great products, it has to become our best product. You could even version it: at the time of writing, the authors considered themselves to be at Basecamp version 50.3.
Basecamp does not run on long-term plans. The planning horizon is six weeks, and nothing beyond that. If something built under that plan turns out not to be what people needed, the loss is six weeks – far better than making a wrong call for an entire year and only finding out afterward.
All work within that six-week window is distributed to three-person teams. Three is deliberately odd – there is no tie vote. Three people are enough to make a real breakthrough but not enough to break what already works. A team of three does not need a dedicated manager. And three people will not inflate a well-scoped problem the way five or ten people tend to.
Deadlines never move. What can move is the scope – the list of things that need to be done by that deadline. Critically, that scoping decision belongs to the team doing the work, not to management. This forces every team member to stay genuinely engaged with the question of what matters for the product and what does not, and to develop a sharper intuition for it over time.
The principle cuts in both directions: never compress the deadline, and never add scope at the last minute. Either move destroys quality and generates the kind of sustained tension that makes teams worse at their jobs.
Basecamp accepts imperfection as a permanent operating condition. Features ship well before they are perfect. Bugs get patched rather than root-caused. This sounds alarming, but the alternative – doing one thing to 100% quality – means doing only one thing. With many priorities in parallel, the real choice is between doing everything at 20% (mediocre across the board) and doing the most important thing at 80% while patching the rest at 5%. The latter is the honest trade-off.
Knowing where to accept imperfection and where not to requires judgment about what actually matters. That judgment is the core product skill.
## Summary
Treating the company itself as a product is a powerful idea. The most interesting effect is that it forces you to think about whether a given change represents a minor version increment – a refinement of the current state – or a major version bump: a genuine upgrade to how the organization works.
Twenty years without a long-term plan is harder to absorb. Though it is fair to say that level of operational calm may require more practice to reach.
The approach is nonetheless essential as a working methodology for early-stage companies. Long-term startup plans are, almost by definition, fiction. Steve Blank's definition of a startup is an organization searching for a repeatable and scalable business model. The initial idea is a starting hypothesis, not a roadmap, and it rarely survives contact with actual customers. Turning that hypothesis into a multi-year plan means following a dead star – and the only question is whether the money or the enthusiasm runs out first.
## About the Book
### It Doesn't Have to Be Crazy at Work
- Author: Jason Fried, David Heinemeier Hansson
- Published: 2018