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 |  Decision Making Constraint Analysis |  Architecture arc42 |  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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 30-90 min | 1-2 Tage | 1-4 h |
Participantsdifferent | 4-10 | 2-8 | 1-4 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | JourneyServiceService design | ConstraintsDecisionPlanningOptions | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |