Basecamp’s historical Shape Up account describes a coordination problem: practices understood by an experienced core became harder to communicate as the organisation grew. Its response combined advance project definition, recurring development periods and explicit limits on investment. This case concerns that documented period, not confirmation of Basecamp’s current practices. [1] [2]
Situation and challenge
Basecamp reports growing from four people to more than fifty. By 2015, its product team had quadrupled and worked remotely. Explaining established working habits to newcomers had become difficult. The company describes needing a more explicit vocabulary and structure rather than relying on shared experience. [1]
What the organisation changed
Basecamp describes adopting six-week development periods and formalising project proposals and selection. A small senior group prepared prospective work alongside delivery teams, specifying a solution’s essential elements while leaving implementation decisions open. [1]
Basecamp calls its chosen investment limit an appetite: a budget selected before designing a solution, rather than a forecast derived from an existing design. Its account describes one- or two-week projects and six-week projects for a designer with one or two programmers. Oversized proposals were narrowed or divided into meaningful portions. During preparation and delivery, scope could change to respect the time boundary. [2]
Reported results and limits
Basecamp reports favourable experiences with earlier techniques in 2009 and 2012. Those retrospective outcomes are qualitative; the supplied material establishes no quantified productivity improvement. Both sources are first-party accounts, not independent corroboration. [1] [2]
Basecamp also describes investigating a permissions request and identifying an archive warning as a narrower response. The account contrasts a one-day change with a possible six-week project; it does not establish measured savings from a controlled comparison. [2]
What smaller businesses can learn
Our analysis: the transferable distinction is between deciding how much a problem deserves and predicting how long a proposed solution will take. A small business can ask the first question before commissioning detailed plans. That does not make the second question unnecessary. A budget expresses a preference; feasibility still needs examination. If the minimum useful result cannot fit, the sensible response may be to defer the work rather than disguise an unrealistic commitment.
Our analysis: clearer boundaries can serve as a handover between an owner and the people doing the work. The boundary should explain the problem, the intended benefit and what can be omitted. Otherwise, permission to adjust scope may become ambiguity about expectations. This is an interpretation of the process, not an independently demonstrated effect at Basecamp.
Transfer limit: a very small business may have nobody available to prepare future projects while others deliver. Its staff may also juggle customer support and operational emergencies. Copying the six-week duration or staffing pattern would therefore be a weak starting point. Work with mandatory requirements or indivisible dependencies offers less freedom to reduce scope.
Takeaways to try
Suggested application: choose one discretionary internal improvement. Write a short brief identifying the problem, an affordable time allowance, the smallest useful outcome and explicit exclusions. Ask whoever will deliver it to identify uncertainties before you commit. Keep required quality and safety checks separate from optional additions, so reducing scope does not mean accepting an unusable result.
Suggested review: record the original boundary, subsequent scope decisions and whether the result addressed the stated problem. Note interruptions and unresolved work as well as completion. Use that record to adjust your next project allowance. Treat this as a local learning exercise, not a promised productivity gain or a test Basecamp is documented to have run.
Sources
Independent analysis prepared with AI assistance from the linked public company accounts, checked on 2026-09-21. Company-reported outcomes are not independently verified. Takeaways are our interpretation, not claims of affiliation or first-hand research.