📎 Webclip
Constraints only work if they hurt
The post says Basecamp uses six-week budgets for most major product work, not as deadlines but as a way to keep scope flexible and quality high. The budget pushes the team to write less software and make trade-offs instead of drifting into late, bloated work.
It also says good constraints hurt when they work. Features and settings that seem important often get cut, but the discipline of shipping on a budget has proved worth the sacrifice. Basecamp has changed cycle lengths at times, but the author presents budgeted shipping as a key reason a small team can release so much for so long.
Reading notes#
- Basecamp uses six-week budgets for most major product work.
- The constraint is meant to be a budget, not a deadline.
- Budgets keep quality high while making scope variable.
- The team tries to write less software, with fewer features and fewer settings.
- A limited time frame makes trade-offs explicit instead of leaving work in the realm of “we really ought to.”
- Good constraints hurt because they force the team to cut features and settings they think matter.
- The author says those cuts often prove right after the fact.
- The habit of shipping every six weeks is presented as worth the sacrifice.
- Basecamp has used other intervals before, including two-month cycles and 8-week summer cycles.
- The post treats shipping on a budget, rather than on a deadline or “when it’s done,” as a key part of how Basecamp has shipped so much with a small team.
