View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:User InterviewsEmpathy MappingSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion | ![]() UX Research User Interviews | ![]() UX Research Empathy Mapping | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30–60 min per interview | 30–60 min | 1-2 h | 60-120 min |
Participantsdifferent | 1 participant per interview | 4-8 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Empathy Map, Assumptions List, Research Gaps | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | QualitativeResearchCustomerDiscovery | SynthesisQualitativeWorkshop | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |



