View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Operations Runbook |  Operations After-Action Review |
|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 2-6 h | 20-60 min | 20-45 min |
Participantsdifferent | 2-8 | 1-4 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Runbook, Checklist, Escalation Path | Lessons learned, Action items, Event summary |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | OperationsReliabilityDocumentation | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
