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 TRIZ | ![]() DevOps Blameless Postmortem | ![]() Innovation Brainstorming |
|---|---|---|---|
Purposedifferent | 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. | 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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | High | Medium | Low |
Timedifferent | 1-4 h | 30-90 min | 30-60 min |
Participantsdifferent | 2-8 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Postmortem Doc, Action Items, Timeline | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






