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 Concept Mapping | ![]() Architecture Quality Attribute Workshop | ![]() Decision Making Assumption Surfacing | ![]() Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 2-4 h | 45-90 min | 60-90 min |
Participantsdifferent | 1-8 | 5-15 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Quality Scenarios, Priority List, Architecture Concerns | Assumption List, Critical Assumptions, Learning Plan | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | RequirementsArchitectureWorkshop | AssumptionsRiskDecisionDiscovery | RiskArchitectureWorkshopValidation |



