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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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)
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
LowLowMediumLow
Timedifferent
30–60 min per interview1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
1 participant per interview1-41 or a small team; particularly suitable for 3–4 people2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryArchitecture Document, Context View, Runtime View, Deployment ViewLean 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 checksAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
QualitativeResearchCustomerDiscovery
ArchitectureDocumentationCommunication
ArchitectureQualityRiskAssessmentLean
AssumptionsRiskDecisionDiscovery
Add more methods