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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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 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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-4 h1-2 h1-3 h1-2 h
Participantsdifferent
4-103-105-304-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority AreasAlignment Map, Open Issues, Decision Questions
Tagsno overlap
JourneyServiceService design
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods