Shape Up Principle: The Betting Table
· Summarized
Key takeaways
- The betting table is a core part of 37 Signals' product planning, focused on transparent, focused decision-making led by a designated final authority.
- Decisions are made asynchronously wherever possible, enabling thoughtful input and reducing meeting fatigue.
- Prioritization involves trade-offs, resource considerations, and timing, with flexibility for pitches to reappear in future cycles.
- Clarity of roles—as a council with a final decision-maker—improves decision quality and reduces conflicts.
- Effective resource planning aligns project pitches with team capacity, skill sets, and other commitments.
- The process encourages continuous learning from each cycle and avoids backlog clutter, emphasizing current relevance over backlog accumulation.
- Shape Up offers a powerful framework, emphasizing the importance of structured decision cycles and clear authority within product teams.
Summary
The Purpose and Structure of the Betting Table
This section explains what the betting table is—a key decision-making forum at 37 Signals where pitches for upcoming product work cycles are discussed and prioritized. The process involves refining pitches into a clear set of projects that align with company goals and resource availability. The betting table is designed not as a democracy but as a council-like structure, where one person (usually a product leader) makes the final decision after gathering input from others. This ensures focused decision-making and avoids the pitfalls of consensus-driven delays.
Evolution of the Betting Table Process
Jason and David describe how the betting table's format has evolved over the years, from large calls with many participants to a more streamlined, often asynchronous process. They emphasize the importance of clear roles, particularly the final decision-maker, to prevent the decision-making from becoming unwieldy. The process now involves multiple stages—initial pitches in a shared workspace, collaboration among different roles, and final decision-making, which is often done by a single person to maintain clarity and efficiency.
Decision-Making and Resource Allocation
The episode discusses how decisions about which projects to pursue are made in a way that balances input and clarity of authority. While the final decision rests with one person, others play advisory roles and advocate passionately for their pitches. Resource availability and team capacity are considered during the process to ensure realistic commitments. Assignments of team members are planned after project selection, factoring in their skills, availability, and the existing workload, to optimize execution.
Handling Rejected and Future Pitches
Not all pitches make it into a cycle; some are deferred to future cycles or discarded if their relevance diminishes. The episode highlights that pitches don’t automatically get a second chance but can be revisited if circumstances change. This approach prevents backlog buildup and encourages continuous prioritization based on current company needs and customer requests, treated as a moving average rather than a linear list.
The Benefits of Asynchronous Communication and Planning
37 Signals favors written, asynchronous communication over live meetings, citing advantages such as thoughtful consideration, fairness, and efficiency. Detailed pitches are shared well in advance of decision meetings, allowing team members to process and contribute meaningfully. The process supports better decision quality by giving everyone time to reflect and avoids the inefficiencies of real-time discussions. This approach also reduces the pressure on participants and helps maintain focus on critical disagreements that may require a call.
Sponsors
- 37 Signals · You can learn more about the product development process and principles discussed in this episode by reading the book Shape Up, available as a free download or purchase on their site.
Show notes
Picture this: a dimly lit room where velvet-robed figures gather in secret to make decisions of paramount importance as the fate of the pitches for the next product development cycle hangs in the balance.
The "betting table” – where the formalized pitches for each six-week work cycle are selected – might seem mysterious but we're about to unravel its secrets.
Listen in as host Kimberly Rhodes sits down with 37signals co-founders Jason Fried and David Heinemeier Hansson to explore the unique inner workings of the "betting table" and how this process shapes each product development cycle.
Tune in to discover 37signals' approach to selecting and refining projects at the "betting table."
Check out the full video episode on YouTube
Show Notes:
[00:00] - Today on the podcast, the discussion focuses on the betting table and how the decisions are made about which pitches are selected and which projects to schedule.
[00:42] - Jason shares what the betting table is.
[02:26] - The betting table process: refining pitches into a kickoff document.
[03:17] - David shares the background behind the betting table and how it has evolved.
[05:51] - The betting table: passionately advocating for different views, with one person ultimately making the decision.
[06:51] - Ensuring that resource allocation decisions are made efficiently while avoiding committee-driven decision-making.
[08:56] - Decisions made at the betting table can sometimes be passed to others who are more passionate or informed about a particular project.
[10:04] - It's all about timing—unselected pitches don't automatically get another chance in the next cycle, but if they are relevant, they might.
[10:51] - Jason shares his biggest issue with backlogs.
[11:33] - David shares why Shape Up is such a powerful way of working and how the betting table process provides multiple opportunities to influence product direction.
[14:38] - Jason shares how the assignment of team members works during the betting table to ensure that the available resources match the selected projects.
[15:49] - David shares the background behind aligning pitch budgets with available resources and calendars during the betting table.
[19:55] - Why so much of the betting table process is asynchronous and done via written communication,
[22:54] - When calls might need to happen during the betting table process.
[23:57] - For more background on how 37signals manages product development, get your free copy of the book Shape Up. It is available here.
[24:13] - Don't forget you can still enter #TheUnderdogChallenge by sharing the story of your scrappy team on the 37signals LinkedIn post here for a chance to be featured on a future episode of Rework. The deadline to enter is September 15. Rework is a production of 37signals. You can find show notes and transcripts on our website. Full video episodes are available on Twitter and YouTube. If you have a specific question for Jason or David about a better way to work and run your business, leave your voicemails at 708-628-7850.
Links and Resources:
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account