methodatlas
Session Builder

Plan my session

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

Method session1-3 hWorkshop or asyncIssue Map

Session: IBIS

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 Issue Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Frame the issue

    10-15 min

    Formulate the main question as an open issue ("How should we solve X?"). Split broad scope into sub-issues. Place the top issue at the top of the board. Hint: Issues are open questions, not judgments. "Should we do X" is a judgment and should be reframed as "How can we achieve X given Y and Z?"

    FacilitatorIssue Map
  2. 2

    Phase 2: Gather positions

    20-30 min

    Collect possible answers to the issue as positions (at least three). Use one clear sentence per position with a concrete answer. Hint: If only one position is named, the discussion is not open. The facilitator generates at least one counter-position with a devil's advocate role.

    FacilitatorPositions
  3. 3

    Phase 3: Assign arguments

    30-45 min

    Collect pro and contra arguments for each position. Arguments can be data, experience, or constraints. Add arrows from argument to position and make pro/contra symbols visible. Hint: Some arguments apply to multiple positions. Add a separate arrow per relationship to avoid illegible maps.

    FacilitatorArgument Notes
  4. 4

    Phase 4: Check relationships

    20-30 min

    Review the map together. Mark weak arguments. Note sub-issues that arise as new issues ("issue knot"). Hint: IBIS maps often produce issue knots that belong in separate sub-maps. Do not force all content into one map.

    FacilitatorIssue Map
  5. 5

    Phase 5: Make a decision or keep open questions

    15-20 min

    Mark position(s) driving decisions. Add rationale in the Decision Log. Add owner and date for open sub-issues. Hint: IBIS is primarily documentation, not a decision engine. If no position dominates, pass decision to the decider with the map as an attachment.

    OwnerPositions
  6. 6

    Publish artifact

    10 min

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

    OwnerIssue Map
Usable artifact

Session Brief

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

session-brief.md

Session Brief: IBIS

Goal

Artifact: Issue Map

Working Question

Which positions answer the central issue, and which arguments support or challenge each position?

Context

Central issue (question) as starting point; existing design docs or architecture decisions; list of existing discussion states; definition of what counts as argument (qualitative, quantitative).

Setup

  • Format: Method session
  • Duration: 1-3 h
  • Mode: Workshop or async
  • Participants: A facilitator with IBIS experience; two to eight participants with domain and architecture knowledge; a scribe who maintains the map and consolidates digitally afterwards.
  • Owner: A facilitator with IBIS experience
  • 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 Issue Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with three colors of notation (issue as question, position as statement, pro and contra argument symbols); symbols for pro (+) and contra (-); markers; timer; shared definition of IBIS notation.

Preparation

Display the issue at the top as a question. Show symbols for position and argument type. State the rule: each position answers one issue, every argument references one position.

Agenda

  1. Phase 1: Frame the issue (10-15 min) Owner: Facilitator Action: Formulate the main question as an open issue ("How should we solve X?"). Split broad scope into sub-issues. Place the top issue at the top of the board. Hint: Issues are open questions, not judgments. "Should we do X" is a judgment and should be reframed as "How can we achieve X given Y and Z?" Output: Issue Map

  2. Phase 2: Gather positions (20-30 min) Owner: Facilitator Action: Collect possible answers to the issue as positions (at least three). Use one clear sentence per position with a concrete answer. Hint: If only one position is named, the discussion is not open. The facilitator generates at least one counter-position with a devil's advocate role. Output: Positions

  3. Phase 3: Assign arguments (30-45 min) Owner: Facilitator Action: Collect pro and contra arguments for each position. Arguments can be data, experience, or constraints. Add arrows from argument to position and make pro/contra symbols visible. Hint: Some arguments apply to multiple positions. Add a separate arrow per relationship to avoid illegible maps. Output: Argument Notes

  4. Phase 4: Check relationships (20-30 min) Owner: Facilitator Action: Review the map together. Mark weak arguments. Note sub-issues that arise as new issues ("issue knot"). Hint: IBIS maps often produce issue knots that belong in separate sub-maps. Do not force all content into one map. Output: Issue Map

  5. Phase 5: Make a decision or keep open questions (15-20 min) Owner: Owner Action: Mark position(s) driving decisions. Add rationale in the Decision Log. Add owner and date for open sub-issues. Hint: IBIS is primarily documentation, not a decision engine. If no position dominates, pass decision to the decider with the map as an attachment. Output: Positions

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

Closeout

  • Update result artifact: Issue Map
  • 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

Issue Map: IBIS

Working Question

Which positions answer the central issue, and which arguments support or challenge each position?

Context

Central issue (question) as starting point; existing design docs or architecture decisions; list of existing discussion states; definition of what counts as argument (qualitative, quantitative).

Participants

  • Owner: A facilitator with IBIS experience
  • Participants: A facilitator with IBIS experience; two to eight participants with domain and architecture knowledge; a scribe who maintains the map and consolidates digitally afterwards.

Input

Whiteboard or Miro board with three colors of notation (issue as question, position as statement, pro and contra argument symbols); symbols for pro (+) and contra (-); markers; timer; shared definition of IBIS notation.

Template

IBIS Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Issue Map:
  • Positions:
  • Argument Notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Issue Map 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

IBIS Working Template

View templateCompact working template for IBIS with context, input, output artifacts, and next step.
canvas

ibis-working-template.md

Compact working template for IBIS with context, input, output artifacts, and next step.

IBIS Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Issue Map:
  • Positions:
  • Argument Notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Issue Map.
  • One map per issue with date. For new information or overturned decisions, create a follow-up map as v2; keep old positions marked as "rejected" with rationale.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet