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 |  Team Design Team API |  Architecture Architecture Decision Record |  Architecture C4 Model |
|---|---|---|---|---|
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. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | Half day initial, dann laufend | 15-45 min | 1-4 h |
Participantsdifferent | 4-10 | Ein Team plus Stakeholder | 1-3 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Team API Document | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | JourneyServiceService design | TeamAlignmentCommunicationService | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |