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 arc42 |  Operations Root Cause Tree Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 | Low | Low | Medium | Low |
Timedifferent | 45–90 min | 1-2 Tage | 1-3 h | 15-30 min |
Participantsdifferent | 3-10 | 1-4 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Architecture Document, Context View, Runtime View, Deployment View | Cause Tree, Evidence Notes, Countermeasures | Root cause notes, Countermeasures |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureDocumentationCommunication | Root causeTreeIncidentQuality | Root causeIncidentLeanProblem solving |