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 Example Mapping |  Decision Making Cynefin Workshop |  Agile Acceptance Criteria 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 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. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 30-60 min | 60-180 min | 20-40 min pro Story |
Participantsdifferent | 1-8 | 3-7 | 4-20 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Example Map, Acceptance Criteria, Open Questions | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Acceptance Criteria, Story Update |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ComplexitySensemakingDecision | AgileRequirementsRefinementBehavior-Driven Development |