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 | ![]() Operations Accountability Ladder | ![]() Facilitation Expectation Mapping |
|---|---|---|---|
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. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 4-12 | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Ownership Reflection, Action Commitment, Coaching Notes | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | ResponsibilityLeadershipTeam | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






