View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsCausal Loop DiagramBehavior Over Time GraphArchitecture Decision Record
| Criterion |  Architecture Request for Comments |  Systems Thinking Causal Loop Diagram |  Systems Thinking Behavior Over Time Graph |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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 Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. | A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 20-45 min | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-10 | 1-3 |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Causal Loop Diagram, Feedback Notes, Leverage Points | Behavior Over Time Graph, Trend Hypotheses, Key Events | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | FeedbackSystems thinkingCausalityDynamics | Systems thinkingPatternsDynamics | ArchitectureRationaleDocumentationGovernance |