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 a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Affinity Diagramming
UX Research
Affinity Diagramming
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.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
MediumMediumLowLow
Timedifferent
2-4 h60-120 min45–90 min1-2 Tage
Participantsdifferent
4-102-83-101-4
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogCommunication Canvas, Stakeholder Messages, Architecture Communication PlanTheme clusters, Insight statements, Opportunity areasArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
JourneyServiceService design
ArchitectureCommunicationStakeholdersCanvas
SynthesisQualitativeRoot cause
ArchitectureDocumentationCommunication
Add more methods