Data Strategy: Unleash the Disruptive Power of Data
Because data sits in databases and files on some server somewhere, the information technology (IT) department was historically taking care of it. As a non-IT person, all you wanted was access to the data. Somehow IT would proceed to explain just how hard this was for them to do without requirements. You would retort that your needs were "I want access to everything." You know the drill. It involves circles and the expression "going around."
Times have changed. IT now manages infrastructure and offers services, and the business is being asked to play the role of "product manager" to guide IT in leveraging this data asset. You are not a data management expert, yet you are in the driver's seat. So how will you guide IT?
You are not a data management expert, yet you are in the driver's seat. So how will you guide IT?
Thankfully, you have us to guide you. The tool we will go through today is called the Data Strategy. It is useful to look at the Data Strategy as a contract between those who need the data, a group you are part of, and those who will make sure that it is available, of high quality, and relevant, according to your expectations (within reason, more on that as we go). Imagine you are a product manager, and this is your product roadmap.
What is a Data Strategy, and Why Does it Matter?
Scour the internet, and there are hundreds of definitions. We think that a picture is worth more than a definition. That data is an asset to be harnessed is an understatement nowadays; the Data Strategy documents how the organization will come together to ensure it optimizes what it will get out of data. It creates the plan, the roadmap to get there.
There are six strategies to define:
The data asset itself
How we assign value and set priorities
Communication
The platforms and digital infrastructure
The organization, the people and the culture
As the diagram shows, the Data Strategy will define what each component means and how we expect it to be delivered. Of course, the six strategies are very connected and must work together.
A Data Strategy will likely lead to a Data Transformation, in the form of a program that will last more than a fiscal year, delivering incremental business value and the underlying required sub-components, such as operationalizing a Data Governance Framework and a Data Quality Framework. There is a good chance that it could be self-funding.
The savings will come in a few different shapes:
faster, more accurate analytical models can create sizeable revenue uplift
reduced storage and infrastructure costs (the cloud.)
improved productivity among data resources
The business case will come from answering these few questions, upfront:
What features, based on data, can transform your business model or your market position?
What area of the business is most at risk of being disrupted by data?
How can data improve profitability?
How can we use data to reduce our business risk?
What is the opportunity cost of waiting?
Can you do it with in-house teams?
When we think of opportunities like data de-duplication, redundant or inconsistent data, and automation, it's easy to see how a Data Transformation based on a solid Data & Analytics Strategy can indeed pay for itself. And don't get us started on how projects with limited budgets often put in place solutions that are either not scalable or sustainable. The Data Strategy aligns not only imminent work but also how the future will evolve.
The benefits of a solid Data Strategy are:
inform decision making;
know customer trends;
mitigating risks;
smarter services and products;
better internal operation;
More revenue.
How to balance offense and defense
The questions above highlight another aspect of the Data & Analytics Strategy: Are we trying to change the business, or are we mitigating risks and protecting something? Most organizations need to do both, but depending on your industry, you may lean one way or another. As an example, the financial industry is very regulated and one company may opt to first focus on defence or prioritize some capabilities that cover such needs as compliance with privacy laws.
Leandro DalleMule, CDO at AIG at the time, and Thomas H. Davenport wrote an article for HBR.org almost three years ago about trade-offs between "defence," and "offence" when it comes to data, between control and flexibility in its use. The article says that in highly-regulated industries, like Healthcare, we typically see a more defensive approach., whereas, in Retail, we take a more offensive approach. And 50/50 is not a good idea, based on the fact that IT will need to execute somewhat differently depending on the orientation. Read the article for more details.
How to put the business first
These principles will help in setting overall objectives. You will go down rabbit holes during your work sessions, but these principles will help you see things clearly and get back to basics if you refer to them often.
Eliminate silos;
Encourage collaboration and sharing;
Make data visible and accessible;
Dissociate the needs for protection, availability, quality, and relevance of data from the operating processes and practices required to fulfill those needs;
Establish guidelines for analysis and analytical applications;
Identify which data leads to customer lifetime value;
Identify which data leads to operational efficiency;
Identify which data measures "experience" with your products or services;
Be clear about the business outcomes you are driving for.
How to plan and carry out a Data Strategy
First, success requires some pre-conditions. To have the best chances of success, these will help:
Obtain buy-in. We have seen that organizations obtain the best results when they work collaboratively. Not all organizations have such a culture, unfortunately. No one said it would be easy;
Have a data management team that will drive the exercise for you; they will inherit much responsibility in carrying the work out, so they should be a big part of the process;
Involve all essential functions. Data can help save costs, increase revenue and change or improve your offering. So everyone can benefit and contribute. Eventually, many of those involved here will be part of Data Governance.
If you need a project plan, a Data Strategy exercise goes like this:
Assess the current state;
Define the future state (for all six components in the framework above);
Identify the gaps, especially what is preventing you from reaching the business outcomes you have identified;
Choices. The gaps may prove to be more than the organization can absorb, for valid reasons. Refine your target state so that filling the gaps become your objectives for moving forward;
Identify your transition approach based on the constraints and the business priorities of the organization;
Put together a program that incrementally transitions to your future state according to your defined approach;
Use the Data Governance function to guide the program and adapt, because one thing is a given, the plan will change;
As the program winds down, Data Governance becomes the driving force behind the evolution of your Data Strategy in the future. It continues to ensure the organization derives maximum value from data. Because it is business-driven and perfectly aligned to the business plan, it becomes easy to justify keeping all components optimized and up to date.
How to include all the latest Data capabilities
The Data Strategy should go into some level of detail, particularly conceptual architecture. For all six components previously discussed, think of a diagram that fits on one page that shows boxes and lines, sometimes with arrows, that shows what you aim to build in simple terms. A high-level data flow diagram or an organization chart both fit the objective. Here is an example from Snowflake for the Data Platform component:
As mentioned before, experts and your data management team should do this for you, with your guidance. But here is an important point: your Data Strategy must be rooted in reality. It must leverage available technology concepts. Therefore, it should include your organization's position (will you use them, why, how do they fit in your conceptual architecture and what business outcomes they will contribute to) on the following generally accepted, modern approaches to analytics:
Data ingestion, replication, and extraction-transfer-load
Data federation
Data cataloging
Master & reference data governance and data quality
Data pipelining and orchestration
Distributed big data processing
Big data databases and data storage
Cloud platform-as-a-service
Machine learning and data science
Analytics
Adaptability & agility
Automation
Collaborative functions
Data governance tools
Elasticity
Data security
Data warehouse, data lake, data marts, data lakehouse
Data zones
Unstructured and semi-structured data
Streaming
NoSQL databases
Docker and containers
Microservices
Tips and Reminders for successful Data Strategies
A checklist!
Having done a few of these, we have come to appreciate what contributes to the right Data Strategy. These are the characteristics of a successful one. It pays to remember these as a checklist.
Executive-sponsored Executives today see data as strategic assets. Unfortunately, many organizations have a hard time harnessing the value of data because of many varied factors. Conveniently, a Data Strategy sponsored at the highest level will benefit from the proper attention, an A-team assigned and adequate follow-through because executives will expect tangible results.
Unifying Another characteristic of a successful Data Strategy is that it isn't a single-department deliverable; it is an enterprise-level one, much like a Digital Strategy. Everyone who matters has been consulted and onboard. Everyone is part of the solution! There is unity, a consensus around it. It is a real collaborative effort. Most times, executive pressure certainly lubricates teamwork to get there. Everything indeed is related.
Adequately resourced (in time and people) We cannot do a great job of a Data Strategy in a week. We must allocate enough time to discuss the issues, socialize them and agree on them. Rushing things in this respect is like rushing a business strategy: quality is much more important than meeting a deadline. Allow enough time to include everyone that needs to be involved and to have an integrated product. The same goes for the quality of the team: Go broad and choose your best. It will be worth it.
Done to its full extent There are many moving parts in a Data Strategy (see the framework above). Still, they are all equally important, if not critical. Like links in a chain, the whole Data Strategy will be as healthy and as useful as the quality, effort and collaboration put in the definition of its components.
Awareness that it is a culture to be data-driven Organizations are not equal in this respect. Some will have a harder time getting there. Change management and leadership will be so essential to execute the Strategy. There will be selling involved, forums, maybe a buddy system and data literacy activities. Do not underestimate the people aspect - it is the most important.
Conclusion
There are many elements here, so we repeat that it is helpful to get outside help from a third party with no skin in the game who can guide you from a best-practices point of view. Start from the business needs always. Make sure Data Governance is business-driven. Involve your best people and do it right the first time. One advantage of a formal exercise is that not only are you documenting the roadmap and your vision but also the decisions you will take, especially in terms of compromises. Politics being what it is, contexts change and people tend to forget the situation of those that were there before them.
Comments