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:Standard Work Analysis Risk Storming Architecture Decision Record ARID (Active Reviews for Intermediate Designs)

Criterion	Operations Standard Work Analysis	Architecture Risk Storming	Architecture Architecture Decision Record	Architecture ARID (Active Reviews for Intermediate Designs)
Purposedifferent	When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.	Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.	An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.	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.
Complexitydifferent	Medium	Low	Low	Medium
Timedifferent	1-3 h	60-90 min	15-45 min	2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent	2-6	4-12	1-3	Designers, developers as users, and facilitation
Formatdifferent	Workshop	Workshop	Async	Workshop + async
Outputdifferent	Standard Work Sheet, Deviation List, Improved Standard, Training Needs	Annotated Diagram, Prioritized Risk List, Action Backlog	ADR File, Decision Log, Rationale	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap	LeanProcessQuality	RiskArchitectureWorkshopValidation	ArchitectureRationaleDocumentationGovernance	ArchitectureEngineeringFeedbackValidationTasks

Add more methods