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 Runbook |  Domain Modeling EventStorming |  Knowledge Modeling Event Modeling |  UX Design Service Blueprinting |
|---|---|---|---|---|
Purposedifferent | 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. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 20-60 min | 2-8 h | 2-6 h | 0.5-2 Tage |
Participantsdifferent | 1-4 | 5-12 | 2-8 | 6-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Runbook, Checklist, Escalation Path | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Event Model, UI Flow, Commands, Read Models | Service Blueprint, Fail Points, Ownership Map |
Tagsno overlap | OperationsReliabilityDocumentation | Domain-Driven DesignEventsDiscoveryWorkshop | EventsBlueprintDomain-Driven DesignBehavior | Service designOperationsJourneyBlueprint |