methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
HighLowHighLow
Timedifferent
0.5-2 Tage30 min Setup, dann laufend1-6 Wochen30-60 min
Participantsdifferent
6-121-3 maintaining, briefing for everyone4-102-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapRAID Log, Status Report Source8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Service designOperationsJourneyBlueprint
RiskTrackingStakeholdersGovernance
QualityProblem solvingRoot cause
Root causeQualityOperations
Add more methods