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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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
MediumMediumLowLow
Timedifferent
As needed1-3 h30-60 min30-60 min
Participantsdifferent
4-153-103-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesProcess Map, Handoff List, Improvement BacklogStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
IncidentOperationsReliability
ProcessOperationsImprovement
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods