View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Causal Loop DiagramLASR (Lightweight Approach for Software Reviews)Architecture Communication CanvasStock and Flow Diagram
| Criterion |  Systems Thinking Causal Loop Diagram |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Communication Canvas |  Systems Thinking Stock and Flow Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min | 2-6 h |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Causal Loop Diagram, Feedback Notes, Leverage Points | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | FeedbackSystems thinkingCausalityDynamics | ArchitectureQualityRiskAssessmentLean | ArchitectureCommunicationStakeholdersCanvas | DynamicsSimulationFeedbackSystems thinking |