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 Scatter Diagram |  Architecture C4 Model |  Operations Fishbone Diagram |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 30-90 min | 1-4 h | 30-60 min | 2-6 h |
Participantsdifferent | 1-4 | 1-5 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Context Diagram, Container Diagram, Component Diagram | Fishbone Diagram, Cause Categories, Investigation Backlog | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityVisualization | ArchitectureCommunicationVisualization | Root causeQualityOperations | RiskQualityOperationsRoot cause |