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 Concierge MVP
Product Discovery
Concierge MVP
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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.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
LowMediumLow
Timedifferent
60-90 min1-4 Wochen60-90 min
Participantsdifferent
4-103-10 Kunden4-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentConcierge Learnings, Service Blueprint, MVP RisksAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
MVPValidationServiceDiscovery
RiskArchitectureWorkshopValidation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming