Compare

View methods side by side.

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

Selected:ARID (Active Reviews for Intermediate Designs)Game Day Causal Factor Analysis Causal Loop Diagram

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	DevOps Game Day	Operations Causal Factor Analysis	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.	In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.	For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.	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	Medium	High	High	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	Halber Tag	2-6 h	1-3 h
Participantsdifferent	Designers, developers as users, and facilitation	5-20	3-10	2-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Simulation Notes, Gaps List, Updated Runbooks	Event Timeline, Causal Factor Chart, Cause List, Corrective Actions	Causal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ResilienceOperationsIncident	CausalityIncidentRoot causeTimeline	FeedbackSystems thinkingCausalityDynamics

Add more methods