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 Risk Storming.
Architecture
Risk Storming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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.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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowLowMedium
Timedifferent
60-90 min60-90 min1-2 h1-2 h
Participantsdifferent
4-104-123-104-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentAnnotated Diagram, Prioritized Risk List, Action BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision Questions
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
RiskArchitectureWorkshopValidation
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
Add more methods