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 two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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 Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.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.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 Tage60-90 min15-45 min1-3 h
Participantsdifferent
Internes Team4-101-31-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesProblem Cluster, Prioritized Challenge, ExperimentADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ResearchCustomerSynthesis
FacilitationDecisionProblem solvingWorkshop
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods