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 arc42 |  Knowledge Modeling Knowledge Mapping |  Decision Making Red Teaming |
|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 | Low | Medium | High |
Timedifferent | 1-2 Tage | 1-3 h | 1-4 h |
Participantsdifferent | 1-4 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | KnowledgeMappingRisk | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
