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 Design Service Blueprinting |  Decision Making Argument Mapping |  Architecture C4 Model |
|---|---|---|---|
Purposedifferent | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 | High | Medium | Low |
Timedifferent | 0.5-2 Tage | 1-3 h | 1-4 h |
Participantsdifferent | 6-12 | 1-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Argument Map, Evidence Gaps, Decision Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Service designOperationsJourneyBlueprint | SensemakingDecisionRationale | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
