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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
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 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.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.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.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
LowHighLowMedium
Timedifferent
30-120 min2-6 h30-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-63-103-71 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Observation Notes, Improvement IdeasFMEA Table, Risk Priority, Mitigation ActionsExample Map, Acceptance Criteria, Open QuestionsLean 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
LeanObservationProcessOperations
RiskQualityOperationsRoot cause
Behavior-Driven DevelopmentRequirementsExamplesRefinement
ArchitectureQualityRiskAssessmentLean
Add more methods