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 | ![]() Architecture Architecture Decision Record | ![]() Knowledge Modeling Knowledge Mapping | ![]() Knowledge Modeling IBIS |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 15-45 min | 1-3 h | 1-3 h |
Participantsdifferent | 5-15 | 1-3 | 3-12 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | ADR File, Decision Log, Rationale | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Issue Map, Positions, Argument Notes |
Tagsno overlap | RequirementsArchitectureWorkshop | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk | RationaleKnowledgeDecision |



