Top 10 Web 3.0 technologies to pump up businesses in the years to come
Explore the most well-recognized web 3.0 technologies and witness how they are changing the current business landscape.
What kind of technology can be considered as the most promising and useful for business? Artificial Intelligence, Internet of Things, and big data? It depends on the industry specifics of a particular company and the processes that need to be improved, you say. And you are right. But does it really matter which innovations are introduced into the business to transform it, if the IT solutions’ related data is not prepared in any way and it looks like a kind of chaos? In any case, the company won’t get the results that it was expecting: customer dissatisfaction, inefficient resources management, and the inability to determine threats. Garbage at the entrance – garbage at the exit, as George Fuechsel, who used GIGO as a training method, said.
Strategic data management (quality assessment) is called Data Governance (DG), and practical (quality improvement) is called Data Management (DM). The fact that these concepts are not interchangeable was proclaimed by Michele Goetz, Forrester Chief Analyst. To make it easier for the audience to feel the difference between them, data officers from one of the biggest IT providers compared data processing and cooking. So, Data Management is like kitchen shelves that store products and all the cooking equipment, and Data Governance is the recipes/instructions that help to correctly dispose of a large number of ingredients and use the equipment to make a delicious dish out of them.
In other words, competent Data Management is impossible without a well-thought-out data management strategy. DM tools (i.e., ETL systems or MDM solutions) are standardized and they can be configured to work with specific data and processes. Data Government, on the contrary, is a unique plan that takes into account features and specifics of the particular company.
Each company should have its own Data Governance. According to Vimal Vel, Vice President of Dun & Bradstreet (a provider of data solutions), many of their customers are inspired by the idea of Data Governance and immediately begin to develop a strategy, without paying attention to the preparation, which should be, definitely, the preliminary (zero) stage of Data Governance. As our own Avenga experience with data solutions and services implementation proves, no one can proceed without it. At the beginning, you need to understand the stage of the business regarding DG and what you’d like to get after a certain time – most of the data that is being worked on as part of the strategy should be related to business performance.
Surveys show that many companies aren’t clear in considering strategic data management. In particular, only 48% of survey participants, conducted by First San Francisco Partners, had a program for their information processing. Meanwhile, there are several understandable principles that the Data Governance strategy is based on:
Many organizations want to share data sets across the enterprise, but taking the first steps can be challenging. These challenges range from purely technical issues, such as data formats and APIs, to organizational cultures in which managers resist sharing data they feel they own. Data Governance is a set of practices that enables data to create value within an enterprise. When launching a data governance initiative, many organizations choose to apply best practices, such as those collected in the Data Management Association’s Body of Knowledge (DAMA-BOK). While these practices define a desirable end state, attempting to apply them broadly across the company as a first step can be disruptive, expensive, and slow to deliver value. Here are six main DG principal things, described by John Klein in the “Six Things You Need to Know About Data Governance” publication.
First, Consumers need to know what data is available and whether that data set is appropriate for their use:
The data set needs to pass these tests before moving to the next category.
The second category (Data Set Semantics) addresses concerns about the meaning of the complete data set:
The third category focuses on the meaning and structure of each record in the data set.
The fourth category covers concerns about accessing the data set, such as is it reachable, what are the interface protocols and APIs, and how is access controlled.
Finally, Consumers are concerned about quality of service. The data sets that they use must be delivered with availability and performance that is consistent with the requirements for the applications that they are building.
An enterprise data catalog is a mechanism to capture and communicate this information about data sets within the enterprise. The data catalog is a repository that contains information about the data sets (i.e., metadata) that are available in the enterprise. There are commercial products that implement metadata catalogs; however the initial version of the catalog can be implemented using any lightweight technology that supports searching or sorting, such as a wiki, SharePoint site, or even a shared spreadsheet. If you start with a lightweight implementation, you can decide what features and scale you need and migrate to a commercial product if needed.
→ Read how the business domain knowledge plays a vital role in providing software quality.
Combining the six principles discussed above, the playbook for lightweight data governance can be described as follows:
Step 1: Identify your high-benefit decisions. These decisions might be infrequent but high impact, high frequency but low impact, or something in between.
Step 2: Identify the data sets that support your highest-benefit decisions.
Step 3: For each of those data sets identify the producer-consumer relationship. If it is a one-to-one relationship, then little or no governance may be needed. If it is a one-to-many or a many-to-many, then governance may increase value.
Step 4: What constraints should you impose on the Producer? How will data Consumers need to adapt? Use the Data Consumer Concerns framework described above to identify possible governance actions. At each point, balance costs and benefit to keep value positive.
Step 5: Repeat Steps 2, 3, and 4 for each high-benefit decision identified in Step 1.
Step 6: Periodically review your list of high-benefit decisions for changes and introduce or remove governance constraints using a data set value to guide decision making.
A data governance framework is a set of data rules, organizational role delegations and processes aimed at bringing everyone in the organization onto the same page.
There are many data governance frameworks out there. As an example, we will use the one from The Data Governance Institute. This framework has 10 components; let’s discuss it in detail.
The master data can be described by the way that it interacts with other data.
A mission and vision that states why Data Governance is essential within our organization. At best, this should be related to the business objectives of the enterprise. This should be endorsed by top management.
The short-term and long-term goals for the Data Governance program as well as the success criteria and their measurement. Often this should address the main pain points that exist in various lines of the business. This must be aligned with the funding and other involved line management.
Data rules and definitions in the form of data policies, data standards, and data definitions preferable as a business glossary, as well as how business rules transform into data rules. This should cover the data assets describing the core business entities essential to meeting the business objectives. The data governance office/team will work with data owners and data stewards to set this up.
Engagement of data stakeholders in the roles of data owners, data stewards, data custodians, and others who are accountable and/or responsible must be consulted or should be informed.
The Governance Office / Team should be organized to support the cross-functional data governance structures and activities. It collects metrics and success measures and reports on them to data stakeholders. It provides ongoing stakeholder care in the form of communication, access to information, record-keeping, and education/support.
Last, but not least, a set of standardized, documented, and repeatable processes must be deployed with the right balance of enabling technology. The orchestration of data governance processes will ultimately determine the success – or failure – of your data governance framework and the ability to grow in data governance maturity.
Measuring your organization up against a data governance maturity model can be a very useful element in making the roadmap and communicating the as-is and to-be part of the data governance initiative and the context for deploying a data governance framework.
One example of such a maturity model is the Enterprise Information Management maturity model from Gartner, an analyst firm.
Most organizations will, at the beginning of a data governance program, find themselves in the lower phases of such a model.
Phase 0 – Unaware: This might be in the unaware phase, which often will mean that you may be more or less alone in your organization with your ideas about how data governance can enable better business outcomes. In this phase, you might have a vision for what is required but you need to focus on much humbler things such as convincing the right people in the business and IT about smaller goals around awareness and small wins.
Phase 1 – Aware: In the aware phase, where lack of ownership and sponsorship is recognized and the need for policies and standards is acknowledged, there is room for launching a tailored data governance framework addressing obvious pain points within your organization.
Phases 2 and 3 – Reactive & Proactive: Going into the reactive and proactive phases means that a more comprehensive data governance framework can be established covering all aspects of data governance and the full organizational structure that encompasses data ownership and data stewardship, as well as a Data Governance Office / Team, in alignment with the achieved and to be achieved business outcomes.
Phases 4 and 5 – Managed & Effective: By reaching the managed and effective phases your data governance framework will be an integrated part of doing business.
If your current data governance policies and procedures are your guidebook, the maturity model is your history book. It’s compiled from historical data based on a maturity assessment, which compares a company’s performance to established goals and benchmarks over a given period – a quarter, for example, or a year, or even five years. The model shows where you’ve been, which helps shape where you’re going.
While a “one-size-fits-all” approach doesn’t really work for a maturity model, an “if-the-shoe-fits” approach works well for many companies. Search for existing models, find one that’s close, and adjust it to meet your company’s needs. If the shoe doesn’t fit, it’s easy to change the size of the shoe. It’s not so easy to change the size of your foot.
Data Governance is the strategic approach. Master Data Management (MDM) is the tactical execution. That’s it. We’re good. You can go home now.
Not convinced? Ok. Don’t take our word for it. As promised, we’re back with Scott Taylor of MetaMeta Consulting. He has forgotten more about master data than most of us will ever know, so we’re happy to give him the last word.
“All enterprise systems need master data management,” Scott said at our Profisee 2019 kickoff event. “Marketing, sales, finance, operations. There is benefit everywhere, in enterprises of any size, in every industry, across the globe, at any point in their data journey.”
Master data is the most important data, Scott said, because it is the data in charge. It’s about the “business nouns”–the essential elements of your business: customers, partners, products, and services. Whatever your business is, that’s where master data lives and breathes. You may have the best governance plan on the planet but well-governed bad data is still bad data. It’s not going to help your business.
“Everybody is in the data business, whether they realize it or not,” Scott said. “Everything we touch turns to data. Business is transforming from analog to digital. No matter what your product is, data is your product. Business is changing because of data, and data is power.”
“With the right tools, you can harness that power right now.”
We couldn’t have said it better ourselves.
The increasing awareness around data protection and data privacy, for example, manifested by the European Union General Data Protection Regulation (GDPR), have a strong impact on data governance.
The terms of data protection by default and data privacy by default must be baked into our data policies and data standards especially when dealing with data domains as employee data, customer data, vendor data, and other party master data.
→ Explore more Essentially, Data is good. It’s the use cases that can be problematic
As a data controller, you must have full oversight over where your data is stored, who is updating the data, and who is accessing the data and for what purposes. You must know when you handle personally identifiable information and do it for legitimate purposes in the given geography, both in production environments and in test and development environments.
Having well-enforced rules for the deletion of data is a must too in the compliance era.
On the one hand, you can learn a lot from others who have been on a data governance journey. However, on the other hand every organization is different and you need to adapt data governance practices all the way, starting from the unaware maturity phase to the nirvana in the effective maturity phase.
Nevertheless, please find below a collection of the 15 short best practices that will apply in general:
At Avenga, we craft digital experiences that define the success of your business. Being around for over 20 years, we have been exploring, experimenting and implementing data solutions and services to make data work for your business needs.