methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
HighMediumMediumLow
Timedifferent
1-4 h1-3 Tage1-3 h15-45 min
Participantsdifferent
3-81-41-81-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanArchitecture Views, Cross-view Notes, RationaleArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, Rationale
Tagsno overlap
RiskDecisionSensemaking
DocumentationStakeholdersArchitecture
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
Add more methods