View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Accountability Ladder | ![]() Facilitation Expectation Mapping | ![]() Agile Start Stop Continue | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-45 min | 45-90 min | 30-60 min | 45-90 min |
Participantsdifferent | 1-8 | 3-12 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tags1 shared | ResponsibilityLeadershipTeam | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |



