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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
LowMediumLowLow
Timedifferent
15-45 min1-3 h45-90 min30-60 min
Participantsdifferent
1-33-104-123-12
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleProcess Map, Handoff List, Improvement BacklogStarfish Board, Practice Changes, ExperimentsStart Stop Continue Board, Improvement Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ProcessOperationsImprovement
RetrospectiveImprovementExperimentsTeam
RetrospectiveImprovementTeamReflection
Add more methods