View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Process MappingSpotify Model MappingStarfish RetrospectiveTeam Topologies Interaction Modes
| Criterion |  Operations Process Mapping |  Team Design Spotify Model Mapping |  Agile Starfish Retrospective |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 90-180 min | 45-90 min | Half day |
Participantsdifferent | 3-10 | 5-15 | 4-12 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Spotify Model Map, Action List | Starfish Board, Practice Changes, Experiments | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | ProcessOperationsImprovement | TeamOrganizationAlignmentDiagnosis | RetrospectiveImprovementExperimentsTeam | TeamAlignmentCollaborationOrganization |