Shape Up: shaping work and betting on six-week cycles

Who should use it, and when not to

Use it when feature requests are vague or keep growing, when estimates are always wrong, or when a team wants long, uninterrupted stretches of work instead of an endless queue of tickets.

It suits product teams that can control their own schedule. Teams with fixed client deadlines or heavy support duties may borrow only parts, such as the pitch. For a full requirements document, use the PRD skill.

The core ideas

Fixed time, variable scope. Singer contrasts appetites with estimates. An estimate takes a design and asks how long it will take; an appetite takes a time budget and asks what design fits it. A small batch is one designer and one or two programmers for one or two weeks; a big batch is the same team for six weeks.

Shaping. Shaped work is rough (room for the team to design), solved (the main elements are clear) and bounded (appetite and no-gos). Tools include breadboarding (places, affordances, connections) and fat-marker sketches.

The pitch. Five ingredients: problem, appetite, solution, rabbit holes and no-gos.

Bets, not backlogs. At the betting table, people decide which pitches to bet on for the next cycle. Unchosen ideas aren't stored in a queue; if they matter, they come back.

Cycles and cool-down. Six weeks of uninterrupted work, then a cool-down for fixes and exploration. If a project doesn't finish in its cycle, the default is that it doesn't get more time automatically, which Singer calls the circuit breaker.

A worked mini example

This is an illustration. Sales asks for "full recurring appointments" in a booking app for physiotherapists; engineering estimates three months. A clinic owner books the same patient every Tuesday for eight weeks, by hand, and once forgot one.

The shaped problem is weekly treatment courses, not every recurrence pattern. Appetite: six weeks. Solution: "repeat weekly" on the booking form with a number of weeks, a list of clashes before confirming, and each booking independent afterwards. Rabbit holes resolved: no editing of the whole series. No-gos: other patterns, "edit all following", patient-created series.

How to write a pitch

1. Find the problem in a specific story, separate from the requested solution.
2. Set the appetite: a small or big batch, and why.
3. Sketch the solution as elements and flows, not finished screens.
4. Find rabbit holes and decide each one now.
5. List the no-gos.
6. Assemble the five ingredients into a short pitch.
7. Check it is rough, solved and bounded before the betting table.

The shaped pitch skill turns a raw request into a pitch with these five ingredients.

Common mistakes

• Starting from the estimate. Fix the time, shape the scope.
• Wireframes too detailed. The team loses room to design.
• Words too abstract. "Improve recurrence" isn't shaped.
• Leaving the rabbit holes for mid-cycle.

Where it comes from

Ryan Singer worked on product strategy at Basecamp and wrote Shape Up to describe how the company works, with a foreword by Jason Fried. Basecamp publishes the whole book free on its website, with a print edition available.

This page is an independent summary in our own words. It is not affiliated with or endorsed by Ryan Singer or Basecamp. The book's title is used only to name it. More explainers are in the business books index.

Questions

What is an appetite in Shape Up?

How much time a problem is worth, decided before designing the solution: for example two weeks or six weeks for a small team. Unlike an estimate, it fixes the time and lets the scope change to fit.

What goes into a Shape Up pitch?

Five ingredients: the problem, the appetite, the solution at a rough level, the rabbit holes (risks and how they were resolved), and the no-gos (what is out of scope).

Does Shape Up use a backlog?

No. Basecamp describes bets instead of backlogs: before each cycle, a betting table chooses among shaped pitches, and ideas that aren't chosen are not kept in a queue. Important ideas come back.