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 |  Agile Example Mapping |  Decision Making Argument Mapping |
|---|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 h | 60-90 min pro Feature | 30-60 min | 1-3 h |
Participantsdifferent | 1-8 | 3-6 | 3-7 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | SensemakingDecisionRationale |