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
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
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Purposedifferent
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.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.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
MediumHighMediumMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional2-6 h2-4 h1-3 h
Participantsdifferent
Designers, developers as users, and facilitation1-62-62-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsStock and Flow Model, Dynamics Notes, Simulation HypothesesBarrier Inventory, Failure Analysis per Barrier, Action BacklogCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
DynamicsSimulationFeedbackSystems thinking
Root causeSafetyIncident
FeedbackSystems thinkingCausalityDynamics
Add more methods