Shape Up
DesignProduct

Shape Up

Ryan Singer
Read 15 May 2021

Review

Shape Up arrives with opinions, which is rarer than it sounds in a product book. Ryan Singer doesn't describe a neutral framework you can adapt however you like; he describes how Basecamp actually works, and that specificity is the whole point. The problems it targets are real ones: long projects that drift, no breathing room for strategic thinking, teams that ship slower as the codebase ages. I won't pretend most teams can adopt this wholesale. The six-week cycles and no-backlog betting table require a level of senior buy-in that most organizations never have. But that's the wrong way to read it. The question the book keeps raising is: what can I borrow from this? Plenty, it turns out.

Key Takeaways

The parts worth keeping

Shaping

Shaping is up-front design work that sets boundaries and reduces project risk before handing anything to a development team. It runs on a separate track from building: one group shapes while another builds.

Shaped work has three properties:

The four steps of shaping:

  1. Set the appetite. Not an estimate of how long something will take, but a decision about how much time it deserves. Small batch (1-2 weeks) or full cycle (6 weeks). Fixed time, variable scope. If you can't define the problem narrowly enough to fit the appetite, the idea needs more work. Watch out for grab-bags (refactors and redesigns): split them into smaller, better-defined projects.
  2. Find the elements. Move from words to the key components of the solution. Use breadboards (places, affordances, connection lines) and fat marker sketches to stay at the right level of abstraction. Too concrete and you remove decision-making from the team; too vague and they have nothing to start from.
  3. Address risks and rabbit holes. Walk through the use case slowly. Find the holes before betting on the work. Declare what you won't do. The work is ready when you can name the solution elements, the known rabbit holes, and the explicit out-of-scope areas.
  4. Write the pitch. The pitch is what goes to the betting table. It contains: the problem, the appetite, the solution (as sketches or breadboards), known rabbit holes, and declared no-gos. Invite comments before it gets committed.

Betting

Before each six-week cycle, a betting table decides what gets built. No backlog. Pitches are reviewed and bets are placed. Ideas that don't get picked either come back stronger next time or they don't; important ideas resurface on their own.

Three phases for building a new product (rather than adding to an existing one):

Building

Teams get assigned projects, not tasks. Done means deployed. The first few days are for orientation; the real task list reveals itself through actual work, not planning.