DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.
DIBB
Links data, insights, beliefs, and bets so strategy and product decisions become traceable and reviewable.
On what basis, and with which Beliefs and Insights from which data, does the team take which Bet (decision)?
The team gathers relevant data, formulates the central insights, makes beliefs derived from those insights explicit, chooses a concrete bet, versions success criteria and assumptions, and later reviews the bet against new learning.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Gather relevant data
- 2Formulate central insights
- 3Make beliefs explicit
- 4Choose a concrete bet
- 5Version success criteria and assumptions
- 6Review the bet against learning
The runsheet guides execution with 6 phases, timeboxes, 6 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Strategic decisions
- Product bets
- Cross-functional alignment
- Documenting strategy logic
Not good for
- Operational day-to-day decisions
- Pure backlog prioritization
- Topics without a data basis
Deep dive
DIBB was developed at Spotify for structured decision-making in product and strategy. A decision is built across four layers: Data are facts, metrics, or observations. Insight is the key interpretation drawn from the data. Belief is the conviction derived from the insight, including assumptions and context. Bet is the concrete decision or strategic wager. The structure keeps clear what a strategy is based on and which layer must be revisited when evidence changes.
Keep beliefs and bets clearly separated from data. Version DIBB documents so learning loops remain visible, and revisit beliefs when new data challenges them.
DIBB Working TemplateCompact working template for DIBB with context, input, output artifacts, and next step.markdown
dibb-working-template.md
Compact working template for DIBB with context, input, output artifacts, and next step.
DIBB Working Template
Goal
Spotify framework: Data, Insight, Belief, Bet, to structure decisions in a traceable way.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- DIBB document:
- Beliefs list:
- Bets list:
- Learning report:
Assumptions and open questions
- ...
Decision / next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Statt DIBB, wenn du mit Architecture Decision Record eine Architekturentscheidung mit Kontext, Optionen und Konsequenzen dokumentieren willst.
Similar methods
All methodsMoves target group, value, goals, and priorities toward a concrete result through "define the top metric", "describe the main driver of the top metric", and "set the review cadence".
Turns target group, value, goals, and priorities into a tangible result by drafting a raw goal, checking specificity, and defining time relevance.
Moves target group, value, goals, and priorities toward a concrete result through "name the main metric", "collect possible unintended side effects", and "use counter metrics alongside the main metric in reviews".
Vision, target group, needs, value, and business goals fit onto one board that exposes assumptions for validation.
Uses a structured proposal and review process to make non-trivial technical or product changes discussable and decidable.
Turns target group, value, goals, and priorities into a tangible result by setting the goal, identifying actors, and choosing the smallest meaningful next steps.