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 System Dynamics Simulation |  Systems Thinking Wardley Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. | 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. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 2-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | Wardley Map, Strategic Options, Evolution Notes | 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 |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | StrategySystems thinkingDynamics | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
