View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  DevOps Blameless Postmortem |  Agile Start Stop Continue |  Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | 30-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 3-12 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Postmortem Doc, Action Items, Timeline | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | TeamAlignmentCollaboration | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection |