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
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
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.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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
HighLowLowMedium
Timedifferent
0.5-2 Tage45–75 min30-60 min1-3 h
Participantsdifferent
6-12Team members involved3-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership Map4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
Service designOperationsJourneyBlueprint
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
Add more methods