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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
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)
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.
Complexitydifferent
LowHighMediumLow
Timedifferent
1-2 h2-6 h3–4 h for initial assessment; preparation and deeper analysis additional30-120 min
Participantsdifferent
2-83-101 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeFMEA 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 checksObservation Notes, Improvement Ideas
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RiskQualityOperationsRoot cause
ArchitectureQualityRiskAssessmentLean
LeanObservationProcessOperations
Add more methods