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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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.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'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
HighLowMediumLow
Timedifferent
Halber Tag30-60 min1-3 h30-60 min
Participantsdifferent
5-203-123-103-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksStart Stop Continue Board, Improvement ActionsProcess Map, Handoff List, Improvement BacklogEmotion Board, Themes, Action Items
Tagsno overlap
ResilienceOperationsIncident
RetrospectiveImprovementTeamReflection
ProcessOperationsImprovement
RetrospectiveTeamReflection
Add more methods