View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Argument Mapping | ![]() Architecture Request for Comments | ![]() Systems Thinking Causal Loop Diagram | ![]() Systems Thinking Behavior Over Time Graph |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 20-45 min |
Participantsdifferent | 1-8 | 3-20 Reviewer | 2-8 | 1-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | 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 |
Tagsno overlap | SensemakingDecisionRationale | ArchitectureDecisionAsyncGovernance | FeedbackSystems thinkingCausalityDynamics | Systems thinkingPatternsDynamics |



