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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.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.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
LowHighLowLow
Timedifferent
60-90 min1-4 Wochen15-45 min60-90 min
Participantsdifferent
4-101-61-34-12
Formatdifferent
WorkshopAsyncAsyncWorkshop
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentExperiment results, Decision log, Learning summaryADR File, Decision Log, RationaleAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
ExperimentsGrowthAnalyticsValidation
ArchitectureRationaleDocumentationGovernance
RiskArchitectureWorkshopValidation
Add more methods