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 | ![]() Architecture Architecture Decision Record | ![]() Delivery RAID Log | ![]() Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-90 min | 15-45 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 2-10 | 1-3 | 1-3 maintaining, briefing for everyone | 3-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Rich Picture, Problem Framing Notes | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | Systems thinkingFramingStakeholders |



