View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations PDCA Cycle |  Knowledge Modeling Concept Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 1 h bis mehrere Wochen | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-60 min |
Participantsdifferent | 1-8 | 1-8 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Concept Map, Relationship Labels, Knowledge Gaps | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Continuous improvementLeanExperiments | KnowledgeConceptsMappingSensemaking | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskExperimentsValidation |