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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.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 dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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
MediumLowMediumLow
Timedifferent
30-90 min30-60 min15-60 min je Zyklus30-60 min
Participantsdifferent
3-123-121-83-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement ActionsSituation Assessment, Decision Loop, Action UpdatesEmotion Board, Themes, Action Items
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
DecisionChangeLearningStrategy
RetrospectiveTeamReflection
Add more methods