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
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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.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.
Complexitydifferent
HighLowMediumMedium
Timedifferent
1-4 h30-90 min1-3 Wochen vom Draft bis zur Entscheidung1-3 h
Participantsdifferent
3-82-83-20 Reviewer1-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArgument Map, Evidence Gaps, Decision Rationale
Tags1 shared
RiskDecisionSensemaking
ConstraintsDecisionPlanningOptions
ArchitectureDecisionAsyncGovernance
SensemakingDecisionRationale
Add more methods