Rituals
The rhythms that make context live and breathe
The choice of rituals is highly contextual, so in the Starter Pack, we're offering broad-swatch recommendations to help you get started. These are meant to be adapted—not adopted wholesale. Every organization needs to evolve its own rhythms.
We follow a few guiding principles:
Key Principles
- Fractality. The more frontline rituals resemble those used at higher levels (e.g., product group or org-wide), the more you're reinforcing common language, enabling upward mobility, and allowing individuals to build fluency in how the organization thinks and decides.
- Show, Not Tell (Across Layers). Whenever possible, include multiple levels (e.g., directors participating in team-level triads) so that leadership can model behavior, demonstrate judgment, and share context through action—not just direction. This is critical for trust and shared understanding.
- Single Purpose or Open Agenda—But Not In-Between. We generally advocate for either single-purpose meetings with a clear goal and structure, or open agenda meetings where teams build the agenda collaboratively in advance. Avoid hybrid meetings that try to do both, as they often fail at both.
Rituals the Starter Pack Supports
There are many meetings that will naturally occur in any organization. But here are the ones the Starter Pack is designed to support, structure, and evolve with you over time.
These rituals reinforce a core idea: The real rhythm of product work flows from insights → opportunities → options → bets → execution → impact.
Along that journey, we also create feedback loops, review cycles, and decision checkpoints. These don't happen once—they happen at every level: team, triad, group, area, and org leadership.
Actionable Input Reviews
These are biweekly reviews that form the foundation of ongoing alignment and adaptation. They should involve:
- The team
- Their triad
- Ideally their skip-level triad or adjacent group leadership
Teams reflect on:
- Their actionable inputs
- Direction and variation over time
- What's changing and why
- Where focus should shift next
This is not a retro, a business review, or a status report. It's a learning loop focused on lever control, team focus, and signal interpretation.
From Insights to Bets
This is the backbone of the Starter Pack's discovery-to-delivery flow. You can think of it as a set of meetings designed to support diverge-converge cycles—each step narrowing the field of uncertainty and building momentum toward a well-formed, well-governed bet.
| Phase | Ritual | Purpose |
|---|---|---|
| Insights | Insight Deep Dives (monthly) | Variable-agenda sessions to explore relevant signals, research, and qualitative/quant data. Optional, divergent, and high-signal. |
| Opportunities | Opportunity Reads & Discussions | Pre-read and discuss early-stage opportunities. Focus is on shaping, surfacing gaps, and preparing for prioritization—not decision-making. |
| Opportunity Framing & Appetite Setting | Opportunity Selection + Appetite Meeting | Get crisp on which opportunities move forward, and at what scale. Options are forming, but decisions not yet made. |
| Options → Bets | Bet Assessment & Commitment | Teams present bets—structured options with clear investment theses, governance models, and learning loops. Not all bets are solution bets (e.g., "Give a team runway for 6 months"). |
| Bet → Work | Kickoff Meeting (for major bets) | Align on intent, scope, context, and rhythm for execution. Used for large or strategic bets, not everything. |
| Bet Governance | Weekly Progress Syncs (Triads / Teams) | As bets go live, triads and/or teams reflect on progress, risks, and learning. These evolve in nature as bets start showing impact. |
Bets can include experiments, projects, features, exploratory efforts, or capability investments. What matters is the structure: learning model, decision points, and type of work.
Cross-Cutting and Fractal Layers
The rituals listed above aren't just for product teams. Leadership runs them too, with different scope and altitude:
- Triads at group and area levels have their own actionable input reviews, bet syncs, and insight sessions.
- Product leaders evaluate business metrics, portfolio-level bets, and strategic capability gaps in similar ways.
Other Common Review & Governance Meetings
These vary by org but tend to slot in around the flow outlined above:
| Meeting | Purpose |
|---|---|
| QBRs | Summarize impact, reset strategic priorities, and calibrate forward investment. |
| Weekly Business Reviews (WBRs) | Operate like "pulse checks" for teams or groups. Metrics + issue surfacing. |
| Monthly Check-ins | Used by triads to stay in sync with leadership, connect with cross-functional partners, and reset where needed. |
| Readouts & Reviews | Lightweight, async or live updates to share what's been shipped, learned, or blocked. |
| Retrospectives | Focused reflection, often framed around bets or capability goals rather than just delivery. |
| Ad Hoc Brainstorms & Working Sessions | Used as needed. Ideally well-scoped, time-bound, and documented. |
| Budgeting / Resource Reviews | Typically tied to strategy resets, new bet commitments, or cross-area prioritization. |
| Hiring Plan Reviews | Framed around capability needs, upcoming bets, and team stage—not just headcount numbers. |
Modular Meeting Design: People × Purpose
Rather than mandating fixed formats, the Starter Pack encourages modular design:
- Get the right people: Triads, teams, skip levels, partners, leadership.
- Set the right purpose: Insight sharing? Bet commitment? Progress review?
- Stay crisp: Stick to single-purpose or clearly scoped variable agendas.
- Deep dive when needed: Use open time intentionally—not as filler.