View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Standard Work AnalysisContext MapDomain StorytellingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Operations Standard Work Analysis |  Domain Modeling Context Map |  Knowledge Modeling Domain Storytelling |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 1-2 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-6 | 2-8 | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | Context Map, Integration Patterns, Boundary Notes | Domain Story, Glossary Notes, Process Narrative | Lean 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 | LeanProcessQuality | Domain-Driven DesignBoundariesStrategy | KnowledgeDomain-Driven DesignProcess | ArchitectureQualityRiskAssessmentLean |