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 | ![]() Operations A3 Problem Solving | ![]() 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | 45-90 min | 1-4 h |
Participantsdifferent | 6-12 | 2-5 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | A3 Report, Action Plan, Root Cause Analysis | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Service designOperationsJourneyBlueprint | LeanProblem solvingCoachingOperations | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






