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:ABC Analysis ARID (Active Reviews for Intermediate Designs)Consensus Workshop Software Architecture Canvas

Criterion	Operations ABC Analysis	Architecture ARID (Active Reviews for Intermediate Designs)	Facilitation Consensus Workshop	Architecture Software Architecture Canvas
Purposedifferent	With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.	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.	When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.	The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.
Complexitydifferent	Low	Medium	Medium	Low
Timedifferent	30-60 min	2–4 h review as a planning range; preparation and evaluation additional	1-3 h	1-2 h
Participantsdifferent	1-5	Designers, developers as users, and facilitation	5-30	3-10
Formatdifferent	Async	Workshop + async	Workshop	Workshop
Outputdifferent	ABC Classification, Focus Rules, Control List	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Consensus Clusters, Theme Titles, Priority Areas	Architecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap	PrioritizationOperationsPortfolio	ArchitectureEngineeringFeedbackValidationTasks	FacilitationConsensusWorkshopAlignment	CanvasArchitectureAlignmentWorkshop

Add more methods