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 RAPID |  Architecture arc42 |  Architecture Request for Comments |
|---|---|---|---|---|
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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 0.5-2 Tage | 45-90 min | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 6-12 | 3-12 | 1-4 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | RAPID Role Map, Recommendation, Decision Log | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | Service designOperationsJourneyBlueprint | DecisionRolesGovernance | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance |