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 AnalysisKnowledge MappingATAM (Architecture Tradeoff Analysis Method)Domain Storytelling
| Criterion |  Operations Standard Work Analysis |  Knowledge Modeling Knowledge Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 2-6 | 3-12 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | LeanProcessQuality | KnowledgeMappingRisk | ArchitectureQualityRiskTradeoffsStakeholders | KnowledgeDomain-Driven DesignProcess |