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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
HighLowLowMedium
Timedifferent
0.5-2 Tage30-120 min20-45 min1-3 h
Participantsdifferent
6-122-63-123-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapObservation Notes, Improvement IdeasLessons learned, Action items, Event summaryProcess Map, Handoff List, Improvement Backlog
Tags1 shared
Service designOperationsJourneyBlueprint
LeanObservationProcessOperations
LearningOperationsImprovement
ProcessOperationsImprovement
Add more methods