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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Empathy Mapping
UX Research
Empathy Mapping
Affinity Diagramming
UX Research
Affinity Diagramming
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h30–60 min45–90 min60-120 min
Participantsdifferent
3-104-83-102-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesEmpathy Map, Assumptions List, Research GapsTheme clusters, Insight statements, Opportunity areasCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
SynthesisQualitativeWorkshop
SynthesisQualitativeRoot cause
ArchitectureCommunicationStakeholdersCanvas
Add more methods