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 C4 Model |  Operations A3 Problem Solving |  Operations After-Action Review |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 1-4 h | 45-90 min | 20-45 min |
Participantsdifferent | 1-5 | 2-5 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | A3 Report, Action Plan, Root Cause Analysis | Lessons learned, Action items, Event summary |
Tagsno overlap | ArchitectureCommunicationVisualization | LeanProblem solvingCoachingOperations | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
