View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Domain StorytellingStandard Work AnalysisATAM (Architecture Tradeoff Analysis Method)Gemba Walk
| Criterion | ![]() Knowledge Modeling Domain Storytelling | ![]() Operations Standard Work Analysis | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() 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. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Low | Medium | High | Low |
Timedifferent | 1-2 h | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-120 min |
Participantsdifferent | 2-8 | 2-6 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Observation Notes, Improvement Ideas |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | LeanProcessQuality | ArchitectureQualityRiskTradeoffsStakeholders | LeanObservationProcessOperations |



