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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing Wardley Mapping with its core stages and visible working result.
Systems Thinking
Wardley Mapping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Purposedifferent
When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.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.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
HighMediumMediumHigh
Timedifferent
1-4 Wochen1-3 h2–4 h review as a planning range; preparation and evaluation additional2-6 h
Participantsdifferent
1-62-10Designers, developers as users, and facilitation1-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryWardley Map, Strategic Options, Evolution NotesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsStock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
StrategySystems thinkingDynamics
ArchitectureEngineeringFeedbackValidationTasks
DynamicsSimulationFeedbackSystems thinking
Add more methods