View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Starfish Retrospective |  Facilitation Expectation Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | 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 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | 45-90 min | 60-90 min |
Participantsdifferent | 4-12 | 3-12 | 3-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
