View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsFishbone DiagramArchitecture Communication CanvasFailure Mode and Effects Analysis
| Criterion |  Knowledge Modeling Competency Questions |  Operations Fishbone Diagram |  Architecture Architecture Communication Canvas |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 2-4 h | 30-60 min | 60-120 min | 2-6 h |
Participantsdifferent | 2-8 | 2-8 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Fishbone Diagram, Cause Categories, Investigation Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Root causeQualityOperations | ArchitectureCommunicationStakeholdersCanvas | RiskQualityOperationsRoot cause |