Shape Up: Stop Running in Circles and Ship Work that Matters
Central idea
Teams ship more predictably when leaders bound the problem before committing and let builders vary scope inside a fixed appetite.
Summary
Shape Up separates project work into shaping, betting, and building. Shaping turns a raw idea into something rough, solved, and bounded: the problem is clear, major risks are exposed, and the team knows what is deliberately out of scope. Leaders set an appetite—the amount of time worth spending—instead of pretending an early estimate is precise. A betting table chooses a few shaped pitches rather than maintaining an endless backlog. Once selected, a small team owns the project, discovers the real tasks, organizes work into meaningful scopes, and cuts optional scope to finish within the cycle. Progress is measured by moving from unknowns to known execution, not by counting completed tickets.
Key ideas
Shape before committing
Resolve the core interaction, technical risks, boundaries, and no-gos while the cost of changing direction is still low.
Fix time, vary scope
An appetite forces trade-offs; it prevents both open-ended projects and false certainty from detailed upfront estimates.
Assign projects, not tasks
Give builders enough context and authority to discover the work and make local scope decisions.
The Shape Up loop
Shape a bounded pitch.
→Bet on a few worthwhile projects.
→Let a small team own the build.
→Cut scope and ship within the appetite.
Why it matters now
AI accelerates implementation, but it does not decide which problem deserves a team, what risks matter, or where scope should stop. Those shaping decisions become more—not less—valuable.
Continue with the original
This short version preserves the main argument. Follow the source for the complete talk, article, or book.