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 Communication Canvas |  Operations Scatter Diagram |  Operations 8D Problem Solving |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-120 min | 30-90 min | 1-6 Wochen | 15-30 min |
Participantsdifferent | 2-8 | 1-4 | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | Root causeQualityVisualization | QualityProblem solvingRoot cause | Root causeIncidentLeanProblem solving |