methodatlas
Product Strategy

DIBB

Links data, insights, beliefs, and bets so strategy and product decisions become traceable and reviewable.

Core question
On what basis, and with which Beliefs and Insights from which data, does the team take which Bet (decision)?
LowWorkshop + async1-2 h
Purpose

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.

How it works

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.

DIBB · From Data to BetRun Data, Insight, Belief, and Bet as an explicit decision trail from signal to prioritized action
Data -> Insight -> Belief -> BetData, Insight, Belief und Bet machen den Weg von Signal zu Entscheidung explizit.Data bis EntscheidungsspurData, Insight, Belief und Bet machen den Weg von Signal zu Entscheidung explizit.nicht Rohdaten alleinAnnahme sichtbarBet mit BegründungDatabeobachtbares SignalInsightMuster oder BedeutungBeliefexplizite AnnahmeBetkonkrete EntscheidungEntscheidungsspurwarum diese Wette sinnvoll ist, bleibt nachvollziehbar

Flow

  1. 1Gather relevant data
  2. 2Formulate central insights
  3. 3Make beliefs explicit
  4. 4Choose a concrete bet
  5. 5Version success criteria and assumptions
  6. 6Review the bet against learning

The runsheet guides execution with 6 phases, timeboxes, 6 pitfalls, and clear stop criteria.

Open runsheet

Ideal 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

In detail

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.

Facilitation

Keep beliefs and bets clearly separated from data. Version DIBB documents so learning loops remain visible, and revisit beliefs when new data challenges them.

Output artifacts
DIBB documentBelief listBet listLearning report
Tags
Artifact templates
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.

Architecture Decision Record

Statt DIBB, wenn du mit Architecture Decision Record eine Architekturentscheidung mit Kontext, Optionen und Konsequenzen dokumentieren willst.

Similar methods

All methods