View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations A3 Problem Solving |
|---|---|---|---|
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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ArchitectureQualityRiskTradeoffsStakeholders | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
