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 | ![]() Architecture C4 Model | ![]() Agile Mad Sad Glad | ![]() 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45–75 min | 1-4 h | 30-60 min | 60-120 min |
Participantsdifferent | Team members involved | 1-5 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Context Diagram, Container Diagram, Component Diagram | Emotion Board, Themes, Action Items | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ArchitectureCommunicationVisualization | RetrospectiveTeamReflection | ArchitectureCommunicationStakeholdersCanvas |



