View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Business Strategy GAP Analysis |  Operations Change Analysis |  Engineering Fault Isolation |
|---|---|---|---|---|
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. | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 45-120 min | 30-180 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 2-6 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Gap Matrix, Action Plan, Risk Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyAnalysisPlanning | ChangeRoot causeTroubleshootingComparison | TroubleshootingDiagnosisEngineering |