View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps ChatOps |  Growth Growth Experiment |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment. | 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 | Ongoing | 1-2 Wochen | 30-60 min | 45-90 min |
Participantsdifferent | 2-20 | 1-6 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Chat Transcript, Action Log, Automations | Experiment card, Result summary, Next bet | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | CollaborationEngineeringIncident | MarketingGrowthExperimentsLearning | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |