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 Scrum |  Knowledge Modeling Concept Mapping |  Decision Making Red Teaming |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-2 h | 1-4 h | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Concept Map, Relationship Labels, Knowledge Gaps | Challenge Findings, Risk Register, Mitigation Plan | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | AgileIterationCadence | KnowledgeConceptsMappingSensemaking | RiskDecisionSensemaking | AssumptionsRiskDecisionDiscovery |