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 Polarity Mapping |  Agile Example Mapping |  Delivery RAID Log |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-2 h | 30-60 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 3-12 | 3-7 | 1-3 maintaining, briefing for everyone | 3-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Example Map, Acceptance Criteria, Open Questions | RAID Log, Status Report Source | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingTradeoffsLeadership | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskTrackingStakeholdersGovernance | Systems thinkingFramingStakeholders |