View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Polarity MappingRequest for CommentsCurrent Reality TreeTheory of Constraints Thinking Process
| Criterion |  Systems Thinking Polarity Mapping |  Architecture Request for Comments |  Systems Thinking Current Reality Tree |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
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. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 2-6 h | 0.5-3 Tage |
Participantsdifferent | 3-12 | 3-20 Reviewer | 3-8 | 4-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Current Reality Tree, Core Problems, Intervention Ideas | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureDecisionAsyncGovernance | Systems thinkingRoot causeConstraintsCausality | Theory of ConstraintsConstraintsSystems thinkingCausality |