View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Mad Sad Glad | ![]() UX Design Service Blueprinting | ![]() Agile Start Stop Continue | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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 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 | Low | High | Low | Low |
Timedifferent | 30-60 min | 0.5-2 Tage | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 6-12 | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Service Blueprint, Fail Points, Ownership Map | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | Service designOperationsJourneyBlueprint | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |



