What is Shape Up?
Shape Up is a product development methodology created by Basecamp (now 37signals). It replaces sprint backlogs and velocity with Appetite (a time budget), Pitches (shaped work), and a Betting Table (a strategic decision point every cycle).
The core insight: most teams spend too much time estimating unshapen work and too little time thinking deeply about what to build. Shape Up inverts this — spend more time shaping before committing, then give teams uninterrupted time to build.
The 8-Week Cycle
After the 6-week building cycle, teams enter a 2-week Cooldown period — unstructured time for bug fixing, exploration, and rest. Shaping for the next cycle happens continuously in parallel with building.
Typical 8-week cadence: Weeks 1–6 → Building cycle (teams ship committed work) Weeks 7–8 → Cooldown (fixes, exploration, shaping) Day 1 of next cycle → Betting Table (commit to next pitches) Shaping always happens in parallel — it is NOT a phase.
Appetite vs Estimate
The most important concept in Shape Up: Appetite is how much time you're willing to spend on something — a business decision. An estimate is how long you think something will take — a technical prediction.
| Concept | Appetite | Estimate |
|---|---|---|
| Definition | Max time we'll invest for the value it delivers | Prediction of how long it'll take |
| Who sets it | Business / shapers | Developers |
| Changes scope? | Yes — scope is variable, appetite is fixed | No — teams work to the scope |
| Typical sizes | Small batch (1–2 weeks) or Big batch (6 weeks) | Story points, hours, days |
| Risk | Known upfront | Discovered mid-execution |
Shaping Work
Shaping is the upstream design work that transforms a raw idea into a pitch. It is done by a small team (usually 1 designer + 1 technical person) away from the building team. The output is a pitch, not a spec.
The four properties of shaped work
Writing a Pitch
A pitch is the output of shaping — a short document that gives the betting table enough information to make a yes/no decision. It is not a requirements document.
Pitch structure: 1. Problem — what customer pain are we addressing? 2. Appetite — how much time are we willing to spend? (S or L batch) 3. Solution — rough sketches (breadboards/fat marker) of the approach 4. Rabbit holes — what could go wrong? what are we explicitly NOT doing? 5. No-gos — what's out of scope to keep the appetite intact? Pitch length: 1–2 pages (or equivalent doc). Not a novel. Audience: the betting table (typically senior product + tech leadership)
Breadboards & Fat Markers
Shapers use two visual techniques to communicate the solution without over-specifying it:
Breadboard — a wireframe notation for flows: → Places (screens/dialogs) → Affordances (buttons, fields, actions) → Connection lines (navigation between places) Purpose: show the flow without implying visual design Fat marker sketch — drawn with a thick marker (or Sharpie): → Too rough for anyone to take as a spec → Shows spatial layout and rough composition → Leaves design decisions to the building team Purpose: communicate concept, not implementation
The Betting Table
The Betting Table is a brief meeting (2–4 hours) of senior stakeholders held before each building cycle. They review shaped pitches and decide which ones to "bet" on for the next cycle.
Betting Table participants (typically): → CEO / product leadership → CTO / technical leadership → Senior designer → No middle management, no committees Outcomes: → Accepted: pitch is assigned to a team for the next cycle → Declined: not this cycle (no backlog — re-pitch if still relevant) → Needs more shaping: return to shaper with specific questions Rules: → Teams are committed to 6 weeks uninterrupted → No new work added mid-cycle (circuit breaker) → No carryover — unfinished work is cancelled, not extended
The Building Phase
Once work is committed at the betting table, teams of 1–3 people (1 designer + 1–2 programmers) are given 6 weeks of uninterrupted time. No status meetings, no sprint reviews, no re-prioritisation.
Team autonomy
Teams in the building phase: → Decide their own order of work within the shaped pitch → Define their own tasks (no pre-assigned task lists) → Discover and solve implementation details autonomously → Cut scope to protect the appetite (not the schedule) → Have a single point of contact: the team itself
Scopes & Hill Charts
Teams organise work into Scopes (integrated slices of the problem) and track progress with Hill Charts — a visual tool that shows whether work is in the "figuring out" or "making it happen" phase.
Scopes (not tasks): → Meaningful chunks of the feature that can be completed end-to-end → Name reflects the problem solved, not the layer (e.g. "Invite flow" not "Backend") → Each scope can be shipped independently if needed Hill Chart: Uphill = "figuring out" (unknowns remain) Downhill = "making it happen" (path is clear) Peak = all unknowns resolved Status meeting replacement: → Teams update their Hill Chart in the project tool → Stakeholders check the chart, not the people → Stalled scopes on the uphill side trigger a conversation
Shape Up vs Scrum
| Dimension | Shape Up | Scrum |
|---|---|---|
| Cycle length | 6-week building + 2-week cooldown | 1–4 week sprints, continuous |
| Backlog | None (pitches are ephemeral) | Product Backlog (persistent) |
| Scope | Variable (fixed appetite) | Fixed per sprint (variable timeline) |
| Team size | 1–3 per project | 3–9 developers |
| Progress tracking | Hill charts (scopes) | Sprint burndown |
| Mid-cycle changes | Not permitted (circuit breaker) | Not permitted (Sprint Goal protected) |
| Best for | Product companies, ≤30 engineers | Any team size, continuous delivery |
Anti-Patterns
| Anti-Pattern | Problem | Fix |
|---|---|---|
| Maintaining a backlog | Old ideas accumulate; "maybe later" means never, except you're still managing it | Let pitches expire; re-pitch if still relevant next cycle |
| Over-specifying pitches | Teams can't make decisions; shaped work feels like a spec | Rough solutions only; fat markers, not wireframes |
| Adding work mid-cycle | Teams lose the uninterrupted time that makes Shape Up work | Enforce the circuit breaker; new work waits for the next betting table |
| Treating appetite as estimate | Teams treat the 6 weeks as a deadline and add scope to fill it | Scope is variable; if done early, use remaining time to improve quality |
| Carryover | Unfinished cycles extend; appetite becomes meaningless | Cancel unfinished work; re-shape and re-pitch if it's still worth doing |
| No shaping capacity | Betting table has nothing to bet on; teams get busywork | Senior people must protect time for shaping — it is strategy work |
Shape Up Cheat Sheet
Key concepts Appetite → how much time we're willing to spend (business decision) Pitch → shaped proposal: problem + appetite + rough solution + rabbit holes Betting → senior leadership chooses pitches; no committee; no backlog Circuit → unfinished work is cancelled, not extended Cooldown → 2 weeks after building for fixes, exploration, shaping Cycle cadence Weeks 1–6 → Building (teams work uninterrupted on committed pitches) Weeks 7–8 → Cooldown + Betting Table prep Day 1+ → Next building cycle begins Pitch elements 1. Problem (the customer pain) 2. Appetite (Small: 1–2 weeks | Large: 6 weeks) 3. Solution (breadboards + fat marker sketches) 4. Rabbit holes (known risks/unknowns to address early) 5. No-gos (explicit out-of-scope items) Building tools Scopes → integrated slices of the problem (not layers) Hill Chart → uphill (figuring out) → peak (solved) → downhill (making it happen) Team size: 1 designer + 1–2 programmers per project