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 Fishbone Diagram |  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. | 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 | Low | Low | High |
Timedifferent | 45–90 min | 1-4 h | 30-60 min | 1-6 Wochen |
Participantsdifferent | 3-10 | 1-5 | 2-8 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Context Diagram, Container Diagram, Component Diagram | Fishbone Diagram, Cause Categories, Investigation Backlog | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureCommunicationVisualization | Root causeQualityOperations | QualityProblem solvingRoot cause |