Quarterly Bets for Product
Quarterly bets are time-boxed, scoped commitments to a specific outcome with explicit kill criteria — a hybrid between a project, an experiment, and a contract. Basecamp's Shape Up methodology popularized the format: a 'bet' is a shaped problem with an appetite (how much time you're willing to spend) and a clear win condition.…
The trap
The trap is calling work 'bets' but treating them like plans — extending the timebox, re-scoping mid-bet, declaring partial completion a win. Once a bet's timebox slips, the format is broken. The other trap: too many bets running concurrently. Shape Up's discipline is one bet per team per cycle. Teams that run 4 'bets' in parallel are running 4 projects with bet-flavored vocabulary; the focus benefit disappears. Third trap: bets without kill criteria. If a bet can never 'fail,' it's not a bet, it's a wish.
What to do
Pick 3–5 quarterly bets at the org level (one per team for a small org, one per group for a larger one). Each bet has: shaped problem (1 page), appetite (e.g., 6 weeks), win condition (specific outcome), kill criteria (when to stop early). Use a 'cool-down' period of 2 weeks between cycles for cleanup, exploration, and shaping the next bets. At end-of-quarter, score bets win/lose/kill — not 'partial.'
Formula
In practice
Basecamp pioneered Shape Up bets: 6-week appetites, no extensions, work organized around 'shaped' problems with explicit boundaries. After Basecamp open-sourced the methodology, Linear adopted a similar 'cycles' approach (6-week cycles in their case), and many YC companies adopted variants. The defining example from Shape Up: when a bet runs out of time, you ship what's done or kill the work. You don't extend. This forces the team to scope around what fits in the appetite from day 1, rather than discovering scope creep at week 5. Source: Basecamp, Shape Up by Ryan Singer.
Pro tips
- 01
Ryan Singer (Shape Up): 'The appetite is the constraint. We don't ask how long it will take — we say how much time it's worth and shape the work to fit.'
- 02
Distinguish bets from operational work. Bets are the discretionary investments; bug fixes, security, and ops are not bets — they're hygiene. Mixing them collapses the format.
- 03
Publish bet outcomes. A team that runs 5 bets per quarter and never publishes which won, lost, or was killed is not running real bets. The published score is what creates the accountability that makes the format work.
Myth vs reality
Myth
“Bets are just sprints with marketing”
Reality
Sprints commit to a backlog; bets commit to an outcome with a kill criterion. A sprint that 'didn't finish' gets carried over. A bet that doesn't pay off ends. The difference is the contract with reality, not the duration.
Myth
“Bets and roadmaps are incompatible”
Reality
They serve different layers. The roadmap (Now/Next/Later or outcome-based) sets direction. Bets are the quarterly mechanism to make progress on direction. A team can have a Now item and run a bet inside it.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your team's 6-week bet hits week 6 with the work 75% complete. The team requests a 2-week extension because 'we're so close.' What's the disciplined response?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Bet Win Rate (Hit in Appetite, No Extension)
Product teams using Shape Up or cycles methodologyToo Safe — Raise Ambition
> 80%
Healthy
50–70%
Acceptable
30–50%
Too Ambitious — Improve Shaping
< 30%
Source: Basecamp Shape Up + Linear cycles practice
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Basecamp
2009–present
Basecamp pioneered Shape Up: 6-week appetites with 2-week cool-downs, shaped problems with explicit boundaries, no extensions allowed. Ryan Singer documented the methodology in the Shape Up book (open-sourced), which has been adopted by hundreds of companies. The defining cultural rule: when an appetite ends, you ship what's done or kill the work. Extensions are not granted. This forces shaping discipline upstream — teams learn to scope work that fits the appetite from day 1.
Standard Appetite
6 weeks
Cool-Down
2 weeks
Extensions Granted
0 (cultural rule)
The appetite is the constraint that makes the format work. Once extensions are allowed, Shape Up becomes a sprint with marketing. The discipline is what's NOT permitted.
Linear
2020–present
Linear adopted a 'cycles' approach inspired by Shape Up — typically 6-week cycles with explicit goals per cycle and a hard end date. Linear's product team has publicly discussed how the cycles model produces predictable shipping cadence and forces honest conversations about scope. Their published reflections emphasize the same Basecamp discipline: cycles end on schedule, work that didn't fit either ships smaller or moves to a future cycle (re-bet, not extend).
Cycle Length
6 weeks
Mid-Cycle Scope Changes
Discouraged
Public Cycle Recap
Yes
The format scales beyond Basecamp. Companies that adopt cycles and publish outcomes get the focus benefit; those that adopt cycle vocabulary without the discipline get the overhead without the benefit.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Quarterly Bets for Product into a live operating decision.
Use this concept as the framing layer, then move into the matched diagnostic — or have us scope the build.
Typical response time: 24h · No retainer required
Turn Quarterly Bets for Product into a live operating decision.
Use Quarterly Bets for Product as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.