View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Expectation Mapping | ![]() Agile Start Stop Continue | ![]() Systems Thinking CATWOE Analysis | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30-60 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 3-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection | Systems thinkingFramingStakeholders | RetrospectiveImprovementExperimentsTeam |



