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 |  Architecture Request for Comments |  Systems Thinking Soft Systems Methodology |  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. | 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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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 | Medium | High | Medium |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 0.5-3 Tage | 1-3 h |
Participantsdifferent | 3-12 | 3-20 Reviewer | 5-15 | 1-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureDecisionAsyncGovernance | Soft systemsComplexitySensemakingSystems thinking | SensemakingDecisionRationale |