View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Service Blueprinting |  Product Discovery Kano Model |  Agile Start Stop Continue |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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 features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 0.5-2 Tage | 1-2 Tage | 30-60 min | 45-90 min |
Participantsdifferent | 6-12 | 10-50 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Kano Matrix, Feature Classes, Priority Themes | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | Service designOperationsJourneyBlueprint | SatisfactionPrioritizationCustomer | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |