methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
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.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.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
MediumMediumLowLow
Timedifferent
30-90 min45-90 min30-60 min45-90 min
Participantsdifferent
3-123-83-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsEmotion Board, Themes, Action ItemsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
Systems thinkingFramingStakeholders
RetrospectiveTeamReflection
AlignmentStakeholdersTeam
Add more methods