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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Affinity Diagramming
UX Research
Affinity Diagramming
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception 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.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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 Tage1-2 h45–90 min1-2 h
Participantsdifferent
Internes Team3-103-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesArchitecture Canvas, Goals, Constraints, Quality AttributesTheme clusters, Insight statements, Opportunity areasInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ResearchCustomerSynthesis
CanvasArchitectureAlignmentWorkshop
SynthesisQualitativeRoot cause
AlignmentArchitectureCanvas
Add more methods