methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session1-2 hours for first draft, plus reviewsWorkshop or asyncDIBB document

Session: DIBB

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 2-8. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward DIBB document. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Section 1: Data

    30-45 min

    Collect hard data, facts, and observations. For each data point define source (dashboard, study, interview quote, market report). Add collection date and context. No interpretation in this section. Hint: Interpreting in Data mixes layers. Data should be numbers, quotes, facts. Interpretation belongs in Insight. If merged, it is unclear later what is evidence and what is interpretation.

    FacilitatorDIBB document
  2. 2

    Section 2: Insight

    30-45 min

    Derive key findings from data. Insight links multiple data points into one picture. Keep to 3-5 insights; more dilutes the result. Reference underlying data for each insight. Hint: An insight tied to only one data point is often just a restatement. Real insight combines at least two data points into a statement.

    FacilitatorBelief list
  3. 3

    Section 3: Belief

    30-45 min

    Belief is a derived conviction from Insights. A Belief is a position: "We believe that ...", often with implicit assumptions. Make assumptions explicit. Reference Insights for each Belief. Hint: Beliefs without explicit assumptions become untestable later. If "the market keeps growing" is hidden as an assumption, that belief cannot be updated when the trend changes.

    FacilitatorBet list
  4. 4

    Section 4: Bet

    30-45 min

    Define what we do, what we do not do, what we invest in, and over which time horizon. Define Bet success measurement (which metric and when shows success). Name explicit exclusion options. Hint: A Bet without success measurement is hope. Each Bet needs at least one metric and one horizon. A Bet without non-action options is wishful thinking.

    FacilitatorLearning report
  5. 5

    Section 5: Review and signature

    30-60 min

    Run reviewer round with written comments. Owner revises where needed. Sponsor signs Bet in writing. Record date, version, and review date (for example 6 months). Hint: Reviews often reveal where data is weak or Beliefs are vague. Substantive critique triggers revisions, not polish. Sponsor signature creates commitment, not ceremony.

    FacilitatorDIBB document
  6. 6

    Section 6: Learning and updates

    Quarterly, 1 h

    Quarterly review: which Beliefs are challenged by new data? For each Belief set status: confirmed, weak, disproven. If disproven, adapt or reconfirm Bet with new rationale. Hint: Teams that never review Beliefs keep Bets alive artificially. Visible update of Beliefs protects against sunk-cost bias.

    OwnerBelief list
  7. 7

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerDIBB document
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: DIBB

Goal

Artifact: DIBB document

Working Question

On what basis, and with which Beliefs and Insights from which data, does the team take which Bet (decision)?

Context

Decision question in one sentence; available data and sources; known assumptions from previous decisions; Bet time horizon; success metric for the Bet (what shows success at 6, 12, or 24 months).

Setup

  • Format: Method session
  • Duration: 1-2 hours for first draft, plus reviews
  • Mode: Workshop or async
  • Participants: One owner (strategy lead, PM, or departmental head) as author; one to three reviewers from neighboring areas; sponsor with decision mandate; data owner for fact check.
  • Owner: One owner (strategy lead, PM, or departmental head) as author
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward DIBB document. After the session, the artifact should be shareable, reviewable, or reusable.

Input

DIBB template with four sections (Data, Insight, Belief, Bet); source directory for data; stakeholder review plan; versioning system (Git or Notion); success measurement setup.

Preparation

Create the DIBB template. Prepare source section for data. Schedule review slot in calendar. Activate versioning tool. Definition of done: sponsor signs Bet.

Agenda

  1. Section 1: Data (30-45 min) Owner: Facilitator Action: Collect hard data, facts, and observations. For each data point define source (dashboard, study, interview quote, market report). Add collection date and context. No interpretation in this section. Hint: Interpreting in Data mixes layers. Data should be numbers, quotes, facts. Interpretation belongs in Insight. If merged, it is unclear later what is evidence and what is interpretation. Output: DIBB document

  2. Section 2: Insight (30-45 min) Owner: Facilitator Action: Derive key findings from data. Insight links multiple data points into one picture. Keep to 3-5 insights; more dilutes the result. Reference underlying data for each insight. Hint: An insight tied to only one data point is often just a restatement. Real insight combines at least two data points into a statement. Output: Belief list

  3. Section 3: Belief (30-45 min) Owner: Facilitator Action: Belief is a derived conviction from Insights. A Belief is a position: "We believe that ...", often with implicit assumptions. Make assumptions explicit. Reference Insights for each Belief. Hint: Beliefs without explicit assumptions become untestable later. If "the market keeps growing" is hidden as an assumption, that belief cannot be updated when the trend changes. Output: Bet list

  4. Section 4: Bet (30-45 min) Owner: Facilitator Action: Define what we do, what we do not do, what we invest in, and over which time horizon. Define Bet success measurement (which metric and when shows success). Name explicit exclusion options. Hint: A Bet without success measurement is hope. Each Bet needs at least one metric and one horizon. A Bet without non-action options is wishful thinking. Output: Learning report

  5. Section 5: Review and signature (30-60 min) Owner: Facilitator Action: Run reviewer round with written comments. Owner revises where needed. Sponsor signs Bet in writing. Record date, version, and review date (for example 6 months). Hint: Reviews often reveal where data is weak or Beliefs are vague. Substantive critique triggers revisions, not polish. Sponsor signature creates commitment, not ceremony. Output: DIBB document

  6. Section 6: Learning and updates (Quarterly, 1 h) Owner: Owner Action: Quarterly review: which Beliefs are challenged by new data? For each Belief set status: confirmed, weak, disproven. If disproven, adapt or reconfirm Bet with new rationale. Hint: Teams that never review Beliefs keep Bets alive artificially. Visible update of Beliefs protects against sunk-cost bias. Output: Belief list

  7. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: DIBB document

Closeout

  • Update result artifact: DIBB document
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

DIBB document: DIBB

Working Question

On what basis, and with which Beliefs and Insights from which data, does the team take which Bet (decision)?

Context

Decision question in one sentence; available data and sources; known assumptions from previous decisions; Bet time horizon; success metric for the Bet (what shows success at 6, 12, or 24 months).

Participants

  • Owner: One owner (strategy lead, PM, or departmental head) as author
  • Participants: One owner (strategy lead, PM, or departmental head) as author; one to three reviewers from neighboring areas; sponsor with decision mandate; data owner for fact check.

Input

DIBB template with four sections (Data, Insight, Belief, Bet); source directory for data; stakeholder review plan; versioning system (Git or Notion); success measurement setup.

Template

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.

Completion Check

  • DIBB document is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

DIBB Working Template

View 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.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits DIBB document.
  • Use SemVer per DIBB document. Major version for Bet changes, minor for Belief updates, patch for data refresh. Archive prior versions with diff view. New Bet reversal creates a new DIBB with a reference.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet