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 |  Operations A3 Problem Solving |  Architecture Architecture Communication Canvas |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 60-120 min | 15-30 min |
Participantsdifferent | 3-20 Reviewer | 2-5 | 2-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | A3 Report, Action Plan, Root Cause Analysis | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | LeanProblem solvingCoachingOperations | ArchitectureCommunicationStakeholdersCanvas | Root causeIncidentLeanProblem solving |