View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Decision Jam |  Architecture ARID (Active Reviews for Intermediate Designs) |  Engineering Fault Isolation |  Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 60-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 30-180 min | 2-8 h |
Participantsdifferent | 4-10 | Designers, developers as users, and facilitation | 1-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Cluster, Prioritized Challenge, Experiment | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | FacilitationDecisionProblem solvingWorkshop | ArchitectureEngineeringFeedbackValidationTasks | TroubleshootingDiagnosisEngineering | Problem solvingRoot causeDecisionOperations |