View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Customer Journey Mapping |  Architecture Software Architecture Canvas |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|
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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 2-4 h | 1-2 h | Half day |
Participantsdifferent | 4-10 | 3-10 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | JourneyServiceService design | CanvasArchitectureAlignmentWorkshop | TeamAlignmentCollaborationOrganization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
