Basecamp's alternative to sprints and backlogs: six-week cycles, fixed time and variable scope, with a built-in 'appetite' that caps how much a problem is worth. Growing fast among smaller product teams.
▸ Try the interactive toolShape Up, developed by Ryan Singer at Basecamp, is a product-development methodology that rejects sprints in favour of six-week cycles with uninterrupted focus and built-in appetite constraints. It's growing in adoption, especially at smaller, founder-led product companies, precisely because it offers an alternative to the backlog-and-sprint machinery many teams find grinding.
Two ideas define it. First, fixed time, variable scope: a project gets a fixed appetite (typically six weeks), and the scope flexes to fit the time — the opposite of estimating a fixed scope and letting time stretch. Second, appetite over estimate: instead of asking ‘how long will this take?’, Shape Up asks ‘how much is this problem worth to us?’ — and that appetite becomes the constraint the solution must fit. Work is ‘shaped’ at the right level of abstraction before being bet on, and teams get uninterrupted cycles with no sprint ceremonies.
Fixed time, variable scope — set the appetite, flex the scope to fit
Appetite, not estimate — ask 'how much is this worth?' not 'how long?'
Shaped work — defined at the right abstraction before betting
Six-week cycles — uninterrupted focus, no sprint ceremonies
Shape Up is a reaction against two pains: the endless grind of sprints and backlog grooming, and the way fixed-scope estimation lets timelines balloon.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Scope creep stretching timelines | Fixed scope + flexible time means projects expand indefinitely. | Fixed time + variable scope caps the investment and ships on time. |
| Estimate theatre | ‘How long will it take?’ invites inaccurate, padded estimates. | ‘How much is it worth?’ sets a deliberate appetite instead. |
| Sprint grind | Constant two-week cycles and grooming exhaust teams. | Six-week cycles give uninterrupted focus and breathing room. |
| Under-shaped work | Vague projects expand or stall once started. | Shaping defines the right level of detail before betting on it. |
Decide how much a problem is worth — typically a small (two-week) or big (six-week) batch. The appetite is a deliberate cap on investment, chosen before any solution exists.
Define the solution concretely enough to be actionable but loosely enough to leave room for the team's judgement. Over-specified shaping removes autonomy; under-shaped work expands or stalls.
Leadership 'bets' on which shaped projects get a six-week cycle. There's no backlog that haunts the team — unbet work simply isn't committed, and is reconsidered fresh next time.
Within the cycle, the team cuts scope as needed to ship something good within the appetite. The deadline is fixed; what gets built flexes — not the reverse.
After each six-week cycle, a short cool-down handles loose ends and lets the team breathe before the next bet. The rhythm is sustainable by design.
A team kept asking ‘how long will this feature take?’, getting padded estimates, then watching scope creep stretch the actual timeline far past them. Every project felt open-ended, and the backlog of half-promised work loomed permanently.
Reframing with Shape Up changed the question to ‘how much is this problem worth to us?’ They set a six-week appetite, shaped the work to fit it, and committed to flexing scope rather than time. When the cycle ran short, they cut the least essential scope and shipped something good on time — instead of letting the project balloon. The fixed appetite turned an open-ended estimate into a deliberate, bounded bet.
The deliverable is shaped work with a set appetite, bet on for a six-week cycle, with scope flexing to fit the fixed time.
| Sprints/backlog | Shape Up |
|---|---|
| Estimate the scope | Set the appetite (worth) |
| Fixed scope, flexible time | Fixed time, flexible scope |
| Permanent grooming backlog | Bet fresh each cycle, no haunting backlog |
| Two-week sprints | Six-week cycles + cool-down |
Shape Up's central inversion — fix the time, flex the scope; ask what a problem is worth, not how long it takes — is a genuinely different way to think about commitment, and it directly attacks the scope creep that plagues estimate-driven work.
Whether Shape Up fits depends on context, and that's the real lesson. Its six-week cycles and no-backlog discipline work beautifully for smaller, founder-led teams that can make clean bets and protect uninterrupted focus — which is exactly where it's spreading. It fits less naturally where work is highly interdependent across many teams, or where stakeholders demand the predictability that fixed-scope commitments (however flawed) seem to offer. A PM's value isn't in dogmatically adopting Shape Up, Scrum, or Kanban, but in recognising which of their core ideas solve the team's actual pain — and the appetite-over-estimate reframing is one worth borrowing even by teams that never adopt the full method.
The whole point is appetite, not estimate. Ask what the problem is worth, not how long it takes.
If you let the deadline stretch, you've lost Shape Up's core discipline. Cut scope, hold the time.
Specifying every detail removes the team's autonomy. Shape at the right abstraction, no further.
Shape Up bets fresh each cycle. A permanent backlog of promises reintroduces the grind it avoids.
Shape Up strips structure for focus; SAFe (Tool 10) adds it for scale — opposite responses to delivery.
‘Betting’ on cycles rather than committing far ahead mirrors the roadmap's confidence horizons (Module 2, Tool 25).
‘How much is this worth?’ is a prioritisation question — it connects to RICE/ICE value thinking (Module 1).
Fixed-time/variable-scope is one expression of ‘responding to change’ (Tool 01).
Take a project you'd normally estimate. Instead of asking ‘how long will it take?’, ask ‘how much is solving this worth — two weeks, or six?’ Set that as a fixed appetite.
Now think about what scope you'd cut to ship something good within that fixed time, rather than letting the time stretch.
The shift from ‘how long?’ to ‘how much is it worth?’ is the single most portable idea in Shape Up — even teams that never adopt the method can use it to stop projects ballooning.