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 | ![]() Architecture arc42 | ![]() UX Research Personas |
|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 1-4 h | 1-2 Tage | 1-3 Tage |
Participantsdifferent | 1-5 | 1-4 | Internes Team |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | ResearchCustomerSynthesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






