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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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
LowLowMediumLow
Timedifferent
20-60 min30-60 minAs needed30-60 min
Participantsdifferent
1-43-124-153-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathStart Stop Continue Board, Improvement ActionsIncident Log, Action Tracker, Stakeholder UpdatesEmotion Board, Themes, Action Items
Tagsno overlap
OperationsReliabilityDocumentation
RetrospectiveImprovementTeamReflection
IncidentOperationsReliability
RetrospectiveTeamReflection
Add more methods