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 |  Architecture ARID (Active Reviews for Intermediate Designs) |  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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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–4 h review as a planning range; preparation and evaluation additional | 45-90 min |
Participantsdifferent | 3-12 | Designers, developers as users, and facilitation | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | ArchitectureEngineeringFeedbackValidationTasks | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
