<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[dScribe data - Medium]]></title>
        <description><![CDATA[On a mission to create the most intuitive data catalog on the planet - Medium]]></description>
        <link>https://medium.com/dscribe-data?source=rss----517f32502aa9---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>dScribe data - Medium</title>
            <link>https://medium.com/dscribe-data?source=rss----517f32502aa9---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:28:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/dscribe-data" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Are you gatekeeping your metadata contributors?]]></title>
            <link>https://medium.com/dscribe-data/are-you-gatekeeping-your-metadata-contributors-b12211b8aa41?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/b12211b8aa41</guid>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-discovery]]></category>
            <category><![CDATA[metadata-management]]></category>
            <dc:creator><![CDATA[Pieter Delaere]]></dc:creator>
            <pubDate>Thu, 30 Jun 2022 11:17:05 GMT</pubDate>
            <atom:updated>2023-10-15T09:31:49.556Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XL77J4gJgTkPcrbPCRaXhw.png" /><figcaption>crowdsourcing metadata contributions</figcaption></figure><p>In a <a href="https://medium.com/dscribe-data/the-importance-of-broad-discovery-in-metadata-governance-afa804175a0">previous article</a>, we discussed in which scenarios the discoverability of data assets (reports, datasets, etc.) might need to be restricted. Now that we’ve got a strategy in place to ensure that the visibility of highly sensitive assets is restricted, let’s talk about a broader question. <strong>How can we maximize contributions while also ensuring the high quality and trustworthiness of our metadata documentation?</strong></p><p>Before we start, let’s point out a critical success factor in any metadata-driven documentation effort: <strong>automation</strong>. Trying to manually keep a list of all potentially relevant data assets will not put you in a happy place. Better to rely on <a href="https://dscribedata.com/integrations/">connectors</a> to automatically crawl the available metadata from various sources. Apart from the fact that you don’t have to turn into a fulltime typist, you might find that there is a lot more information to be retrieved via metadata than you’d expect. The following insights are often available: stakeholders (asset creator, last updated by), recency (creation date, last update date) and context (location, dependencies with other assets).</p><p>Although automation can bring us a long way, further context added by human experts will always be valuable. That brings us back to our initial question. At face value, it’s a tricky balance to find. In a data context, you might assume that the more users you give permission to create and edit documentation, the higher the chance of mistakes and thus the lower the overall quality of that documentation becomes. On the other hand, restricting permissions to contribute to the bare minimum also doesn’t sound too great. You wouldn’t want to be responsible for creating all that documentation on your own now do you?</p><p>What will be the right model for your organization will depend on a number of factors. To start this thought exercise, you can ask the following questions:</p><ul><li>What does my organization structure look like? Are we organized by domain, geographic region, business unit…?</li><li>Which relevant roles are available within my organization? Which data-related roles do we have in place or are we planning to create?<br> Note: data documentation and governance are often perceived as a lot of work. However, with or without a metadata initiative in place, many people in your organization inevitably have been (manually) doing the activities you are looking for. Whether it’s in an Excel list or an automation-enhanced data catalog makes no difference. What you’re trying to do is make their tasks easier and more effective.</li><li>When it comes to data, does your organization aspire to have an open-by-default or a restricted-by-default mentality? In terms of metadata policies, the former will likely result in a lighter touch than the latter.</li></ul><p>The good news is that whatever your organizational model, you should be able to define and implement the policies that suit your needs. Below are 3 examples that might provide you with some inspiration:</p><p><strong>Self-service &gt; Domain Validation &gt; Global Validation<br></strong>This organization makes no distinction between glossary assets (field definitions, metric calculations, business terms, etc. ) and catalog assets (reports and datasets). The bulk of all data assets exist in context of self-service initiatives. These assets can freely be documented by anyone in the organization, but not validated. Assets linked to a specific domain can be validated by one of the appointed domain stewards, indicating their trust level. Cross-domain assets are assigned to a global data (governance) team, who verify these assets are accurate and comply with the organizations’ guidelines and definitions.</p><p><strong>Centralized glossary + democratized catalog<br></strong>This organization combines a more limited, but globally harmonized glossary with a freely evolving and dynamic catalog. The assumption taken is that when teams choose to take up ownership of any report or dataset, they are committed to the accuracy of its documentation. By allowing this, documentation becomes more complete with less top-down effort.</p><p>In this organization, glossary assets are managed by recognized domain experts. Catalog assets can by default be contributed to by all people. Teams are free to take up ownership of any catalog asset, after which they can choose to validate them on their own authority.</p><p><strong>Assigned ownership<br></strong>This organization has a matrix structure, mainly domain-driven but with separate geographic structures in place for several domains. In addition, there is a strong project-driven approach, with many multiyear projects consisting of various stakeholders throughout the organization.</p><p>Rather than trying to translate this complex and evolving structure into metadata policies, the organization defines flexible rules to automatically assign assets to one of the existing teams. Rules make use of information such as source system, folder location and asset name prefixes (in those cases where naming conventions are in place) to define these assignments. Assets that could not be automatically assigned are reviewed by a central governance team. Once assigned, each team is responsible for the documentation and (where relevant) validation of each asset. People only have contribution permissions if they are member of the assigned team.</p><p>Here is a final piece of advice to set you on your way: <strong>start small</strong>. Rather than trying to cover every potential nook and cranny of your organization right from the start, you might be better off starting with generously assigned permissions. Assigning permissions too freely is much less damaging than being too restrictive. Documentation mistakes can always be corrected and will provide valuable coaching opportunities to increase data maturity. Keeping people engaged and enthusiastic to contribute is much harder. Focus on enabling as many contributions as possible and with the proper resources and guidance in place, overall quality will be much higher as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b12211b8aa41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/are-you-gatekeeping-your-metadata-contributors-b12211b8aa41">Are you gatekeeping your metadata contributors?</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting a data initiative — the bazaar approach]]></title>
            <link>https://medium.com/dscribe-data/starting-a-data-initiative-the-bazaar-approach-375fc9f1ce36?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/375fc9f1ce36</guid>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[start-with-why]]></category>
            <category><![CDATA[data-literacy]]></category>
            <category><![CDATA[data-discovery]]></category>
            <dc:creator><![CDATA[Pieter Delaere]]></dc:creator>
            <pubDate>Fri, 13 May 2022 11:36:15 GMT</pubDate>
            <atom:updated>2022-04-13T11:29:03.215Z</atom:updated>
            <content:encoded><![CDATA[<h3>Starting a data initiative — the bazaar approach</h3><p>I love this analogy by Barrasa, Hodler &amp; Webber in their whitepaper on <a href="https://neo4j.com/knowledge-graphs-data-in-context-for-responsive-businesses/">knowledge graphs</a>:</p><blockquote><em>“The construction of knowledge graphs is more bazaar than cathedral.”</em></blockquote><p>The same can be said to apply to data initiatives in general. From the cases I’ve been privileged enough to follow up on closely, it appears that organizations taking a step-by-step approach achieve success the fastest. Rather than attempting to design and build a cathedral right from the start, focusing on one specific use case at a time leads to faster return on investment, which makes the initiative be perceived as more rewarding by its target audience, which in turn increases your momentum for follow-up initiatives.</p><figure><img alt="Working on an initiative here! But why, how and what are we building?" src="https://cdn-images-1.medium.com/max/1024/0*1d_FESjQgZLG-YyB" /><figcaption>Working on an initiative here! But why, how and what are we building?</figcaption></figure><p>Planning on a data initiative right now? Make sure you zoom in sufficiently on the specific use case you wish to start from. As <a href="https://www.youtube.com/watch?v=u4ZoJKF_VuA">Simon Sinek</a> would say, start with <strong>why</strong>: which benefits will your initiative bring to your organization and its users? Proceed by outlining <strong>how </strong>you see the organization reaching this objective. Make sure you attentively listen to your audiences’ feedback to incorporate their feedback and elaborate on potentially confusing points. Finally, once you made sure you’ve got your audience on board, you can spend some time on the <strong>what</strong>: what exactly is this initiative called?</p><p>Some examples:</p><ul><li>Why we need this initiative? Better visibility of and easier access to the available data assets in our organization. How we could achieve this? By implementing a user-friendly, automatically maintained catalog of available reports and data. What do we call this initiative? A data discovery portal.</li><li>Why we need this initiative? Reduce confusion when interpreting reports or data, facilitate the onboarding of new employees. How we could achieve this? By creating a business glossary with harmonized terms and data definitions. What do we call this initiative? A business glossary.</li><li>Why we need this initiative? Increase clarity on which reports or datasets are trustworthy vs which ones are not. How we could achieve this? By introducing an approval workflow facilitating review by the proper stakeholders. What do we call this initiative? Establishing data ownership &amp; governance.</li></ul><p>Taking it one step further, breaking down your chosen use case into several steps can increase your momentum. For example, when focusing on data discovery: unlock one source at a time. When establishing a common business language: iterate per domain.</p><p>Building a ‘data bazaar’ might not sound like a particulary attractive approach as compared to the outlook of a well thought-through ‘data cathedral’. It will however help you cope with a continuously evolving data reality in your organization, enable you to deliver value faster and in the end lead to a more engaged and satisfied user base.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=375fc9f1ce36" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/starting-a-data-initiative-the-bazaar-approach-375fc9f1ce36">Starting a data initiative — the bazaar approach</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The importance of broad discovery in metadata governance]]></title>
            <link>https://medium.com/dscribe-data/the-importance-of-broad-discovery-in-metadata-governance-afa804175a0?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/afa804175a0</guid>
            <category><![CDATA[data-discovery]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[metadata-management]]></category>
            <dc:creator><![CDATA[Pieter Delaere]]></dc:creator>
            <pubDate>Fri, 13 May 2022 11:34:26 GMT</pubDate>
            <atom:updated>2022-05-13T11:34:26.249Z</atom:updated>
            <content:encoded><![CDATA[<p>When thinking about managing authorizations to access actual data, caution is warranted. You might not wish for everyone in the organization to be able to consult your monthly turnover figures. Specific margins per product are valuable information that should be protected from leaking outside the organization. And especially in a GDPR world, not just anyone should be allowed to consult personal customer information at will.</p><p>When talking about metadata authorizations however, things are different. There are two main reasons why you should think differently about your authorizations model for metadata versus for actual data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/1*eVEPztBzPtBqlb3Pia-n5Q.png" /></figure><p><strong>Reason number 1: broad access comes with more rewards</strong></p><p>Although a wealth of information can be gained from metadata alone, the fact that no actual data is exposed offers the opportunity to give significantly broader read access to metadata assets. Doing so comes with significant benefits for three user groups.</p><p>Data consumers, who are making use of data for decision making, analyses or various other reasons, waste less time looking for the reports or datasets they need. Rather than going through an often frustrating search (see an example of classic data discovery <a href="https://dscribedata.com/discovery/">here</a>), a single metadata portal gives them an easy place to start. The better metadata is exposed to them, the broader they can search and the higher the chance they will find something of value to them.</p><p>Data producers, who create reports and data models for themselves or for others, become more productive. Before starting their work, they can have a quick look at which assets exist already, often reducing the need to start from scratch or even resulting in the conclusion that the exact asset they intended to create is already available. Additionally, these data experts who are typically in high demand have a reduced ‘support’ burden. They no longer need to deal with common questions such as ‘Does a report on X exist?’ or ‘Where can I find a dataset with Y and Z?’. These questions can now be answered directly by users via the discovery portal.</p><p>IT managers, who need to decide on which tools to invest in and subsequently wish to maximize their return on those investments, can use a metadata-based discovery portal to boost adoption. Even users who are not yet aware of a tool at their disposal, might discover valuable data assets in it via the portal and subsequently start to make of it. Another result is reduced stress on how to manage a complex and distributed data landscape with various systems. Without having to physically integrate each system, via the metadata at least a single access point can be offered, easily pointing users in the right direction.</p><p><strong>Reason number 2: broad access incurs fewer risks</strong></p><p>When granting access to data, important questions need to be answered. For example: can people cause harm by sharing information with unauthorized users? Are there regulations that need to be complied with when consulting this data (e.g. GDPR)?</p><p>On the other hand, when exposing metadata, such as the name and description of various reports and datasets, only one question matters: is there a reason why the existence of this asset should only be known to a select group of users? In practice, the answer is rarely “yes”. One rare example of where access to metadata might lead to undesired consequences, is the exposure of highly sensitive content such as ‘salary reward reporting’ or ’employee performance ranking’.</p><p>In essence, a key use case for a metadata discovery portal is maximizing discoverability of assets throughout your organization and across various systems. Deviating from that openness should really be done as little as possible in order to reap maximum rewards, as discussed earlier.</p><p><strong>Conclusion</strong></p><p>Offering your employees access to a data discovery platform (powered through metadata) is an incredible gift. Via a single access point, you enable them to find and understand any data resources available in the organization. The result? Increased productivity, data usage and cross-team collaboration, without compromising your actual data’s security.</p><p>Now that we have clarity on how to define metadata discovery policies, in a next blog, let’s talk about defining metadata contribution policies. Who should be allowed to further document various metadata assets? Should you assign metadata ownership and if so, to whom? Follow-up blog post coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afa804175a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/the-importance-of-broad-discovery-in-metadata-governance-afa804175a0">The importance of broad discovery in metadata governance</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making data easily accessible and fully understood]]></title>
            <link>https://medium.com/dscribe-data/making-data-easily-accessible-and-fully-understood-90271463f13e?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/90271463f13e</guid>
            <category><![CDATA[market-trends]]></category>
            <category><![CDATA[data-discovery]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Pieter Delaere]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 11:36:21 GMT</pubDate>
            <atom:updated>2022-01-31T11:35:31.902Z</atom:updated>
            <content:encoded><![CDATA[<p>When we first started working in earnest on our <a href="https://medium.com/dscribe-data/how-my-challenge-as-a-data-consultant-lead-to-the-joy-of-a-new-solution-c7ed87f8c480">data knowledge product</a> in January 2021, we had a clear picture of the customer challenge we wanted to help tackle. However, it was not until we started preparing to pitch to investors and officially launch as a company, that we summarized it onto one phrase:</p><blockquote>“to make data easily accessible and fully understood”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J-h_dFjE2U0TgQzd" /></figure><p>So where did that come from? We could talk about the explosion of data volumes available to organizations. We could mention the increasing variety of structured and unstructured data formats. We could point to the many ‘self-service’ tools used by knowledge workers, making it easier than ever to access and analyze data. But those insights very likely would not be new to you.</p><p>The data market is booming and terms like the data lakehouse, data literacy and data catalogs were ubiquitous in the data-related news of the past year. Rather than talk about major market trends however, when meeting customers I prefer being more pragmatic.</p><blockquote>Market trends can be inspiring, but they become empowering only when you are able to apply them to solve a customer’s specific challenge.</blockquote><p>It is by advising customers on how a solution can help in their specific context, that value is recognized. Here are <strong>3 tangible stories</strong> that in the past have lit up customer’s eyes during conversations.</p><p>An industrial holding, existing of 5 largely independent divisions was struggling to consolidate its reporting. For his revenue reports, the group’s CEO received over 30 spreadsheets monthly, each with its own format and calculation methods. To tackle this issue, the group decided to offer its divisions a shared data platform, offered freely for data storage and analysis. However, it was only when a dedicated effort was launched to harmonize the definition of revenue and all underlying data elements, that significant gains in efficiency and data accuracy were realized. <strong>A common language, not shared technology, was the breakthrough solution.</strong></p><p>An international food company aimed to roll out harmonized KPI reporting across the top 500 of the organization. Since they were structured as a matrix (functional departments and geographic regions), to achieve this, great efforts were spent on gathering and aligning requirements from all stakeholders, for each KPI. To translate these requirements into straightforward input towards the development team, 2 spreadsheets were created: one containing the KPIs (including a definition, calculation and various labels) and the other containing definitions of individual data elements. Although working towards clearly structured requirements worked well in getting business and IT on the same footing, heavy reliance on the 2 spreadsheets did present a few challenges of its own. Definitions were frequently updated without review by other stakeholders, no history of changes was visible and at one point in time, the shared files were lost, forcing the company to continue from a 2-month old backup. It was by moving towards a tool dedicated to documentation and collaboration around data that these ‘growing pains’ were solved and focus could move back to the task at hand: <strong>establishing clear, harmonized data definitions as a foundation for consolidated KPI reporting.</strong></p><p>At a mid-sized chemical recycling plant, a financial controller was in charge of providing the management and sales teams with weekly reporting on sales, receivables and payables. Having worked at the company for many years, he knew the ins and outs of its business. Via manual data extracts and a number of macros in Excel, he tried to automate his weekly efforts. That worked well at the start — the reports were built quickly and no business user had objections to working with figures in Excel. Over the course of the next 4 years however, additional business requests and an increase in the data volume caused the number of manual actions needed to finalize the reports to grow. What started with one file became 5 (2 with the actual reports and 3 with intermediate transformations). It certainly didn’t help that each file now took around 5 minutes to load and the original financial controller had left the company. Eventually, a data warehouse and visualization tool were implemented, replacing the excel reports. The trickiest part of this new setup was not rebuilding the excel logic, it was understanding why certain transformations were done in the first place. Documentation is often the last thing planned and the first thing left out when looking for cost optimizations. However, people’s memory is not limitless and when people leave, knowledge leaves with them.<strong> Not formulating and storing knowledge almost always means higher costs</strong> <strong>to fill knowledge gaps in the future.</strong> In the end, the new reporting implementation took 6 months. Less than a month to implement the new tools, but nearly 5 months to analyze the existing logic and validate the new results.</p><p>Referring to major trends in the data market is energizing. It allows you to stimulate people to adopt new capabilities and dream up inspiring use cases. But to really make a dent in the data space, let’s not neglect the need to make our ideas specific and tangible enough for people to be not only inspired, but empowered to move forward. For us, that is all about offering a pragmatic solution to “make data easily accessible and fully understood”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90271463f13e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/making-data-easily-accessible-and-fully-understood-90271463f13e">Making data easily accessible and fully understood</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How our challenge as a data consultant led to the joy of a new solution]]></title>
            <link>https://medium.com/dscribe-data/how-my-challenge-as-a-data-consultant-lead-to-the-joy-of-a-new-solution-c7ed87f8c480?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/c7ed87f8c480</guid>
            <category><![CDATA[data-catalog]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-discovery]]></category>
            <category><![CDATA[metadata-management]]></category>
            <dc:creator><![CDATA[Pieter Delaere]]></dc:creator>
            <pubDate>Tue, 30 Nov 2021 08:27:49 GMT</pubDate>
            <atom:updated>2022-01-24T08:20:07.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The dScribe portal: making data easily accessible and fully understood" src="https://cdn-images-1.medium.com/max/1024/1*Z2uu3LGx045uzti0yP6hnw.png" /></figure><p>I always counted myself lucky to have had the opportunity of starting my career in data &amp; analytics. In short, my years as a data analyst, consultant and senior consultant can be summarized as follows: I developed hundreds of reports, helped implement and carefully document a number of state-of-the-art data warehouses and supported a number of companies in rolling out self-service reporting, training and coaching business users to build their own reports based on the available data.</p><p>During these various assignments, I saw <strong>the value of data</strong>. I witnessed organizations relying more and more on data to make strategic decisions. I shared joy with a financial controller who went from having to spend 4 hours every Monday morning wrestling with Excel to prepare his weekly sales report, to doing the same with a refresh button in under 3 minutes. And I was amazed by some of the self-service dashboards, built by users I coached.</p><p>However, I also saw<strong> the struggle</strong>. When I looked at the usage of all those reports I developed, it turned out only a fraction of them had been opened in the previous months. Also, nobody ever read the documentation I spent so much time on. And I saw those self-service analytics rollouts lead to confusion, lots of duplicate reports and quite a few incorrect interpretations of the data.</p><p>So what was to be done? We had great capabilities to work with data, but how could we make sure business users knew which reports existed and how to easily access them? How could we make sure the data we unlocked was understood and correctly interpreted, not just by the experts, but by all users throughout the organization?</p><p>It turns out this is a challenge that <strong>metadata catalogs</strong> aim to solve. So, with a number of expert colleagues, we assessed the tools available on the market, in order to identify the right one for our clients. Our search however did not lead us to the right solution. Each option we reviewed, suffered from one of these elements:</p><p>· They were <strong>too IT-centric</strong>, focusing mainly on crawling and labeling technical metadata, interesting for IT teams but not for business users.</p><p>· They were <strong>too complex</strong>, including a steep learning curve and simply adding another data tool to the pile users already needed to be able to work with.</p><p>With the support of 2 customers who had joined us in our search for the right solution, we decided to start developing our own product, building further on a comprehensive KPI framework I had started to work on with a few colleagues in 2017 (KPIs have always been a hobbyhorse of mine). Three principles guided us in our efforts.</p><p>We wanted a solution that is <strong>easy</strong>. Simplicity of the metadata model, user-friendliness of the user-interface, minimal efforts to deploy a new tenant… All aimed at making it as effortless as possible for our customers to set up and start getting value from their data.</p><p>We wanted a solution that is <strong>flexible</strong>. Each customer has its own specific needs when it comes to documentation and workflows. We created a robust foundation to jump-start new customers in a very open and configurable way, allowing customers to tailor the solution to their reality, including extensive configuration via the interface and custom integrations via APIs.</p><p>We wanted a solution that is <strong>fun</strong>. Because let’s be honest. Searching for the right data is a pain and frankly a waste of time. Nobody likes writing documentation on data, let alone keeping it up-to-date. We make users do as little of that as possible, by automating maintenance of the catalog and by making contributions to the documentation effortless and rewarding.</p><p>The result of this work is the <a href="https://dscribedata.com/"><strong>dScribe catalog</strong></a>, the most intuitive and easy-to-use data discovery and governance solution on the market.</p><p>Today, I am proud to say that thanks to its early adopters, dScribe has become an official product company, fully focused on making our solution available to a broader audience. At dScribe, we believe the greatest opportunity related to data remains largely untapped: the people working with it. We are here to change this, by making data easily accessible and fully understood.</p><p>If this topic resonates with you in any way, please don’t hesitate to send me an <a href="/service/mailto:pieter.delaere@dscribedata.com">email</a>. We have helped several organizations in multiplying the value of data for their users. We’d love to do the same for you.</p><p>Until then, be Data Brilliant, and leave no (data) stone unturned!</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>About dScribe</strong></p><p>dScribe was launched by a team of experienced professionals passionate about helping organizations establish their own data democracy. Too much time and resources are spent on the IT and compliance side of data and not enough on efficiently governing and enabling data usage.</p><p>Based on a proven, battle-tested &amp; carefully improved metadata management framework, dScribe offers you an elegant &amp; powerful way to catapult your organization to the next level of data maturity. Leverage templates to add value from day 1. Adapt, enhance and tailor to your needs as you grow.</p><p>Interested? Drop us an <a href="/service/mailto:info@dscribedata.com">email</a> and let us know how we can help!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7ed87f8c480" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/how-my-challenge-as-a-data-consultant-lead-to-the-joy-of-a-new-solution-c7ed87f8c480">How our challenge as a data consultant led to the joy of a new solution</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IT shouldn’t limit corporate agility]]></title>
            <link>https://medium.com/dscribe-data/it-shouldnt-limit-corporate-agility-164689861801?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/164689861801</guid>
            <category><![CDATA[digitalization]]></category>
            <category><![CDATA[erp]]></category>
            <category><![CDATA[agility]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[docs]]></category>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Wed, 22 Sep 2021 12:00:13 GMT</pubDate>
            <atom:updated>2021-09-22T11:59:46.422Z</atom:updated>
            <content:encoded><![CDATA[<p>This summer’s Harvard Business Review focused on companies’ ability to adapt. Agility is high on every successful company’s agenda. Key to this success is the ability to execute. An unlikely bottleneck is appearing in the one department that should be bringing agility and speed. And it’s not even their fault! The IT department is victim of its own success. Indeed, in three decades, businesses have evolved to relying on IT for supporting most of their activities. Three decades may seem long but think of it: early nineties IT was limited to replacing typewriters and ledgers. A short period of point solutions was followed by a major effort to implement centralise IT around a single technology and, often, vendor. This was the golden age of ERP. We’re not saying ERP is dead but it seems the monolithic approach to IT is being questioned. Reasons often quoted are “ERP is expensive”, “one doesn’t fit all”, “we’re too dependant on one vendor”, etc. They’re all valid arguments. And we’re seeing more and more hybrid IT landscapes indeed where the core ERP is completed by functionality through adding best-of-breed solutions for instance. Also, M&amp;A activity has given rise to companies running on multiple ERP’s. At best it’s the same vendor but often it’s not. As everybody knows, (IT) integration efforts are long and expensive. And the impact of having to change puts extra weight on people, especially in the case of an already stressful takeover. Instead of starting harmonisation efforts right away, businesses take a more strategic, long term approach.</p><p>The whole thing, whichever approach one takes is confrontational though. In a previous life, we sold a best-of-breed solution to a multinational that had ERP from a single vendor. But they ran two separate instances; one for each half of the globe. We focused on implementing our tool on the instance of the headquarters. This was a very complex integration and we were up and running in six months. After going live, our client would then do the same with the second ERP instance. This took them about a whole year. First question is why that second integration took so long. Shouldn’t it actually be shorter than the first one? The whole functional analysis was done and we knew after the first integration where to find and how to connect to the data. Unfortunately that’s not how things went. First, it seemed that the ‘other half of the world’ needed to be convinced of the initial functional analysis. Luckily, the ended subscribing to the original thesis but it took some convincing. Second, and that’s the big one, the second ERP instance was configured totally differently than the first one. Remember: same technology! Because they were separate implementations, not all data was the same in both systems and, even more difficult to resolve: not all data meant the same thing. So you’d find a data point “size” and it’d be different to the one in the other ERP. Reconciling metrics (i.e. centimeters and inches) takes work but it isn’t complex. Knowing that one SIZE measure refers to size of the pallet whereas the other refers to the size of the actual item is harder to discover. So the whole integration process meant they had to go through each data point and consult people from the business in order to get the correct interpretation.</p><p>The example above is real and it’s not a lone example. I’ve seen this happen many times. The cost to these enterprises is very high: longer implementations often involves paying external consultants, it takes internal teams off of their day job and it delays putting the solution into production. Lost savings or lost income from that delay is often forgotten from cost calculations! We’ve also noticed in several cases that people when questioned about the meaning of their data answer “they’ve asked me the same question for that other IT project”. This means that knowledge exists but is not managed efficiently. What’s worse than investing in something that goes unused?</p><p>The key message for IT departments is twofold:</p><p>- it can be avoided</p><p>- it can be solved beforehand</p><p>Set up a central, easily accessible repository for all your data. And don’t just record what you have, but include the where, how it’s defined (across systems if it exists in multiple locations) and what it means. Make this repository accessible to not just the IT department but ideally include the whole organisation. Besides being easily accessible, it should also be easily searchable. This avoids people wasting time having to ask others and waiting for answers. Such a repository avoids having to ‘find out’ on the job and avoids a lot of the time wasted on the integration project. At the same time, it also allows the hybrid landscape to be efficient.</p><p>The time dimension is the most undervalued one in business strategy. If anything, when decisions and actions are taken is more important that what is done. Some products are released only to flop only to become hits when another vendor brings it to market a few years later. Is the success due to that vendor’s genius or did timing play a bigger role? In our case, implementing that central repository should not be done when the need arises. Instead, it should be core to any company’s IT strategy. Setting up and maintaining a central catalog, dictionary and glossary for all your data allows for a smoother roll-out and maintaining of systems integration. And, done well, it can relieve IT of most support calls pertaining to data as business users find their own way through the maze of IT systems, whether they be single- or multi-vendor.</p><p>Maintaining such a central repository is like basic hygiene for IT and data departments. The more agility is demanded from companies in order to maintain relevance and competitiveness, the more attention should be put paid towards basic hygiene. It allows your workforce to act and react more swiftly and to the point whereby instead of resisting, they may embrace change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=164689861801" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/it-shouldnt-limit-corporate-agility-164689861801">IT shouldn’t limit corporate agility</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data doesn’t work for you the way it could?]]></title>
            <link>https://medium.com/dscribe-data/data-doesnt-work-for-you-the-way-it-could-6ebfcf8e214f?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/6ebfcf8e214f</guid>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Tue, 14 Sep 2021 07:09:46 GMT</pubDate>
            <atom:updated>2021-09-14T07:09:46.383Z</atom:updated>
            <content:encoded><![CDATA[<p>When discussing data-driven projects, many symptoms are referred to as ‘due to poor data quality’. That one description can hide many different causes and is a classical case of not being able to see the forest for the trees. Here are some of these symptoms:</p><p>· it takes more than 10 minutes to find data</p><p>· you rely on personal interpretation to know what the data means</p><p>· you don’t know which report tracks which KPI’s</p><p>· the company’s data team is bogged down with support requests rather than focusing on their core tasks</p><p>· data scientists complain they can’t deliver because of ‘poor data quality’</p><p>· updating existing or integrating new IT solutions takes way too long</p><p>· the same KPI doesn’t show the same result in different reports</p><p>· there are many data duplicates and users wonder which one is the trustworthy source</p><p>· too much time is lost in meetings to discuss the meaning and correct interpretation of dashboards</p><p>· business users admit they have poor trust in company data</p><p>· data resides in multiple systems; compiling reports is hard and requires IT support</p><p>· your company rolled out self-service reporting but adoption is low</p><p>· when data needs updating, nobody really knows who to turn to</p><p>I’m sure you can come up with more of these from your own experience — feel free to comment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChCPx4z40zTdHiVNmSqFgg.jpeg" /></figure><p>Whereas until recently the solution to all these issues was to push for system consolidation, corporations are increasingly finding such projects expensive and, contrary to the original intent, they tend to limit flexibility, adaptability and slow down reactiveness of the business.</p><p>More and more companies rely on hybrid IT landscapes and therefore, as a “measure of good hygiene” introduce data catalogs as the go-to place for finding and organising data and the data catalog becomes the de facto go-to place from which to access data and reports.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ebfcf8e214f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/data-doesnt-work-for-you-the-way-it-could-6ebfcf8e214f">Data doesn’t work for you the way it could?</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 3P’s of data management]]></title>
            <link>https://medium.com/dscribe-data/the-3ps-of-data-management-84a373a759f1?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/84a373a759f1</guid>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[docs]]></category>
            <category><![CDATA[user-adoption]]></category>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Mon, 23 Aug 2021 12:59:36 GMT</pubDate>
            <atom:updated>2021-08-23T12:59:36.849Z</atom:updated>
            <content:encoded><![CDATA[<p>Referrals to “the 3 P’s” are common in management literature. A quick search on the internet gives quite a number of explanations for the abbreviation “3P”:</p><ul><li>Product, Price, Place</li><li>Third Party (procurement, architecture, integration)</li><li>Triple Play (television, telephone, internet access)</li><li>Third Player</li><li>Three Pointer (basketball)</li><li>Proven, Probable, Possible (oil industry classification)</li><li>People, Process, Product</li></ul><p>Of these, “product, price, place” is the most commonly taught one in business school. Today, we introduce a slight twist on that one with regards to effective data management: policy, process, people. Let’s take a look at these 3P’s in more detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsaTxH-Q0ooSUiBdNYEIVA.jpeg" /><figcaption>Data is everywhere; people get lost</figcaption></figure><p><strong>Policy</strong></p><p>Your data management policy really refers to the fact that, as a business, you have a plan about data. What this means is that you’ve decided on a — hopefully company-wide — approach to dealing with data. This starts with recognising that there is data and this data, more often than not is siloed and dispersed across many systems. The plan either involves tossing out all those systems and replacing them by one single entity. We’ve seen many attempts at doing so. It typically requires many years of implementation, process changes and, more often than not, frustration amongst users. A more modern approach would let systems in place in recognition than one-fits-all doesn’t really work. Heterogeneous IT landscapes consisting of ERP, CRM, SCM,… and other best-of-breed systems are becoming common because reporting tools allow users to gather data from multiple sources and combine them into actionable output. The new policy then requires a common understanding of what data you have, where it can be found and what it means.</p><p><strong>Process</strong></p><p>In order to then effectively leverage dispersed data, a process needs to be put in place to ensure the above mentioned mapping of the data. Quite like a GPS helps us find our way, the process should help us find data, find the right data, and make sure we understand what this data represents. Indeed, if we allow data to be managed by the direct users — who should be best placed to use it correctly — we must ensure that other people know exactly what that data represents. Take, for example a multinational with a European HQ and US entity. The US users may use as “purchase price” the price at which their entity buys goods, but if those goods were acquired through the HQ, that price is more likely the HQ purchase price plus inter-company pricing. For the US entity their definition of purchase price makes perfect sense, but for corporate reporting, a clear difference must be made between both definitions.</p><p>Managing the “data GPS” is complex and involves many people. To implement the process one can’t rely on paperwork alone. Just like GPS replaced maps and atlases, the process must be materialised through implementation of a tool. That tool would be a data catalog; a digitised process allowing stewards to manage and trace data and offering end users an easy and straightforward access to data stored across multiple systems. The data catalog, by its explanatory nature helps turn data into information.</p><p><strong>People</strong></p><p>A good friend of mine likes to say “a fool with a tool is still a fool”. He does this to emphasise that, however good a tool may be, the person handling the tool determines the result. Therefore, tools should comply with a number of requirements:</p><ul><li>the tool must fit the purpose: depending on the planned use, certain features will be required, others “nice-to-have” and even others will be unneeded (and therefore may render implementation and adoption only more complex). When selecting a tool, seeking advice from specialised consultants is usually a good idea.</li><li>steep learning curves can kill a project before it leaves the starting blocks. Data stewards and end users will use the tool in very different ways; make sure that the training is adapted towards their needs.</li><li>the tool should be efficient and effective. It should be easy to use, accessible, able to search swiftly to all and hardly require any explanation for data consumers (efficient). Your web search engine doesn’t come with a manual either! It should also be able to find the correct data (effective). Some searches may yield a multitude of possible answers. Similar to a search engine, answers should be classified according to likely importance for the person searching. This can be through ratings (by other users), division of the person searching, etc.</li></ul><p>Adoption of the tool and continued usage are key for the success of your data management project. People are emotional beings and we must overcome the initial resistance to change when introducing a data catalog. This is achieved by the efficiency and effectiveness mentioned before. But research has shown that participative systems in which users remain engaged and are encouraged to provide feedback or participate in building out the content not only achieve faster adoption but maintain higher usage rates. User engagement is different for all. While many users are quite happy to just use the GPS, others are enticed to rate and leave comments (as per Google reviews or YELP for restaurants). Being able to contribute increases people’s sense of purpose and before you know it, you have a real data community.</p><p>As you may have guessed by now, while we build the tool, effectively helping to materialise the process, our true focus is on the people. People are the critical success factor of your data management project. Policy and process can be bought (consulting, tools) but the support of your users must be won. Therefore, whatever you do, make sure that your people will want to use the tool. While this can be as simple as “like that tool better”, emotional hurdles are harder to overcome than anything else. And it doesn’t depend on features alone, those in charge of the project will have the important task of picking the tool that will eventually incite the highest usage. As history has shown, you’d rather have picked the iPod than the Zune…</p><p>Therefore, in a spin on the classical “3P” expression, the 3P’s of data management really are People, People and People.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84a373a759f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/the-3ps-of-data-management-84a373a759f1">The 3P’s of data management</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data is the new oil — start digging!]]></title>
            <link>https://medium.com/dscribe-data/data-is-the-new-oil-start-digging-8d5e38c1eef3?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/8d5e38c1eef3</guid>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-catalog]]></category>
            <category><![CDATA[metadata]]></category>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Thu, 19 Aug 2021 12:08:13 GMT</pubDate>
            <atom:updated>2021-08-19T12:08:13.046Z</atom:updated>
            <content:encoded><![CDATA[<h3>Data is the new oil — start digging!</h3><p>Imagine your backyard were located right above an oil field. And you knew about it. Somehow though, you never got to installing a drilling rig. Can’t complain about missing the pot at the end of the rainbow then, can you?</p><p>Well, this is exactly the kind of situation we encounter all the time; companies are awash with data, the C-suite keeps repeating the mantra “data is the new oil”, yet, somehow, they never started drilling. Sure, shovels and pick axes, yes. But really drilling? With the right equipment? Nah.</p><p>So far for similarities though. Contrary to discovering petroleum, drilling for and exposing data is not very capital intensive. Nor does it require physical labor. And that may be part of the problem. Companies are using their data on a daily basis. Some of them actually do quite a decent job given the tools they employ. Very few though actually know if and how well they’re using their data resources or what state those resources are in.</p><p>One of the challenges facing corporates is the disparity of data sources. Data may originate in different systems, be maintained by different people or even started life in different companies altogether (as in the case of post-M&amp;A). Also, whereas the 90’s saw a push towards centralization and unification around massive ERP deployments, the 20’s see an uptake of backbone plus best-of-breed and the corporate IT landscape becomes more heterogenous. It’s as if a company would have different warehouses, some storing similar parts, some storing different parts. In the end, in order to manage and deploy the inventory efficiently, one needs a good inventory management system. We’ve gotten so far that this is a given. Why then, are data not yet viewed as inventory?</p><p>Data have long been part of the technical domain. But as business users have increasing demand for using data, i.e. for self-service BI, companies have discovered that users don’t always access the right data, understand the data correctly or plainly don’t find the data altogether. In which case they need to ask IT again. And IT often discovers there may not be a single source for the requested data. Thus, we must put in place a data inventory management (for both technical — IT — and business data). Enter the Data Catalog.</p><p>This Data Catalog is nothing else than a layer above all your data systems to tell you the “what, where, how to access” of all data. For end users, this means that through a single access point they can find any data, get a clear understanding of what this data point represents and how to access that data point from a technical point of view so it can easily be incorporated in a report for instance. Similarly, the Data Catalog will allow the user to find reports that incorporate the searched data point.</p><p>The Data Catalog allows people, whether they’re technical or business users, to track down data. The current process often involves asking data specialists. This creates avoidable non-value-add overhead for a team that would rather (and better) use their time analysing the data instead of merely helping end-users access it.</p><p>A good Data Catalog though has to do more than just be the altas of data. Instead, it should allow enriching of data so that it becomes searchable like we search the web. And the found data should be actionable. All this leads to finding data according to relevance, not just by exactly matching search terms.</p><p>Success of a Data Catalog implementation can be measured through adoption: do your users connect to and employ the catalog? Population of the catalog is automated as the tool crawls corporate systems in search of data and reports. The Data Catalog is inherently dynamic, brings down data silos and reduces data inconsistencies. Appointing data stewards lets the best placed people validate and enrich the catalog and more often than not, several people must contribute. This means that the Data Catalog must be a true collaboration tool. A good tool thus leads to more people (effectively) using data, increases data literacy and data quality.</p><p>Most companies report “rapid ROI” just by reducing time spent for searching and finding data. Most companies avoid reporting how much they saved by avoiding data inconsistencies, wrong interpretation and usage of data, etc. but a general consensus is that Data Catalogs lead to:</p><p>- improved efficiency</p><p>- better decision-making through improved data comprehension</p><p>- better data consistency / quality</p><p>- better compliance</p><p>In this day and age of digitization, employees’ effectiveness is enhanced by smart data usage. So let’s empower our employees by equipping them with the right tools. Now more than ever, speed of action is important and we want to make sure our employees can access data rapidly but also avoid they use the wrong data or use data wrongly. The Data Catalog is the tool for the trade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d5e38c1eef3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/data-is-the-new-oil-start-digging-8d5e38c1eef3">Data is the new oil — start digging!</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A conversation between 2 Chief Data Officers]]></title>
            <link>https://medium.com/dscribe-data/a-conversation-between-2-chief-data-officers-2f1ea10d49e8?source=rss----517f32502aa9---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f1ea10d49e8</guid>
            <category><![CDATA[data-discovery]]></category>
            <category><![CDATA[data-catalog]]></category>
            <category><![CDATA[data-governance]]></category>
            <dc:creator><![CDATA[Pieter Delaere]]></dc:creator>
            <pubDate>Tue, 17 Aug 2021 08:58:29 GMT</pubDate>
            <atom:updated>2021-08-17T08:53:26.471Z</atom:updated>
            <content:encoded><![CDATA[<p>Two Chief Data Officers meet during a cocktail party. They start to talk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZiCRnC1oUHOTaw1hPxzaSg.jpeg" /></figure><p><strong>[Chief Data Officer 1]<br></strong>Last week, since our regular controller was out of office, our CEO asked me to report on last month’s revenue. After searching for half a day, I found four results:<br>- a Power BI report indicating an ‘Invoice Volume’ of €3.5 million, without additional documentation<br>- a second Power BI report indicating ‘Net Sales’ of €3.7 million, with some documentation on the report in an Excel stored in Microsoft Teams<br>- an embedded analytics report in our ERP system indicating ‘Total Net Sales’ of €3.5 million, with a technical explanation available via the initial ERP blueprint documentation<br>- an Excel sheet forwarded to me by a colleague, assuring me that the included ‘Net Sales’ of €3.2 million was correct</p><p>Feeling rather unsettled, I had to report these various numbers to our CEO, confessing I was not sure which one of these were taking into account intercompany sales, credit notes, transportation costs or service fees.</p><p><strong>[Chief Data Officer 2]</strong><br>Having multiple reports available isn’t necessarily bad, it’s a sign your organization is actively working with data to generate insights! You might want to consider adding a <a href="http://www.dscribedata.com/">metadata catalog</a>.</p><p><strong>[Chief Data Officer 1]</strong><br>How would this help me?</p><p><strong>[Chief Data Officer 2]</strong><br>A good metadata catalog consists of a glossary, data dictionary and data catalog combined in one. With intuitive access for all data users across the organization, this enables anyone to easily find and understand data insights, wherever they are coming from.</p><p><strong>[Chief Data Officer 1]</strong><br>Alright I’m triggered, tell me more.</p><p><strong>[Chief Data Officer 2]</strong><br>While supporting a data and analytics landscape, it can be hard to keep track of all existing reports, queries and data sources throughout the organization. That’s why it’s no luxury to have a data catalog that automatically detects and catalogues the full range of your data assets, no matter where they are located.</p><p>This way, you have all your data assets in one place, which is great! To make sure your users easily understand the content of your catalog, you can maintain a structured set of KPI and data definitions in a transparent data dictionary.</p><p>Finally, colleagues across functional departments and geographical regions often speak their own language. Customer, GDPR, SKU, YTD… You’ve probably heard it all. To make sure everyone speaks the same language and interprets specific terms correctly, a glossary can help. Any term in the glossary can then be referred to when documenting your assets or data definitions.</p><p><strong>[Chief Data Officer 1]</strong><br>Not bad! That does sound like a lot of work though…</p><p><strong>[Chief Data Officer 2]</strong><br>Yes and no. Growing in data maturity is a continuous journey. However, deploying a cloud-native data catalog and leveraging its out-of-the-box connectors can be done in a few days’ time.</p><p>Enriching your catalog via harmonized KPIs, data definitions and glossary terms can be done iteratively over time. I always recommend to be ambitious, but not afraid to start small. Starting with 1 domain, your 20% most popular reports or a key business unit could be the best way to experiment, learn and help boost user adoption.</p><p>For areas where you can’t yet provide dedicated support, you can choose to trust your users’ expertise and give them a centralized way to contribute and share their data knowledge.</p><p><strong>[Chief Data Officer 1]</strong><br>This indeed seems like a good approach to avoid ambiguity across our reporting and to be able to work with data more efficiently. I would love to have that realized!</p><p><em>Interested to hear how a metadata solution can help your organization gain more value from its data? Reach out via </em><a href="/service/mailto:pieter.delaere@dscribedata.com"><em>pieter.delaere@dscribedata.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f1ea10d49e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/a-conversation-between-2-chief-data-officers-2f1ea10d49e8">A conversation between 2 Chief Data Officers</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>