On the week of 16th November, a select group of experts – all data leaders in leading public, private and academic institutions – came together to discuss the National Data Strategy. This article summarises the key points of discussion and consideration for those concerned with the strategy.
The National Data Strategy sets out the UK Government’s ambition for data. It provides a framework for future data policy and outlines a commitment to action. It is a key part of the UK becoming a global data leader.
The UK needs a data strategy to support efficiency and growth across all sectors. In the public sector, it will support more effective delivery of policy and public services. It will also encourage scientific development, increasing the scope and speed of new research. In the private sector, it will support business development and stimulate new markets. How these benefits are realised will depend on the choices made in the content and execution of the strategy, which was largely the focus of the discussion.
Prioritisation and choice of approach are critical to operationalising the data strategy
The need to prioritise, and the challenges of doing so, was a recurring theme of our discussion. To effectively prioritise actions within a data strategy, we first need to understand three things:
1. What are our critical data assets?
2. What value are they currently creating and what could they create in the future?
3. How are they supporting our objectives?
The structure of funding is a significant barrier. Funding is often organised vertically, by department, teams and projects. However, the outcomes of investing in data are felt horizontally, across teams, departments and sectors. By saying investment decisions have to deliver returns in one silo only, data projects may not create enough value to any single department to justify its costs, leaving a lot of untapped potential.
One helpful analogy was the distinction between data that needs an engineering approach, versus that which need a gardening approach. ‘Engineering’ is where there’s more structure, centralised control and specifically designed actions. Alternatively, a gardening approach is gentle stewardship, encouraging autonomous data use within clear structures and systems. These approaches mirror the discussion of top-down and bottom-up approaches. Particularly how policy and regulation work with an entrepreneurial approach.
The discussion was a reminder that different contexts call for different tactics, finding a balance between these approaches to suit the situation.
Data assets typically support multiple use cases across different departments of an organisation, who in turn use that data to drive activities that create value for diverse stakeholders. Prioritising data assets then is a question of understanding which assets create how much value for stakeholders and what investment is required to improve value creation.
The uneven distribution of costs and benefits of developments in data needs consideration.
The benefits of investing in and treating data like an asset, don’t always accrue to those who make the investments. Nor do we see outcomes linearly over time, with some outcomes only coming into play in the long term.
Participants repeatedly highlighted the lack of coordination around projects to improve data, and how activities in organisations are often dispersed, resulting in duplicated efforts. This raised questions of how we incentivise actors (be they public, private or third sector bodies) to do the right thing when they don’t get the benefits directly, but rather they’re transferring the value to others? It also means having robust ways to understand, compare and trade off different stakeholders’ priorities, what type of value creation we prioritise, and whose interests we serve.
Lack of clarity is an issue for the costs associated with data. Studies have shown that approximately 5% of revenues in the private sector are spent on data, but much of this is hidden because the data is siloed. For example, one organisation had six analytics teams building similar solutions on top of flawed data.
The intersection of public and private data is complex
This is a particularly complex area, bringing together a lot of the points we have already addressed.
- What is the right level of formalisation to create structure without encumbering innovation?
- How do we translate the high-level strategic outcomes to prioritised solutions?
- How do we future proof our processes so we don’t create legacies of bad data?
In addition to these questions, there is a fear in the public sector about the motives of the private sector. Is it right for the government to invest in producing and maintaining open-source data that is, in the end, used purely to pursue private profit? One interesting solution involving neutral data custodians was suggested. These kinds of practical solutions will allow us to navigate this space.
Accessibility and fitness for purpose are important, from the beginning of the data lifecycle, and are often misrepresented through analytics
We talked about how, in the public sector more data could be captured in a better condition for different use cases. We also talked about how there are many opportunities in the public sector to collect better data, and make existing data more accessible. The private sector, in particular, may need further incentivisation, and reassurances about possible liabilities, to make more data accessible.
Practically, there was talk of embedding the idea of accessibility and fitness for purpose in procurement and with IT departments (when setting up new data bases) to avoid creating legacies of even more bad data.
For asset management organisations, fitness for purpose needs to be considered from the beginning of the data lifecycle, because they tend to procure data on the state of assets, often in the form of surveys by engineers that are then manually input into IT systems. Definitions and quality parameters often are not aligned across the organisation. When data gets into analytics, with easy to use tools like Power BI, the impression given is one of impressive results, but this often rests on data that is fundamentally flawed.
Digital vs data must be considered in communication
See More Resources
A Guide To Data Valuation
A Guide To Enterprise Data Valuation
A Guide To Data Strategy
A Guide To Data Asset Management
A Guide To Data Culture
A Guide To Data Management
A Guide To Digital Transformation
A Guide To Data Monetization
A Guide To Data Governance
A Guide To Data Condition
A Guide To Data Quality
Read More Insights
Key elements of a data driven culture
The role of data in enterprise digital transformation initiatives
Why managing data as an asset is inevitable
Why you should be treating data as an asset
Different data valuation methodologies
Data quality vs data condition: the power of context
5 Reasons why a Chief Data Officer fails
Climbing the data maturity ladder