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 Constraint Analysis.
Decision Making
Constraint Analysis
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 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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
MediumLowLowLow
Timedifferent
30-90 min30-90 min30-60 min30-60 min
Participantsdifferent
3-122-83-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ConstraintsDecisionPlanningOptions
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods