View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Rich Picture |  Facilitation Expectation Mapping |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | 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 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-90 min | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-10 | 3-12 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Rich Picture, Problem Framing Notes | Expectation Map, Alignment Notes, Agreements | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | AlignmentStakeholdersTeam | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |