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 |  Engineering Fault Isolation |  Architecture arc42 |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | Medium | Low | Medium |
Timedifferent | 60-90 min | 30-180 min | 1-2 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-10 | 1-6 | 1-4 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Cluster, Prioritized Challenge, Experiment | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Architecture Document, Context View, Runtime View, Deployment View | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | FacilitationDecisionProblem solvingWorkshop | TroubleshootingDiagnosisEngineering | ArchitectureDocumentationCommunication | ArchitectureEngineeringFeedbackValidationTasks |