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 4Ls Retrospective | ![]() Agile Mad Sad Glad | ![]() Architecture arc42 | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45–75 min | 30-60 min | 1-2 Tage | 60-120 min |
Participantsdifferent | Team members involved | 3-10 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |



