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 Current Reality Tree | ![]() Architecture Request for Comments | ![]() Architecture C4 Model | ![]() 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 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Medium | Low | High |
Timedifferent | 2-6 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 0.5-3 Tage |
Participantsdifferent | 3-8 | 3-20 Reviewer | 1-5 | 4-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Current Reality Tree, Core Problems, Intervention Ideas | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | Systems thinkingRoot causeConstraintsCausality | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization | Theory of ConstraintsConstraintsSystems thinkingCausality |



