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 |  Operations Causal Factor Analysis |  Agile Start Stop Continue |  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. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 45-90 min | 2-6 h | 30-60 min | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | AlignmentStakeholdersTeam | CausalityIncidentRoot causeTimeline | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |