methodDelivery & agility

Shape Up

A product-development method that shapes bounded pitches, bets on selected work, and gives small teams fixed time with flexible scope to deliver.

Download Markdown (.md)

01What it means

Shape Up is Basecamp’s method for selecting and executing product work. Senior product people shape an idea until its problem, appetite, boundaries, risks, and rough solution are clear enough to bet on. A betting table chooses pitches, then a small team gets a fixed cycle and broad autonomy to discover the detailed solution while building it.[1][2][3]

02Why it matters

Conventional backlogs can accumulate stale requests, and detailed estimates can create false certainty. Shape Up makes investment limits explicit through an appetite, requires important unknowns to be addressed before commitment, and protects a team from constant scope injection during the cycle.

03When to use it

Use it when experienced product teams can shape work, make explicit portfolio bets, and own implementation within meaningful boundaries. It suits organizations willing to discard unselected ideas rather than maintain a giant backlog. Modify it where urgent service work, external deadlines, or formal controls make uninterrupted cycles unrealistic.

04How it works

  1. Frame the customer or business problem and decide how much time it is worth.
  2. Sketch the main interaction and technical approach at the right level of abstraction.
  3. Mark rabbit holes, no-gos, and unresolved risks in a concise pitch.
  4. Choose pitches at a betting table based on context, value, and appetite.
  5. Give a small team responsibility for the detailed solution during a fixed cycle.
  6. Cut scope to preserve the deadline, then cool down, reflect, and choose new bets.

05A practical example

Example

A collaboration product wants easier guest access. Shaping narrows the bet to link-based invitations for existing projects, excludes organization-wide permissions, and sets a six-week appetite. During the cycle, the team drops custom invitation templates to protect security review and the core guest journey.

06Where it breaks

Shape Up reflects Basecamp’s context and is not a universal operating model. Shaping can become opaque design by senior staff, fixed cycles can encourage hidden overtime, and no-backlog rhetoric may lose valuable evidence. Teams still need user research, accessibility work, technical quality, and outcome measurement.

Common mistakes

  • Writing a detailed specification that leaves the delivery team no room to solve.
  • Calling an arbitrary deadline an appetite while keeping scope fixed.
  • Betting on work before exposing major interaction or technical risks.
  • Treating cooldown as spare capacity that must be fully preassigned.

07Sources

  1. Shape Up: IntroductionBasecamp · Official method bookShape Up: Introduction
  2. Principles of ShapingBasecamp · Official method guidancePrinciples of Shaping
  3. Bets, Not BacklogsBasecamp · Official method guidanceBets, Not Backlogs
View saved topics

Start typing to search titles, definitions, categories, and frameworks.