View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Runbook | ![]() Agile Start Stop Continue | ![]() Operations After-Action Review | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 | 20-60 min | 30-60 min | 20-45 min | 30-60 min |
Participantsdifferent | 1-4 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Runbook, Checklist, Escalation Path | Start Stop Continue Board, Improvement Actions | Lessons learned, Action items, Event summary | Emotion Board, Themes, Action Items |
Tagsno overlap | OperationsReliabilityDocumentation | RetrospectiveImprovementTeamReflection | LearningOperationsImprovement | RetrospectiveTeamReflection |



