methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration for Communication Plan
Delivery
Communication Plan
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
30–60 min per interview45-90 min3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage
Participantsdifferent
1 participant per interview2-61 or a small team; particularly suitable for 3–4 people1-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryCommunication Plan, Channel Matrix, Message CadenceLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
QualitativeResearchCustomerDiscovery
CommunicationStakeholdersDeliveryPlanning
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
Add more methods