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 arc42 |  Agile Sailboat Retrospective |  Business Strategy Strategy Execution Loop |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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 | Low | High | Low |
Timedifferent | 1-2 Tage | 45-90 min | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min |
Participantsdifferent | 1-4 | 4-12 | 5-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Sailboat Board, Risks, Improvement Actions | Execution Loop, Review Cadence, Strategic Learning Log | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ArchitectureDocumentationCommunication | RetrospectiveTeamImprovement | ExecutionCadenceLearningGovernance | RetrospectiveImprovementExperimentsTeam |