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 arc42 |  Operations After-Action Review |  Business Strategy Strategic, Tactical and Operational Planning |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 Tage | 20-45 min | 90-180 min | 1-4 h |
Participantsdifferent | 1-4 | 3-12 | 4-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Lessons learned, Action items, Event summary | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureDocumentationCommunication | LearningOperationsImprovement | CadenceGovernanceExecution | ArchitectureCommunicationVisualization |