View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Affinity Diagramming |  Architecture C4 Model |  Operations 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 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. | 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 | Low | Low | High |
Timedifferent | 45–90 min | 1-4 h | 15-30 min | 1-6 Wochen |
Participantsdifferent | 3-10 | 1-5 | 2-6 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Context Diagram, Container Diagram, Component Diagram | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureCommunicationVisualization | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |