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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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
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
The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.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
LowLowHighMedium
Timedifferent
1-2 h15-30 min2-6 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-82-63-101 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Inception Canvas, Risks, Goal List, Open QuestionsRoot cause notes, CountermeasuresFMEA Table, Risk Priority, Mitigation ActionsLean 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
AlignmentArchitectureCanvas
Root causeIncidentLeanProblem solving
RiskQualityOperationsRoot cause
ArchitectureQualityRiskAssessmentLean
Add more methods