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 Sailboat Retrospective |  Architecture Architecture Communication Canvas |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 1-4 h | 45-90 min | 60-120 min | 30-60 min |
Participantsdifferent | 1-5 | 4-12 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Sailboat Board, Risks, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureCommunicationVisualization | RetrospectiveTeamImprovement | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementTeamReflection |