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
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Risk Storming.
Architecture
Risk Storming
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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
LowMediumLowHigh
Timedifferent
60-90 min1-3 h60-90 min1-4 h
Participantsdifferent
4-101-84-123-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentArgument Map, Evidence Gaps, Decision RationaleAnnotated Diagram, Prioritized Risk List, Action BacklogChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
SensemakingDecisionRationale
RiskArchitectureWorkshopValidation
RiskDecisionSensemaking
Add more methods