View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Delivery RAID Log |  Architecture Risk Storming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-180 min | 30 min Setup, dann laufend | 60-90 min | 15-45 min |
Participantsdifferent | 1-6 | 1-3 maintaining, briefing for everyone | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale |
Tagsno overlap | TroubleshootingDiagnosisEngineering | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance |