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 After-Action Review |  Operations A3 Problem Solving |  Architecture C4 Model |  Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | 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. | 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-45 min | 45-90 min | 1-4 h | 30-120 min |
Participantsdifferent | 3-12 | 2-5 | 1-5 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | A3 Report, Action Plan, Root Cause Analysis | Context Diagram, Container Diagram, Component Diagram | Observation Notes, Improvement Ideas |
Tagsno overlap | LearningOperationsImprovement | LeanProblem solvingCoachingOperations | ArchitectureCommunicationVisualization | LeanObservationProcessOperations |