View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Team Design Team Cognitive Load Assessment | ![]() Systems Thinking Rich Picture | ![]() Agile Starfish Retrospective | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | 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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min | 30-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-12 | 2-10 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Rich Picture, Problem Framing Notes | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | TeamComplexityImprovementDiagnosis | Systems thinkingSoft systemsFramingVisualization | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |



