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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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.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 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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 Tage15-45 min1-2 h1-3 Tage
Participantsdifferent
Internes Team1-34-121-4
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesADR File, Decision Log, RationaleAlignment Map, Open Issues, Decision QuestionsArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
ResearchCustomerSynthesis
ArchitectureRationaleDocumentationGovernance
AlignmentStakeholdersStrategyFacilitation
DocumentationStakeholdersArchitecture
Add more methods