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
A paper-based illustration representing Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Empathy Mapping
UX Research
Empathy Mapping
Affinity Diagramming
UX Research
Affinity Diagramming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.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.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 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.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min30–60 min45–90 min1-2 h
Participantsdifferent
3-104-83-103-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Context canvas, Open questions, Shared context notesEmpathy Map, Assumptions List, Research GapsTheme clusters, Insight statements, Opportunity areasArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ContextFramingRequirementsCanvas
SynthesisQualitativeWorkshop
SynthesisQualitativeRoot cause
CanvasArchitectureAlignmentWorkshop
Add more methods