IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.
Knowledge Modeling Mapping tool
IBIS
Maps contested questions so positions, arguments, and decision status remain traceable.
IBIS represents deliberation as a network of Issues, Positions and Arguments. Each position answers a specific issue; pro and con arguments attach to one position. The map preserves what was selected, rejected or left open.
Which position answers the Issue most convincingly given the current arguments?
- Participants
- 2-8 participants
- Time
- 60–120 minutes for an initial map; continue when new arguments emerge

Issue
Frame the Issue
State an open, contested question that Positions can answer.
Positions
Lay out Positions
Capture each serious answer to the Issue as its own Position.
Arguments
Connect Arguments
Attach testable reasons as Pro or Con to the Position they address.
Sub-Issues
Open follow-up Issues
Model unresolved terms, conflicts and information needs as new Issues.
Status
Mark decision status
Mark selected, rejected and open Positions with the governing rationale.
Add new questions as Issues, attach new evidence to existing Arguments and update the status of affected Positions.
A good fit when
For complex design, architecture or policy questions with several plausible positions and a need for durable rationale.
Ideal for
- Design Rationale
- Architecture Decisions
- Policy Discussions
Not good for
- Simple task planning
- Ideation without an argument structure
Outputs

IBIS map
Linked Issues, Positions and Pro and Con Arguments.

Decision state
Status, rationale, open sub-issues and agreed review triggers.
IBIS · Issue Map
Fictional example
Typed entries keep the question, alternatives, reasons and decision state connected.
Issue
What open question must be decided? Add scope, owner and status.
Should the training provider confirm course bookings immediately?
Positions
What concrete answers are available? Write one assertion per Position.
A: confirm immediately; B: review manually first.
Arguments
What reasons support or object to which Position? Add source or assumption status.
Pro A: 78% compliant. Con A: seat limits may be exceeded.
Follow-up Issues
Which decision-relevant sub-questions arise from Positions or Arguments?
Can seat limits be checked automatically before confirmation?
Status
Which Position was selected by whom, under what conditions and with what review trigger?
Pilot A after an automated seat check; review after 100 bookings.
The example is a small excerpt. In a real map, Arguments may generate additional Issues.
First step
State one genuinely contested question as an Issue and define the decision boundary.
Deep dive
The team first formulates the central question as an issue. Then possible answers are collected as ideas and linked with pro and con arguments. This keeps the decision path transparent even when the situation is contradictory.
IBIS works well because it breaks discussions down into issues, positions, and arguments, exposing decision logic as a result. The benefit arises when controversial points are cleanly separated in language and reasoning is visibly attached to exactly one statement. Whoever uses the method well pays attention to sharply distinct questions, traceable counterarguments, and documented conclusions, so debates don't start over from scratch later.
Prepare a guiding question that works as a genuine decision problem, and introduce the team to the three building blocks early, so no mixed forms emerge. It becomes especially important when opinions show up disguised as facts; then they should immediately be recategorized as a position or an argument. In the end, a visible decision or a marked remaining uncertainty tied to the next appointment is needed.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
IBIS: WorksheetState one genuinely contested question as an Issue and define the decision boundary.markdown
ibis-working-template.md
State one genuinely contested question as an Issue and define the decision boundary.
IBIS: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete workflow Time: 60–120 minutes for an initial map; continue when new arguments emerge
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared map, decision question, known options, evidence, criteria and source links.
- Roles: Issue owner, participants with distinct perspectives and a mapper who maintains consistent links.
- Advance information: Decision boundary, existing options, known facts and prior partial decisions.
- Overall time needed: 60–120 minutes for an initial map; continue when new arguments emerge
- Setup: Define the Issue, Position, Pro and Con notation; give every element a stable label and source.
Prepare for the work steps
Issue: Frame the Issue
- Trigger and decision context
- Mandate and constraints
Positions: Lay out Positions
- Issue node
- Proposals and counterproposals
Arguments: Connect Arguments
- Positions
- Evidence, criteria and experience
Sub-Issues: Open follow-up Issues
- Argument network
- Conflicts and missing evidence
Status: Mark decision status
- Complete IBIS map
- Mandate and decision criteria
IBIS · Issue Map
Issue
What open question must be decided? Add scope, owner and status.
...
Positions
What concrete answers are available? Write one assertion per Position.
...
Arguments
What reasons support or object to which Position? Add source or assumption status.
...
Follow-up Issues
Which decision-relevant sub-questions arise from Positions or Arguments?
...
Status
Which Position was selected by whom, under what conditions and with what review trigger?
...
Type entries, assign stable IDs and document the direction of every relationship.
Issue: Frame the Issue
Expected artifact: Issue node
Question, scope, owner and status
Entry:
...
- Can at least two distinct answers be stated?
- Is the question within the mandate?
Positions: Lay out Positions
Expected artifact: Position nodes
One assertion per Position
Entry:
...
- Does every Position answer the Issue?
- Are materially different alternatives separate?
Arguments: Connect Arguments
Expected artifact: Pro and Con Arguments
Claim, target, source and direction
Entry:
...
- Is the direction of every link explicit?
- Can readers distinguish facts, judgements and assumptions?
Sub-Issues: Open follow-up Issues
Expected artifact: Linked sub-Issues
Question, trigger, owner and due date
Entry:
...
- Could the answer change a Position?
- Is the origin of the sub-Issue visible?
Status: Mark decision status
Expected artifact: Statused IBIS map
Decision, rationale, conditions and review
Entry:
...
- Do rejected Positions and Arguments remain readable?
- Is it clear who decided and when to revisit?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/ibis/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Instead of IBIS, when you want to keep arguments and counterarguments apart with a clear reasoning structure.

Uses a structured proposal and review process to make non-trivial technical or product changes discussable and decidable.

Maps critical knowledge, knowledge holders, and gaps so handovers and transfer can be planned deliberately.

Sorts knowledge into Projects, Areas, Resources, and Archive so personal knowledge work stays easier to steer.

Translates domain knowledge into a narrated situation where terms, relationships, and rules are checked together.

Forces complex content into simple language and immediately reveals which knowledge gaps still need closing.
Constraints and origin
Profile
- Method form
- Mapping tool
- Participants
- 2-8
- Time
- 1-3 h
- Maturity
- Canonical
- Origin
- Horst Rittel and Werner Kunz

