View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Current Reality TreeArchitecture Decision RecordRequest for CommentsTheory of Constraints Thinking Process
| Criterion |  Systems Thinking Current Reality Tree |  Architecture Architecture Decision Record |  Architecture Request for Comments |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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 | High | Low | Medium | High |
Timedifferent | 2-6 h | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 0.5-3 Tage |
Participantsdifferent | 3-8 | 1-3 | 3-20 Reviewer | 4-10 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Current Reality Tree, Core Problems, Intervention Ideas | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | Systems thinkingRoot causeConstraintsCausality | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | Theory of ConstraintsConstraintsSystems thinkingCausality |