View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Behavior Over Time GraphARID (Active Reviews for Intermediate Designs)Assumption MappingCausal Loop Diagram
| Criterion |  Systems Thinking Behavior Over Time Graph |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-45 min | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min | 1-3 h |
Participantsdifferent | 1-10 | Designers, developers as users, and facilitation | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Behavior Over Time Graph, Trend Hypotheses, Key Events | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Systems thinkingPatternsDynamics | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation | FeedbackSystems thinkingCausalityDynamics |