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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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.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.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 hAs needed30-60 min45-90 min
Participantsdifferent
3-104-153-104-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogIncident Log, Action Tracker, Stakeholder UpdatesEmotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement Actions
Tagsno overlap
ProcessOperationsImprovement
IncidentOperationsReliability
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
Add more methods