One year on from the general election: what does the UK data landscape look like?

A year on from the UK general election, ODI Head of Policy Ellen Broad revisits last year's 'Open data roadmap for the UK' and reflects on what has been achieved, key challenges that remain and recommendations for strengthening our data infrastructure

null Plans around data transformation within government are evolving quickly. CC BY 2.0, uploaded by [Rennett Stowe]( “Rennett Stowe").

In the lead-up to the 2015 UK general election, the ODI published its ‘Open data roadmap for the UK’. This set out steps the next government could take to strengthen the UK’s data infrastructure, and maximise the benefits of open data.

One year on, there are recommendations set out in the roadmap that are more urgent than ever; there are some that seem blindingly obvious in retrospect; and there are needs we have now that weren’t mentioned in the roadmap at all.

While the UK’s Government Data Programme – coordinated by Government Digital Service – is accelerating work on data-sharing, ethics and registers, open data remains frustratingly siloed.

The ODI’s roadmap set out nine suggestions for the next UK Government on open data, from refining its open data strategy to generating impact from open data and maximising reuse. The roadmap saw open data as a core part of a wider government data strategy – a mechanism to help uncover and map how data is used and shared inside government (as shared data), and to create value for businesses collaborating with government. This blog outlines current challenges for government highlighted in the roadmap, and emerging gaps the roadmap didn’t cover.

Key data challenges for government

The importance of data as infrastructure is not widely recognised

The ODI’s roadmap highlighted the need to build on and refine work on the UK’s National Information Infrastructure, moving beyond a static list of public sector datasets. Since the election, government work on defining and setting rules for essential data infrastructure – inside and outside government – has stalled.

Data is infrastructure – not only for the public sector, but the wider economy. It underpins public service transformation, business innovation and democratic engagement. The UK Government Data Programme espouses the importance of data infrastructure, but while a National Infrastructure Commission has been established by government, data isn’t a part of it.

There are some standout departments accelerating their investment in data infrastructure and open data. In June 2015, Secretary of State for Defra Liz Truss announced the ‘biggest data giveaway the UK has ever seen’, committing to publishing 8,000 datasets as open data in 12 months and transforming how the department uses data in general. The project goes beyond publishing more data; it’s a change to an open culture. The Ministry of Justice, DWP and NHS have all written about their own data work.

Open registers are part the UK’s data infrastructure, and the Government Data Programme has been investing in core reference data that lots of services need. But registers aren’t the only kind of data in our data infrastructure. They’ll need to supplement rather than replace existing mechanisms for publishing core data where they’re already working, via APIs and as static data assets.

The Government Data Programme has been exploring opening up core data assets that are part of the UK’s data infrastructure. The 2016 Budget included up to £5m to explore options for an open, authoritative address register. #OpenDefra has seen the release of high-value datasets like LIDAR, which provides digital elevation information for three quarters of the UK. However, the openness of data maintained by bodies that may be privatised – like the Land Registry – is at risk.

Open data in government is getting more disjointed, not connected

The ODI’s roadmap emphasised the need to embed open data as fundamental to a comprehensive data strategy for government. There’s still a team working on open data as part of the Government Data Programme, but if anything it seems open data is more fragmented than before the general election.

Responsibility for open data is now generally split across two departments: GDS and the Government Data Programme, who are exploring data use inside government which will feed into the Government Digital Strategy, and the Department for Business, Innovation and Skills (BIS), who are asking questions about open data and its use by businesses and third-sector organisations in the National Innovation Plan. The split between departments may make sense if it weaves open data into the natural perspectives and scope for policy interventions within the two departments. But joining up efforts will take strong leadership.

Data policies have not been joined up in consultations from the Government Data Programme itself, with the ‘Better use of data’ consultation noticeably missing policies linked to open data, accessibility of data via open APIs and data science ethics.

And while the focus for the Government Data Programme is public, targets and metrics for its initiatives such as for open data aren’t, making it hard to meaningfully evaluate progress.

There’s a vacuum in public-sector senior data leadership

The roadmap recommended appointing a Chief Data Officer for government, and it still seems there’s a lack of senior leadership and championing of data across government. In late March 2015 Mike Bracken was appointed Chief Data Officer for the UK, alongside his role as Executive Director of Digital in the Cabinet Office and head of GDS. Since Mike’s departure in August 2015 from GDS, no new Chief Data Officer has been appointed. As the Government Data Programme ramps up, and more departments begin to invest in data science, open data and data infrastructure projects, that authoritative voice becomes essential to champion and communicate the big picture for data in the UK; to hold government to account when things go wrong – for example, the Google DeepMind and NHS Royal Free data-sharing arrangement; and to ultimately drive improvements over time.

UK Government’s data highlights

The Government Data Programme’s work on registers – recognising certain kinds of reference data as an essential ‘spine’ for linking up public services – is a promising step that has already been mentioned above.

Open contracting got a Prime Ministerial boost

It’s also been great to see the government’s commitment to open contracting and open procurement data continued. At the 2016 Anti-Corruption Summit hosted by Prime Minister David Cameron, the UK became the first G7 country to commit to the Open Contracting Data Standard (OCDS) for contracts administered by the Crown Commercial Service. Government should go further though. To drive competition and better services, open should be baked into contracts with government, so that where data is collected, maintained, and used with public funding, the outputs are as open as possible for everyone to benefit from.

Government convened sectors to solve problems using open data and open APIs

There have been exciting initiatives outside government, with government convening support around open data and open APIs. The Open Banking Standard work – co-chaired by the ODI and Barclays – aims to make it possible for consumer banking data to be shared efficiently and securely, for citizens’ benefit. The recommendations from the Open Banking Working Group’s final report were incorporated by the CMA in its recent recommendations to reform UK banking, and work in this space continues to evolve rapidly.

UK Cabinet Minister advocated for ‘dogfooding’ open data

In late 2015 Cabinet Minister Matt Hancock became the first politician to use the term ‘dogfooding’ in an official speech in Berlin, highlighting using open data inside government as a priority for the Government Data Programme:

Government using our own data, ‘hundefutter’, or dogfooding as it is called in English, also ensures that we publish high quality data because we know what it feels like to use it. This is taken from a US Chief Executive of a dog food company who ate a can of his own product to prove its quality.

Encouraging civil servants to consume open data, not just publish it, was a recommendation from the ODI’s roadmap and it was fantastic to hear it have Ministerial endorsement. However, it’s not clear how successful this effort from the Government Data Programme has yet been in practice. This ‘dogfooding’ will be key for data publishers inside government to grasp the quality of their data, how it might be improved and how others might use it (or not be able to use it).

What did we miss in the roadmap?

Engagement with the data community

At the time going into the general election, there were a range of data-related engagement groups: the Open Data User Group (ODUG), the Government Transparency Panel, the Open Standards Board and more. Engagement with data users didn’t feature in our roadmap.

Since the election, a Data Leaders Network has been established, comprising of leaders within government, and a Data Steering Group of external data visionaries. The Open Data User Group (ODUG) hasn’t been renewed, and as yet there is no formal engagement strategy in place for communicating with the wider data community, outside of the ODI, which has been asked to reflect the needs of its members. The latest UK National Action Plan for the Open Government Partnership points to the Open Government Network as its platform for engagement on some aspects of data and open government, but again, the OGN reflects a subsection of the UK data community. Other voices and perspectives need to be taken into account, as well.

Personal data-sharing, data science and ethics

There’s work to be done to address the data trust deficit between citizens and organisations managing and using our personal data. The ODI has been working on draft design principles for managing personal data: bringing together openness and privacy to build trust. Several of these reflect requirements of the EU General Data Protection Regulation, which will be in force in the UK by the end of 2017. We’re working now to expand the principles in line with the General Data Protection Regulation (GDPR), and build practical guidelines for organisations handling data ethically.

The Cabinet Office’s data science ethical framework was launched in May. The simplicity of the framework is refreshing, and the team’s skillful use of the open policy-making process to test and adapt its recommendations is an exemplar for government. Just as data projects and what is considered ‘ethical’ evolves and changes, so the framework will adapt, with the team committed to continuing to update the framework after launch.

Open data and data infrastructure for cities and regions

Since the general election, cities have been forging their own paths on data. As the devolution deals are finalised, we’re working with our network of ODI members and UK ODI Nodes to ensure that city data infrastructure is as open as possible.

What are your thoughts?

Plans around data transformation within government, and for the UK generally, continue to evolve rapidly. Alongside GDS in the Cabinet Office, other departments are starting to grapple with their role and responsibilities setting data policies and ideas into practice – it’s part of the BIS Innovation Plan call for ideas, and fundamental to the upcoming UK-France Data Taskforce report being overseen by Treasury and the Department for Culture, Media and Sport.

What exciting work do you see happening that we should highlight? What other areas do you want to see more progress made in? How can the enthusiasm and willingness to engage with data use inside and outside government – and the role of open data to deliver this – be harnessed to contribute towards a cohesive, visionary UK Government data strategy? Add your thoughts as comments on this blog or get in touch with us at [email protected].

Ellen Broad is Head of Policy at the ODI. Follow @ellenbroad on Twitter.

If you have ideas or experience in open data that you'd like to share, pitch us a blog or tweet us at @ODIHQ.