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
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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.For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2-4 h1-3 h1-2 h1-3 h
Participantsdifferent
4-103-83-105-30
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
JourneyServiceService design
FlowMeasurementConstraints
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
Add more methods