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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
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
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 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.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
1-4 h30–60 min per interview3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
1-51 participant per interview1 or a small team; particularly suitable for 3–4 people2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramInterview Notes, Themes, Insight SummaryLean 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
ArchitectureCommunicationVisualization
QualitativeResearchCustomerDiscovery
ArchitectureQualityRiskAssessmentLean
AssumptionsRiskDecisionDiscovery
Add more methods