View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Bottleneck Analysis | ![]() Agile 4Ls Retrospective | ![]() Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 45–75 min | 45-90 min |
Participantsdifferent | 3-8 | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | 4Ls Board, Learning Themes, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | FlowMeasurementConstraints | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






