View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Innovation Lotus Blossom |  Domain Modeling EventStorming |
|---|---|---|---|
Purposedifferent | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-90 min | 45-90 min | 2-8 h |
Participantsdifferent | 3-12 | 3-10 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Lotus Diagram, Idea Themes, Shortlist | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationCreativityDivergenceWorkshop | Domain-Driven DesignEventsDiscoveryWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
