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 Request for Comments |  Agile 4Ls Retrospective |  Operations Accountability Ladder |
|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45–75 min | 20-45 min |
Participantsdifferent | 3-20 Reviewer | Team members involved | 1-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | 4Ls Board, Learning Themes, Improvement Actions | Ownership Reflection, Action Commitment, Coaching Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RetrospectiveLearningReflectionTeam | ResponsibilityLeadershipTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
