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 |  Architecture Risk Storming |
|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
