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 Ideal Days |
|---|---|---|---|
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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 15-60 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 2-9 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RAID Log, Status Report Source | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskTrackingStakeholdersGovernance | EstimationEffortAgile |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
