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 |  UX Research Personas |  Architecture C4 Model |
|---|---|---|---|---|
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. | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 Tage | 45–90 min | 1-3 Tage | 1-4 h |
Participantsdifferent | 1-4 | 3-10 | Internes Team | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Theme clusters, Insight statements, Opportunity areas | Persona Profiles, Needs Summary, Scenario Notes | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureDocumentationCommunication | SynthesisQualitativeRoot cause | ResearchCustomerSynthesis | ArchitectureCommunicationVisualization |