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 Hypothesis-Driven Troubleshooting |  Facilitation Expectation Mapping |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-240 min | 45-90 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 1-6 | 3-12 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |