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
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for Standard Work Analysis.
Operations
Standard Work 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
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.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.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
LowMediumMediumMedium
Timedifferent
1-2 h1-3 h1-3 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-84-102-61 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeCurrent-state map, Future-state map, Bottleneck listStandard Work Sheet, Deviation List, Improved Standard, Training NeedsLean 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
KnowledgeDomain-Driven DesignProcess
LeanFlowWasteDelivery
LeanProcessQuality
ArchitectureQualityRiskAssessmentLean
Add more methods