View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Red Teaming | ![]() Knowledge Modeling Concept Mapping | ![]() Agile Example Mapping | ![]() Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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 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 | High | Medium | Low | Medium |
Timedifferent | 1-4 h | 1-2 h | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-8 | 1-8 | 3-7 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Concept Map, Relationship Labels, Knowledge Gaps | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | RiskDecisionSensemaking | KnowledgeConceptsMappingSensemaking | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |



