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 Competency Questions | ![]() Facilitation Stakeholder Mapping | ![]() Operations Change 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 2-4 h | 60–90 min | 45-120 min |
Participantsdifferent | 2-8 | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Stakeholder Map, Engagement Plan, Risk Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | StakeholdersAlignmentFacilitationChange | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






