View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Operations After-Action Review |  Architecture arc42 |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 45-90 min | 20-45 min | 1-2 Tage | 60-120 min |
Participantsdifferent | 2-5 | 3-12 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Lessons learned, Action items, Event summary | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | LeanProblem solvingCoachingOperations | LearningOperationsImprovement | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |