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 Scatter Diagram with its method-specific working model.
Operations
Scatter Diagram
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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)
Purposedifferent
When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
30-90 min15-30 min1-4 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-42-61-51 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Scatter Plot, Korrelationsnotiz, HypothesenlisteRoot cause notes, CountermeasuresContext Diagram, Container Diagram, Component DiagramLean 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 checks
Tagsno overlap
Root causeQualityVisualization
Root causeIncidentLeanProblem solving
ArchitectureCommunicationVisualization
ArchitectureQualityRiskAssessmentLean
Add more methods