Basecamp's Shape Up ships work in six-week cycles — appetites, not estimates

Basecamp's product team grew from three people to about a dozen while rebuilding Basecamp 2, and the off-the-shelf two-week sprint process left designers and programmers feeling like ticket takers on projects that never felt done. Ryan Singer ran paid workshops to find the words for what already worked intuitively, then wrote it down as a book.

Fix the appetite, vary the scope: shape a project's boundaries first, bet six uninterrupted weeks on it, and when time runs out cut scope — never extend the deadline.

Work is shaped first: a rough outline with boundaries, at the right level of abstraction, priced by an 'appetite' for how much time it is worth. Leadership then bets on it like a gambler — one small team, six weeks, uninterrupted. A circuit breaker caps the downside: if the work is not done at six weeks, the project is questioned hard and scope is hammered down to what matters.

Basecamp shipped Basecamp 3 and years of features on six-week cycles with cool-downs between. The free book made the method a reference point: by 2019–2020, Singer was advising large organizations with hundreds of developers adopting Shape Up, and its vocabulary — appetites, circuit breakers, scopes — spread across product teams.

Basecamp's complaint with Agile was practical, not ideological. Two-week sprints were too short to build and ship anything meaningful, and the habit of shredding a project into sprint-sized tasks made the people doing the work feel like ticket takers: 'imagined tasks' from planning never matched the 'discovered tasks' of real work, so projects slipped from sprint to sprint on a treadmill.

The alternative, written down by head of strategy Ryan Singer in the 2019 book Shape Up, has three parts. Shaping defines the project before anyone commits: the boundaries, the rough outline at the right level of abstraction, and an 'appetite' — how much time this is worth, rather than an estimate of how long it will take. Betting is leadership choosing which shaped projects to fund. Building gives one small team six uninterrupted weeks to own the whole project.

The mechanism that makes it work is the circuit breaker: at the end of six weeks, if the project is not done, it is questioned hard and scope is cut — the deadline never slips. 'Fix time, vary scope' replaces 'fix scope, vary time,' and the two-week sprint's constant start-stop overhead disappears. Between cycles there is a cool-down, a period for fixing bugs and reducing the backlog that sprints never allowed.

The method was not born in a meeting. Singer had prototyped the techniques in 2009 on a project called 37 ID and tested them again on the 2012 Basecamp 2 redesign, then ran paid workshops to see what teams actually struggled with — wireframes that were too finished, designers given no room, programmers reduced to 'code monkeys.' The book grew out of those workshops, and Basecamp published it free online.

Shaping removes risk before the bet: boundaries and an appetite set guardrails, so the team is free to solve the problem its own way.

Six weeks is long enough to build and ship something meaningful, unlike a two-week sprint that starts and stops every Friday.

The circuit breaker fixes time and varies scope, so the deadline never slips and the team feels the satisfaction of shipping.

Assigning the whole project instead of shredded tasks restores ownership — no more ticket-taking code monkeys.

Writing it as a free book let other teams adopt and adapt the language, which is why the method outlived a single company.

Boundaries make teams braver: a fixed appetite and a circuit breaker turn projects into bets with capped downside, so a team can own the work and ship — instead of grinding through a backlog.

Shape Up spread through the free book, Singer's workshops and speaking, and became a standard point of comparison to Scrum in product-development writing. Basecamp kept working in six-week cycles into the 2020s, and teams far outside software adopted appetites and circuit breakers.