Chapter II
The betting table
One short meeting, held during cool-down, where leadership weighs the shaped pitches and decides what the next cycle will build.
The two tracks have run apart for six weeks. The betting table is where they meet. Every finished pitch comes to the betting table once and gets one of two answers: a bet, which gives it a team and a place in the next cycle, or a pass. A pass isn’t a spot in a queue. If the idea still matters, someone pitches it again next time.
Why it's called betting
The word is chosen with care. Three things about a bet are true here that aren’t true of a roadmap — and each one is deliberate.
A bet has stakes.
A plan pretends the future is knowable. A bet accepts that it isn’t. You’re staking six weeks on a pitch you believe pays off — knowing it might not — rather than scheduling an outcome you can’t actually promise.
The betting table has no backlog.
A passed pitch doesn’t slide into a queue for “later.” Later doesn’t exist here. If it still matters next cycle, someone pitches it again, fresh. Ideas earn their place every time or they don’t have one.
The bet is capped.
The appetite set in shaping is the bet — a fixed budget with a hard stop. Work that runs past six weeks doesn’t roll over on its own. It comes back to the table and has to win again.
Who’s in the room
A small group, a short meeting
The betting table is a handful of people — the ones who can commit the company’s time. It’s quiet, and it’s brief. There are no presentations: the pitches were written to be read, and everyone read them before walking in. The meeting isn’t for discovering the pitches. It’s for choosing among them.
Because shaping already did the hard thinking — the appetite is set, the rabbit holes are walked, the no-gos are drawn — the meeting can move fast. Every pitch arrives at the same altitude, bounded and de-risked, which is the only reason a few people can weigh a cycle’s worth of work in a single sitting.
Fig. 1 · What each pitch is weighed against
- 1
Does the problem matter?
Is this worth a slice of the company’s only cycle?
- 2
Is the appetite right?
Do we actually want to spend this much time on this problem?
- 3
Is the solution attractive?
Will building this actually create something worth having?
- 4
Is this the right time?
Does something else have a stronger claim on the cycle?
- 5
Are the right people free?
Can we staff it — or is the one person who could build it already in a bet?
A pitch can be excellent and still not get bet. A great solution to a real problem loses to bad timing, or to the plain fact that everyone who could build it is already committed. Passing here is rarely about quality.
Placing the bet
To bet is to staff
Betting isn’t a stamp of approval — it’s an assignment. You cannot bet on a pitch without putting a team behind it: the same motion that chooses a pitch names the people who will carry it. Choosing and resourcing are the same act.
Which means leadership can’t bet more work than there are people to build it. Bets come in two sizes: six weeks or two. A big batch takes a person’s entire cycle — one pitch, nothing else. Small batches are two weeks each, so a person can hold up to three in a cycle.
Fig. 2 · The betting table’s two outcomes
A focused day view
The calendar shows everything at equal weight, so the day's few get lost among the many.
Team assembled
Bet placed — the pitch gets built in the next cycle.
Shared saved views
Teams rebuild the same calendar filters by hand every week — real, but not this cycle's fight.
Note on passing
Passed — freed, not filed. It leaves nothing behind.
Every pitch gets the same two buttons: bet or pass. A bet leaves with a team, a pass leaves with a short note, and there is no third option.
The other outcome
A pass is not a rejection
To pass is to say not this, not now. A pass can carry a note, a sentence on why, so the shaper isn’t left guessing. Then the pitch leaves the betting table. If it’s still worth doing, someone shapes it again and pitches it next cycle. If it isn’t, it’s gone.
This is why there’s no backlog. Nothing accumulates between cycles, and there’s no old list to groom or feel behind on. Every pitch under consideration is there because someone thought it was still worth pitching.
By the end of the meeting, every pitch is either a bet with a team or a pass. The bets become the next cycle’s building work: when cool-down ends, the builders pick them up and the six weeks start again.
Terms from this chapter
Bet
A commitment to build a pitch in the next cycle, staffed with a team.
Pass
Declining a pitch for this cycle, often with a short note.