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 Concept Mapping | ![]() Agile Specification by Example | ![]() Knowledge Modeling IBIS | ![]() Decision Making Cynefin Workshop |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | 60-90 min pro Feature | 1-3 h | 60-180 min |
Participantsdifferent | 1-8 | 3-6 | 2-8 | 4-20 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Example Table, Acceptance Tests | Issue Map, Positions, Argument Notes | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | AgileRequirementsExamplesBehavior-Driven Development | RationaleKnowledgeDecision | ComplexitySensemakingDecision |



