View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Team Design Spotify Model Mapping |  Operations 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 45-90 min | 90-180 min | 15-30 min | 1-6 Wochen |
Participantsdifferent | 3-12 | 5-15 | 2-6 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |