methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
A paper-based illustration representing Wardley Mapping with its core stages and visible working result.
Systems Thinking
Wardley Mapping
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
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.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
HighMediumMediumLow
Timedifferent
Mehrere Tage bis Wochen1-3 h3–4 h for initial assessment; preparation and deeper analysis additional20-45 min
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron2-101 or a small team; particularly suitable for 3–4 people1-10
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsWardley Map, Strategic Options, Evolution NotesLean 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 checksBehavior Over Time Graph, Trend Hypotheses, Key Events
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
StrategySystems thinkingDynamics
ArchitectureQualityRiskAssessmentLean
Systems thinkingPatternsDynamics
Add more methods