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
Affinity Diagramming
UX Research
Affinity Diagramming
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–90 min60-120 min1-2 h1-2 Tage
Participantsdifferent
3-102-83-101-4
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Theme clusters, Insight statements, Opportunity areasCommunication Canvas, Stakeholder Messages, Architecture Communication PlanArchitecture Canvas, Goals, Constraints, Quality AttributesArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
SynthesisQualitativeRoot cause
ArchitectureCommunicationStakeholdersCanvas
CanvasArchitectureAlignmentWorkshop
ArchitectureDocumentationCommunication
Add more methods