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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighMediumHighMedium
Timedifferent
0.5-2 Tage30-90 minMehrere Tage bis Wochen2-4 h
Participantsdifferent
6-123-122-62-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Service Blueprint, Fail Points, Ownership MapPostmortem Doc, Action Items, TimelineMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Service designOperationsJourneyBlueprint
Site Reliability EngineeringIncidentLearningReliability
Root causeSafetySystemicIncident
Root causeSafetyIncident
Add more methods