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 Causal Factor Analysis | ![]() Architecture Architecture Decision Record |
|---|---|---|---|
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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | High | Low |
Timedifferent | 1-4 h | 2-6 h | 15-45 min |
Participantsdifferent | 1-5 | 3-10 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureCommunicationVisualization | CausalityIncidentRoot causeTimeline | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






