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 |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|
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. | 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
