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 Incident Timeline Analysis | ![]() Systems Thinking Soft Systems Methodology |
|---|---|---|---|
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. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30-90 min | 60-180 min | 0.5-3 Tage |
Participantsdifferent | 2-10 | 3-10 | 5-15 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Rich Picture, Problem Framing Notes | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Rich Picture, Root Definitions, Conceptual Models, Change Agenda |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | IncidentTimelineSite Reliability Engineering | Soft systemsComplexitySensemakingSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






