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 Diary Study |  DevOps ChatOps |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen | Ongoing | 30-60 min | 45-90 min |
Participantsdifferent | 5-20 | 2-20 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Chat Transcript, Action Log, Automations | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | UX researchTrackingBehavior | CollaborationEngineeringIncident | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |