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 Specification by Example | ![]() Knowledge Modeling Concept Mapping | ![]() Decision Making Red Teaming |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 60-90 min pro Feature | 1-2 h | 1-4 h |
Participantsdifferent | 3-6 | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Concept Map, Relationship Labels, Knowledge Gaps | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | KnowledgeConceptsMappingSensemaking | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






