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 |  Knowledge Modeling Domain Storytelling |  Knowledge Modeling Teach-back |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-2 h | 5-20 min | 45–75 min |
Participantsdifferent | 3-8 | 2-8 | 2-8 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Domain Story, Glossary Notes, Process Narrative | Understanding Check, Clarification Notes, Learning Gaps | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | FlowMeasurementConstraints | KnowledgeDomain-Driven DesignProcess | LearningUnderstandingCommunication | RetrospectiveLearningReflectionTeam |