Laurent Dresse, Data Governance Evangelist:
For me, it’s mainly driven by use cases. You cannot expect to document the entire company data assets patrimony from the start. It’s too much of an effort. So you need really to have an iterative approach with your business glossary.
You start small with one or two use cases and move fast by adding more and more use cases to increase the content of your business glossary.
In parallel, you should not hesitate to challenge your glossary structure and metamodel as you move along with the population of the content.
And then, last but not least, you can add new attributes, new classification, new tags, new relationships to build the end-to-end view of your data value chain.
In a nutshell, I would say:
- start with your glossary based on your use cases with a limited scope and perimeter.
- and then build a type of new use case that will come and enrich the content of your business glossary.
- Also, do not be afraid to open quickly your glossary to the organization because this is the best way to gather feedback.
- In your iteration, take into consideration the user feedback, which is an important part of adoption.