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
Empathy Mapping
UX Research
Empathy Mapping
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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 lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 Tage30–60 min2-4 h1-2 h
Participantsdifferent
Internes Team4-85-153-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesEmpathy Map, Assumptions List, Research GapsQuality Scenarios, Priority List, Architecture ConcernsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ResearchCustomerSynthesis
SynthesisQualitativeWorkshop
RequirementsArchitectureWorkshop
CanvasArchitectureAlignmentWorkshop
Add more methods