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 Personas | ![]() Architecture Quality Attribute Workshop | ![]() Architecture C4 Model | ![]() UX Research Empathy Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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 a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Tage | 2-4 h | 1-4 h | 30–60 min |
Participantsdifferent | Internes Team | 5-15 | 1-5 | 4-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Quality Scenarios, Priority List, Architecture Concerns | Context Diagram, Container Diagram, Component Diagram | Empathy Map, Assumptions List, Research Gaps |
Tagsno overlap | ResearchCustomerSynthesis | RequirementsArchitectureWorkshop | ArchitectureCommunicationVisualization | SynthesisQualitativeWorkshop |



