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 |  Knowledge Modeling Event Modeling |  Innovation Lotus Blossom |
|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-90 min | 2-6 h | 45-90 min |
Participantsdifferent | 3-12 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Event Model, UI Flow, Commands, Read Models | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | EventsBlueprintDomain-Driven DesignBehavior | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
