View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Architecture Architecture Decision Record |  UX Research Customer Journey Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 15-45 min | 2-4 h |
Participantsdifferent | Ein Team plus Stakeholder | 1-3 | 4-10 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Team API Document | ADR File, Decision Log, Rationale | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | TeamAlignmentCommunicationService | ArchitectureRationaleDocumentationGovernance | JourneyServiceService design |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
