View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStrategy Execution LoopStarfish RetrospectiveStart Stop Continue
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Business Strategy Strategy Execution Loop | ![]() Agile Starfish Retrospective | ![]() 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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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 | Low | High | Low | Low |
Timedifferent | 15-45 min | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min | 30-60 min |
Participantsdifferent | 1-3 | 5-12 | 4-12 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Execution Loop, Review Cadence, Strategic Learning Log | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ExecutionCadenceLearningGovernance | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |



