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 Architecture Communication Canvas | ![]() Operations Fishbone Diagram | ![]() Operations 8D Problem Solving |
|---|---|---|---|---|
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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 30-90 min | 60-120 min | 30-60 min | 1-6 Wochen |
Participantsdifferent | 1-4 | 2-8 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Fishbone Diagram, Cause Categories, Investigation Backlog | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Root causeQualityVisualization | ArchitectureCommunicationStakeholdersCanvas | Root causeQualityOperations | QualityProblem solvingRoot cause |



