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 Architecture Decision Record | ![]() Operations Process Mapping | ![]() Agile Sailboat Retrospective |
|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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 | Low | Medium | Low |
Timedifferent | 15-45 min | 1-3 h | 45-90 min |
Participantsdifferent | 1-3 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Process Map, Handoff List, Improvement Backlog | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ProcessOperationsImprovement | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






