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 |  Decision Making Red Teaming |  Architecture Request for Comments |  Decision Making Argument Mapping |
|---|---|---|---|---|
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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 h | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h |
Participantsdifferent | 3-12 | 3-8 | 3-20 Reviewer | 1-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Challenge Findings, Risk Register, Mitigation Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskDecisionSensemaking | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale |