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 |  Delivery RAID Log |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | 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 a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-240 min | 30 min Setup, dann laufend | 90-180 min | 45-90 min |
Participantsdifferent | 1-6 | 1-3 maintaining, briefing for everyone | 5-15 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | RAID Log, Status Report Source | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | RiskTrackingStakeholdersGovernance | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |