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 for Theory of Constraints.
Operations
Theory of Constraints
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck 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.For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.
Complexitydifferent
HighHighLowMedium
Timedifferent
0.5-2 Tage2-4 h Analyse, laufend20-45 min1-3 h
Participantsdifferent
6-123-123-123-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Service Blueprint, Fail Points, Ownership MapConstraint Map, Improvement Plan, Flow MetricsLessons learned, Action items, Event summaryBottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures
Tagsno overlap
Service designOperationsJourneyBlueprint
OperationsConstraintsFlowImprovement
LearningOperationsImprovement
FlowMeasurementConstraints
Add more methods