View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  UX Design Service Blueprinting |  Operations Kepner-Tregoe |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Low | High | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 0.5-2 Tage | 2-8 h | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 6-12 | 2-8 | 2-5 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Service Blueprint, Fail Points, Ownership Map | Problem Analysis, Decision Analysis, Risk Plan | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Service designOperationsJourneyBlueprint | Problem solvingRoot causeDecisionOperations | LeanProblem solvingCoachingOperations |