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 |  Facilitation Stakeholder Salience Model |  Agile ROAM Board |  Delivery RAID Log |
|---|---|---|---|---|
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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-180 min | 60-90 min | 20-40 min initial, dann laufend | 30 min Setup, dann laufend |
Participantsdifferent | 1-6 | 3-6 | 3-15 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Salience Diagram, Strategy per Class | ROAM Board, Owner List | RAID Log, Status Report Source |
Tagsno overlap | TroubleshootingDiagnosisEngineering | StakeholdersFacilitationAlignmentGovernance | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance |