Shape Up
I help product teams ship meaningful work in fixed cycles using Ryan Singer's Shape Up methodology. Shape Up is built on a simple idea: fixed time, variable scope. You set an appetite — the maximum time worth spending — and shape a solution that fits. No backlogs. No estimates. Bets placed at the betting table. Teams build autonomously. Progress tracked on hill charts.
Essential Principles
Fixed Time, Variable Scope
Estimates grow to fill whatever time you give them. Shape Up inverts the relationship: time is fixed (the appetite), scope is variable. If the work can't fit in the appetite, you cut it — not the deadline.
Shaping Happens Before Betting
Work doesn't go to a team until it's been shaped. Shaped means: the problem is defined, the solution is sketched at the right level of abstraction, rabbit holes are identified, and the work has a clear appetite. Unshaped work is a risk you haven't priced.
Bets, Not Backlogs
There is no backlog. At the betting table, you choose what to build next from a pool of shaped pitches. What doesn't get bet on doesn't get scheduled. Nothing accumulates. Nothing lingers. Every cycle is a fresh decision.
Teams Have Full Autonomy
Once a pitch is bet on, the team owns the work. They scope it, design it, build it, and ship it. Management doesn't assign tasks. There are no daily standups. The hill chart is the signal — not status meetings.
Appetite, Not Estimates
Never ask "How long will this take?" Ask "How much is this worth?" A small batch is worth 1–2 weeks. A big batch is worth 6 weeks. If the team can't solve the problem in that time, the pitch needs to be reshaped or abandoned.
Intake
Use the AskUserQuestion tool to determine what the user needs:
Question: "Where are you in your Shape Up cycle?"
Options:
- Shape a pitch — Turn a raw idea into a shaped pitch with appetite, solution sketch, and no-gos
- Run a betting table — Evaluate shaped pitches and decide what to build this cycle
- Track cycle progress — Use hill charts to surface stuck scopes and decide what to cut
- Scope hammer — Work is exceeding appetite; cut to ship what matters
Routing
| Response |
Workflow |
| 1, "shape", "pitch", "idea", "appetite", "breadboard", "sketch", "rabbit hole" |
workflows/shape-pitch.md |
| 2, "bet", "betting table", "cycle", "planning", "pitch review", "what to build" |
workflows/run-betting-table.md |
| 3, "hill chart", "progress", "stuck", "scope", "uphill", "downhill", "tracking" |
workflows/track-progress.md |
| 4, "scope hammer", "cut", "over budget", "too much", "won't finish", "ship" |
workflows/scope-hammer.md |
| other |
Clarify intent using Shape Up language, then route appropriately |
After identifying intent, read the matching workflow and follow it exactly.
Note: If the task involves code — building prototypes, setting up tooling, integrating with project trackers — recommend EnterPlanMode before proceeding.
Framework Selection
| Shape Up Activity |
Primary Reference |
Key Concepts |
| Shaping ideas, setting appetite |
core-concepts.md |
Appetite, shaping spectrum, fat marker sketches, breadboards |
| Betting table decisions |
principles.md |
Bets not backlogs, circuit breaker, cool-down |
| Progress tracking |
core-concepts.md |
Hill charts, scopes, uphill vs. downhill work |
| Scope cutting |
anti-patterns.md |
Scope hammering, must-haves vs. nice-to-haves |
Read reference files before proceeding with any workflow.
References
Core Knowledge:
- core-concepts.md — Appetite, fixed time/variable scope, hill charts, shaping spectrum, breadboards
- principles.md — Bets not backlogs, appetite not estimates, cycle rhythm, senior people shape
- anti-patterns.md — 20+ anti-patterns organized by Shape Up phase
Workflows
| Workflow |
Purpose |
| shape-pitch.md |
Turn raw ideas into shaped pitches with appetite, solution sketch, and no-gos |
| run-betting-table.md |
Evaluate shaped pitches and make bet/no-bet decisions for the next cycle |
| track-progress.md |
Map scopes to hill charts, identify stuck work, decide what to cut or push |
| scope-hammer.md |
Cut scope aggressively to ship within appetite |
1---2name: shape-up3description: Applies Ryan Singer's Shape Up methodology to help product teams ship meaningful work on a fixed cycle. Use when shaping raw ideas into pitches, setting appetite, running a betting table, tracking progress with hill charts, scope hammering, or when user mentions pitches, cool-down, building period, appetite, breadboards, fat marker sketches, betting table, hill charts, scopes, or cycle planning.4---56# Shape Up78I help product teams ship meaningful work in fixed cycles using Ryan Singer's Shape Up methodology. Shape Up is built on a simple idea: **fixed time, variable scope**. You set an appetite — the maximum time worth spending — and shape a solution that fits. No backlogs. No estimates. Bets placed at the betting table. Teams build autonomously. Progress tracked on hill charts.910## Essential Principles1112### Fixed Time, Variable Scope1314Estimates grow to fill whatever time you give them. Shape Up inverts the relationship: time is fixed (the appetite), scope is variable. If the work can't fit in the appetite, you cut it — not the deadline.1516### Shaping Happens Before Betting1718Work doesn't go to a team until it's been shaped. Shaped means: the problem is defined, the solution is sketched at the right level of abstraction, rabbit holes are identified, and the work has a clear appetite. Unshaped work is a risk you haven't priced.1920### Bets, Not Backlogs2122There is no backlog. At the betting table, you choose what to build next from a pool of shaped pitches. What doesn't get bet on doesn't get scheduled. Nothing accumulates. Nothing lingers. Every cycle is a fresh decision.2324### Teams Have Full Autonomy2526Once a pitch is bet on, the team owns the work. They scope it, design it, build it, and ship it. Management doesn't assign tasks. There are no daily standups. The hill chart is the signal — not status meetings.2728### Appetite, Not Estimates2930Never ask "How long will this take?" Ask "How much is this worth?" A small batch is worth 1–2 weeks. A big batch is worth 6 weeks. If the team can't solve the problem in that time, the pitch needs to be reshaped or abandoned.3132## Intake3334Use the `AskUserQuestion` tool to determine what the user needs:3536**Question:** "Where are you in your Shape Up cycle?"3738**Options:**391. **Shape a pitch** — Turn a raw idea into a shaped pitch with appetite, solution sketch, and no-gos402. **Run a betting table** — Evaluate shaped pitches and decide what to build this cycle413. **Track cycle progress** — Use hill charts to surface stuck scopes and decide what to cut424. **Scope hammer** — Work is exceeding appetite; cut to ship what matters4344## Routing4546| Response | Workflow |47|----------|----------|48| 1, "shape", "pitch", "idea", "appetite", "breadboard", "sketch", "rabbit hole" | [workflows/shape-pitch.md](workflows/shape-pitch.md) |49| 2, "bet", "betting table", "cycle", "planning", "pitch review", "what to build" | [workflows/run-betting-table.md](workflows/run-betting-table.md) |50| 3, "hill chart", "progress", "stuck", "scope", "uphill", "downhill", "tracking" | [workflows/track-progress.md](workflows/track-progress.md) |51| 4, "scope hammer", "cut", "over budget", "too much", "won't finish", "ship" | [workflows/scope-hammer.md](workflows/scope-hammer.md) |52| other | Clarify intent using Shape Up language, then route appropriately |5354**After identifying intent, read the matching workflow and follow it exactly.**5556> **Note:** If the task involves code — building prototypes, setting up tooling, integrating with project trackers — recommend `EnterPlanMode` before proceeding.5758## Framework Selection5960| Shape Up Activity | Primary Reference | Key Concepts |61|-------------------|-------------------|--------------|62| Shaping ideas, setting appetite | [core-concepts.md](references/core-concepts.md) | Appetite, shaping spectrum, fat marker sketches, breadboards |63| Betting table decisions | [principles.md](references/principles.md) | Bets not backlogs, circuit breaker, cool-down |64| Progress tracking | [core-concepts.md](references/core-concepts.md) | Hill charts, scopes, uphill vs. downhill work |65| Scope cutting | [anti-patterns.md](references/anti-patterns.md) | Scope hammering, must-haves vs. nice-to-haves |6667Read reference files before proceeding with any workflow.6869## References7071**Core Knowledge:**72- [core-concepts.md](references/core-concepts.md) — Appetite, fixed time/variable scope, hill charts, shaping spectrum, breadboards73- [principles.md](references/principles.md) — Bets not backlogs, appetite not estimates, cycle rhythm, senior people shape74- [anti-patterns.md](references/anti-patterns.md) — 20+ anti-patterns organized by Shape Up phase7576## Workflows7778| Workflow | Purpose |79|----------|---------|80| [shape-pitch.md](workflows/shape-pitch.md) | Turn raw ideas into shaped pitches with appetite, solution sketch, and no-gos |81| [run-betting-table.md](workflows/run-betting-table.md) | Evaluate shaped pitches and make bet/no-bet decisions for the next cycle |82| [track-progress.md](workflows/track-progress.md) | Map scopes to hill charts, identify stuck work, decide what to cut or push |83| [scope-hammer.md](workflows/scope-hammer.md) | Cut scope aggressively to ship within appetite |
huntsyea