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 |  Decision Making RAPID |  Delivery RAID Log |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-180 min | 45-90 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 1-6 | 3-12 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | RAPID Role Map, Recommendation, Decision Log | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | TroubleshootingDiagnosisEngineering | DecisionRolesGovernance | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery |