View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Architecture arc42 |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 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 | Low | Low | Low |
Timedifferent | 1-3 h | 1-2 Tage | 45-90 min | 45-90 min |
Participantsdifferent | 3-10 | 1-4 | 4-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Architecture Document, Context View, Runtime View, Deployment View | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureDocumentationCommunication | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |