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)TOWS Matrix Hypothesis-Driven Troubleshooting GAP Analysis

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Business Strategy TOWS Matrix	Engineering Hypothesis-Driven Troubleshooting	Business Strategy GAP Analysis
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.	The TOWS Matrix connects internal strengths and weaknesses with external opportunities and threats into action-oriented strategies. It goes a step further than a pure stocktaking.	When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.	GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.
Complexitysame	Medium	Medium	Medium	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	1-2 h	30-240 min	1-3 h
Participantsdifferent	Designers, developers as users, and facilitation	3-10	1-6	2-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	TOWS Matrix, Strategic Options, Priority Actions	Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary	Gap Matrix, Action Plan, Risk Notes
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	StrategyAnalysisOptions	TroubleshootingProblem solvingDiagnosis	StrategyAnalysisPlanning

Add more methods