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 |  Architecture C4 Model |  Operations Process Mapping |  Operations Learning Review |
|---|---|---|---|---|
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. | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20-45 min | 1-4 h | 1-3 h | 1-3 h |
Participantsdifferent | 3-12 | 1-5 | 3-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Context Diagram, Container Diagram, Component Diagram | Process Map, Handoff List, Improvement Backlog | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | LearningOperationsImprovement | ArchitectureCommunicationVisualization | ProcessOperationsImprovement | LearningRetrospectiveIncidentOperations |