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 arc42 |  UX Research Affinity Diagramming |  Operations A3 Problem Solving |  Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 1-2 Tage | 45–90 min | 45-90 min | 2-8 h |
Participantsdifferent | 1-4 | 3-10 | 2-5 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Theme clusters, Insight statements, Opportunity areas | A3 Report, Action Plan, Root Cause Analysis | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | SynthesisQualitativeRoot cause | LeanProblem solvingCoachingOperations | Problem solvingRoot causeDecisionOperations |