View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Contradiction Analysis |  DevOps Game Day |  DevOps Blameless Postmortem |  Innovation TRIZ |
|---|---|---|---|---|
Purposedifferent | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 60-120 min | Halber Tag | 30-90 min | 1-4 h |
Participantsdifferent | 2-8 | 5-20 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Simulation Notes, Gaps List, Updated Runbooks | Postmortem Doc, Action Items, Timeline | Contradiction Statement, Inventive Principles, Solution Concepts |
Tagsno overlap | ContradictionsInnovationProblem solving | ResilienceOperationsIncident | Site Reliability EngineeringIncidentLearningReliability | InnovationProblem solvingContradictionsCreativity |