methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Sailboat Retrospective
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.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
LowMediumLowLow
Timedifferent
15-45 min1-3 Tage30-60 min45-90 min
Participantsdifferent
1-31-43-124-12
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, RationaleStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods