Concept
Constraints as an advantage
Constraints as an advantage is Rework's argument that less money, fewer people and less time are not obstacles to route around but forces that push a founder toward the essential thing, which is the only thing customers pay for.
Fried and Hansson built Basecamp without venture capital and turned that fact into a philosophy. Their observation is that abundance produces waste: a team with money hires before it needs to, builds features nobody asked for, and plans for a scale that never comes, because nothing forces it to choose. A constrained team has to choose, and choosing is where the product gets good. Their related heresy is that planning is guessing: a long-term plan is written by people who do not yet have the information, and calling it a plan makes it hard to abandon when the information arrives. So they advise working with what you have, deciding for now rather than forever, and treating the lack of resources as an editor that cuts everything that does not matter. The founder who complains about constraints is usually describing the thing that will save them.
A real-life example
A two-person team in Gaziantep making software for small textile workshops could not afford a salesperson, so the founders installed the software themselves, on site, in each workshop. The constraint forced them to watch the software being used badly, and the twenty things they fixed as a result were the difference between a demo and a product. Competitors with sales teams had never watched a single installation.
How to use it
- 1List what you lack, money, people, time, and next to each write what the lack forces you to cut or do yourself; that column is your advantage.
- 2Decide for the next few weeks, not the next few years, and write plans as guesses you expect to replace.
- 3When tempted to raise or hire your way around a constraint, first ask what the constraint is trying to teach you.