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
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 C4 Model with its core stages and visible working result.
Architecture
C4 Model
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumLowLowHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-4 h15-30 min2-6 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-52-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Lean 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 checksContext Diagram, Container Diagram, Component DiagramRoot cause notes, CountermeasuresFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureCommunicationVisualization
Root causeIncidentLeanProblem solving
RiskQualityOperationsRoot cause
Add more methods