View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() Agile Acceptance Criteria Workshop | ![]() Decision Making Argument Mapping | ![]() Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 20-40 min pro Story | 1-3 h | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 3-6 | 1-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Acceptance Criteria, Story Update | Argument Map, Evidence Gaps, Decision Rationale | Example Table, Acceptance Tests |
Tagsno overlap | RationaleKnowledgeDecision | AgileRequirementsRefinementBehavior-Driven Development | SensemakingDecisionRationale | AgileRequirementsExamplesBehavior-Driven Development |



