View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Argument MappingArchitecture Communication CanvasStarfish RetrospectiveSailboat Retrospective
| Criterion | ![]() Decision Making Argument Mapping | ![]() Architecture Architecture Communication Canvas | ![]() Agile Starfish Retrospective | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 60-120 min | 45-90 min | 45-90 min |
Participantsdifferent | 1-8 | 2-8 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | SensemakingDecisionRationale | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |



