Key Insights: Rework: Change the Way You Work Forever
Jason Fried and David Heinemeier Hansson built 37signals into a profitable software company without outside investors, a sales team, or a large staff. *Rework* is the operating manual behind that choice: a short set of refusals aimed at habits borrowed from companies far bigger than yours.
5 Pillars of Success
1. Planning is guessing, so decide just in time
A long-range plan describes a future nobody has seen, and its real cost is loyalty: once the plan exists, people defend it instead of reading what is happening. The substitute is just-in-time decision-making. Decide what you can decide now, from what you can observe, and leave the rest open until it matters.
The mechanism is shrinking the unit of commitment: work cut into pieces short enough that being wrong stays cheap. Fried and Hansson built Basecamp and 37signals' other products this way, without a multi-year master plan.
2. Protect attention, and treat meetings as a last resort
The book counts work in concentration, not hours. An hour-long meeting with eight people does not cost an hour; it costs eight person-hours plus the fragments of focus lost on either side. Interruptions carry the same surcharge: regaining a deep working state takes far longer than the interruption.
The fix is structural. Replace recurring status meetings with written updates people read on their own schedule, and keep whatever meetings remain small, short, and tied to one problem. The same reasoning covers workaholism: exhausted people make worse decisions and turn staying late into visible proof of commitment, so if cuts are needed the workaholics should go first.
3. Build half a product, not a half-assed product
Every feature costs attention, maintenance, and clarity forever, so the default answer to a request is no. Curation, not accumulation, is the core product skill.
The mechanism is a fixed order of cuts. Find the epicenter: the one thing that makes the product valuable, done before anything adjacent. When something is not working, resist the instinct to add; the correct move is usually to remove. Then ship: a first version that is not slightly embarrassing probably arrived too late.
37signals kept Basecamp deliberately narrow instead of matching competitors feature for feature, and when the framework behind it proved useful on its own, they released Ruby on Rails publicly. A by-product became a product and a reputation.
4. Out-teach instead of out-spend
Marketing is not a department. It is everything the company does: the support reply, the error message, the pricing page, how the product behaves when it breaks.
The mechanism is teaching in public. Emulate chefs rather than line cooks: chefs share technique openly and gain reputation from it, while line cooks guard their tricks and stay interchangeable. Specific, honest communication compounds; hiding imperfections makes a company read as manufactured.
The 37signals blog and books built an audience that made conventional advertising unnecessary. An audience you own survives a platform changing its rules; followers on someone else's network do not.
5. Fund yourself, and treat small as a destination
Outside money is not free. It buys speed and imposes an exit-shaped objective, pushing the company toward the scale its investors need rather than the scale its customers justify. The default is funding the business from revenue, which forces cost discipline early and keeps the roadmap tied to what customers will pay for.
The mechanism is a distinction the book draws sharply: start a business, not a startup. A startup is a temporary organization whose product is the search for a business model; a business makes money. Building to flip is building to flop: a company designed for sale makes the short-term decisions that hollow it out.
37signals is the case in point: profitable, independent, and willing to decline growth it did not want. Independence is what lets a company serve its customers rather than its investors.
Key Takeaway
"Build half a product, not a half-assed product."
Practical Task
1. **Audit one inherited rule.** Name a process you follow only because that is how it is done. Write down the company size it was designed for and delete it if that was far larger than yours. 2. **Convert one status meeting into a written update.** Participants post what they did, what is blocked, and what they need. Keep the meeting only if the writing exposes a decision. 3. **Cap the meetings that survive.** Fewer than six people, under thirty minutes, one problem on the agenda, and a required decision or artifact at the end. 4. **Protect one uninterrupted block per day.** Two to four hours with notifications off, treated as the day's primary output, not the time left over. 5. **Before adding a feature, name what it replaces.** If you cannot say what it removes in complexity or attention, it is not ready to build. 6. **Publish one thing you know.** A post or a public explanation of a customer problem you solved. Teaching is cheaper than advertising and it compounds.