View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Knowledge Modeling Concept Mapping |  Decision Making Assumption Surfacing |  Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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. | 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 | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 45-90 min | 1-4 h |
Participantsdifferent | 3-20 Reviewer | 1-8 | 2-8 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Concept Map, Relationship Labels, Knowledge Gaps | Assumption List, Critical Assumptions, Learning Plan | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | KnowledgeConceptsMappingSensemaking | AssumptionsRiskDecisionDiscovery | RiskDecisionSensemaking |