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 Architecture Decision Record |  Operations Process Mapping |  Architecture C4 Model |  Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | 15-45 min | 1-3 h | 1-4 h | 30-120 min |
Participantsdifferent | 1-3 | 3-10 | 1-5 | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Process Map, Handoff List, Improvement Backlog | Context Diagram, Container Diagram, Component Diagram | Observation Notes, Improvement Ideas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ProcessOperationsImprovement | ArchitectureCommunicationVisualization | LeanObservationProcessOperations |