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 C4 Model | ![]() UX Research Card Sorting | ![]() Operations Fishbone Diagram | ![]() Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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 content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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 | 1-4 h | 20-45 min | 30-60 min | 1-6 Wochen |
Participantsdifferent | 1-5 | Based on research question | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Content groups, Label set, IA hypotheses | Fishbone Diagram, Cause Categories, Investigation Backlog | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | ArchitectureCommunicationVisualization | Information architectureNavigationStructure | Root causeQualityOperations | QualityProblem solvingRoot cause |



