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 of Lean Startup with its method-specific working model.
Innovation
Lean Startup
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)
Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis
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 uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.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 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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 hWochen bis Monate je Lernzyklus3–4 h for initial assessment; preparation and deeper analysis additional1-3 h
Participantsdifferent
2-82-81 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeHypothesis list, MVPs, Learning reports, Pivot or persevere decisionLean 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 checksStandard Work Sheet, Deviation List, Improved Standard, Training Needs
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
LeanStartupValidationMVP
ArchitectureQualityRiskAssessmentLean
LeanProcessQuality
Add more methods