View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  Knowledge Modeling IBIS |  Decision Making Cynefin Workshop |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 1-3 h | 60-180 min | 20-40 min pro Story |
Participantsdifferent | 3-7 | 2-8 | 4-20 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Issue Map, Positions, Argument Notes | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RationaleKnowledgeDecision | ComplexitySensemakingDecision | AgileRequirementsRefinementBehavior-Driven Development |