View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Rich Picture |  DevOps Blameless Postmortem |  Knowledge Modeling IBIS |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | 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. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30-90 min | 30-90 min | 1-3 h | 20-60 min |
Participantsdifferent | 2-10 | 3-12 | 2-8 | 1 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Rich Picture, Problem Framing Notes | Postmortem Doc, Action Items, Timeline | Issue Map, Positions, Argument Notes | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | Site Reliability EngineeringIncidentLearningReliability | RationaleKnowledgeDecision | LearningKnowledgeUnderstanding |