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 |  Architecture Request for Comments |  Architecture Architecture Decision Record |  Decision Making Argument Mapping |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 0.5-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 1-3 h |
Participantsdifferent | 6-12 | 3-20 Reviewer | 1-3 | 1-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale |