View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() DevOps Blameless Postmortem | ![]() Decision Making Assumption Surfacing | ![]() Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 30-90 min | 45-90 min | 20-60 min |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Issue Map, Positions, Argument Notes | Postmortem Doc, Action Items, Timeline | Assumption List, Critical Assumptions, Learning Plan | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | RationaleKnowledgeDecision | Site Reliability EngineeringIncidentLearningReliability | AssumptionsRiskDecisionDiscovery | LearningKnowledgeUnderstanding |



