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 Research User Interviews | ![]() Agile 4Ls Retrospective | ![]() Agile Start Stop Continue | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–60 min per interview | 45–75 min | 30-60 min | 30-60 min |
Participantsdifferent | 1 participant per interview | Team members involved | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | QualitativeResearchCustomerDiscovery | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection |



