View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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 read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 | 1-4 h | 45-90 min | 45-90 min | 60-120 min |
Participantsdifferent | 1-5 | 4-12 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureCommunicationVisualization | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement | ArchitectureCommunicationStakeholdersCanvas |