View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking CATWOE Analysis | ![]() Agile Mad Sad Glad | ![]() DevOps Blameless Postmortem | ![]() Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 45-90 min | 30-60 min | 30-90 min | 45-90 min |
Participantsdifferent | 3-8 | 3-10 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Emotion Board, Themes, Action Items | Postmortem Doc, Action Items, Timeline | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | Systems thinkingFramingStakeholders | RetrospectiveTeamReflection | Site Reliability EngineeringIncidentLearningReliability | AlignmentStakeholdersTeam |



