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
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
Process Mapping method illustration showing its working structure
Operations
Process Mapping
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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
HighMediumLowLow
Timedifferent
2-4 h Analyse, laufend1-3 h45–75 min30-60 min
Participantsdifferent
3-123-10Team members involved3-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Constraint Map, Improvement Plan, Flow MetricsProcess Map, Handoff List, Improvement Backlog4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
OperationsConstraintsFlowImprovement
ProcessOperationsImprovement
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods