View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Mad Sad Glad | ![]() Architecture Architecture Communication Canvas | ![]() Agile Start Stop Continue | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Low | Low |
Timedifferent | 30-60 min | 60-120 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 2-8 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveTeamReflection | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |



