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.

Selected:Service BlueprintingBlameless PostmortemStart Stop ContinueLearning Review
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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Learning Review.
Operations
Learning Review
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
HighMediumLowMedium
Timedifferent
0.5-2 Tage30-90 min30-60 min1-3 h
Participantsdifferent
6-123-123-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapPostmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
Service designOperationsJourneyBlueprint
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
Add more methods