View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Spotify Model Mapping |  Operations Process Mapping |  Operations 5 Whys |  Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 90-180 min | 1-3 h | 15-30 min | 2-8 h |
Participantsdifferent | 5-15 | 3-10 | 2-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Spotify Model Map, Action List | Process Map, Handoff List, Improvement Backlog | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | ProcessOperationsImprovement | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations |