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 Failure Mode and Effects Analysis |  Operations Gemba Walk |  Operations Scatter Diagram |
|---|---|---|---|---|
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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 1-4 h | 2-6 h | 30-120 min | 30-90 min |
Participantsdifferent | 1-5 | 3-10 | 2-6 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions | Observation Notes, Improvement Ideas | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause | LeanObservationProcessOperations | Root causeQualityVisualization |