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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.
Complexitydifferent
LowHighHighLow
Timedifferent
60-90 min1-4 h1-4 Wochen60-90 min
Participantsdifferent
4-103-81-64-12
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentChallenge Findings, Risk Register, Mitigation PlanExperiment results, Decision log, Learning summaryAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
RiskDecisionSensemaking
ExperimentsGrowthAnalyticsValidation
RiskArchitectureWorkshopValidation
Add more methods