View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Quality Attribute Workshop | ![]() Knowledge Modeling IBIS | ![]() Knowledge Modeling Concept Mapping | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 1-3 h | 1-2 h | 15-45 min |
Participantsdifferent | 5-15 | 2-8 | 1-8 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps | ADR File, Decision Log, Rationale |
Tagsno overlap | RequirementsArchitectureWorkshop | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking | ArchitectureRationaleDocumentationGovernance |



