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 |  Agile Start Stop Continue |  Decision Making Force Field Analysis |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Ongoing | 30-60 min | 45-90 min | 30-60 min |
Participantsdifferent | 2-20 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Chat Transcript, Action Log, Automations | Start Stop Continue Board, Improvement Actions | Force Field Map, Change Levers, Risk Notes | Emotion Board, Themes, Action Items |
Tagsno overlap | CollaborationEngineeringIncident | RetrospectiveImprovementTeamReflection | ChangeDecisionStrategy | RetrospectiveTeamReflection |