Government as a Platform is a phrase coined by Tim O’Reilly in 2011 and defined and redefined by all sorts of people, organisations and governments ever since. This post offers a whistle stop tour of about 20 definitions and descriptions before condensing them all into one:
Reorganizing the work of government around a network of shared APIs and components, open-standards and canonical datasets, so that civil servants, businesses and others can deliver radically better services to the public, more safely, efficiently and accountably.
There’s a lot of concise power in that and if the intention is to focus primarily on the platform, it works pretty well. But if the intention is to focus more on the government, it has two pretty serious drawbacks. One is that it makes the surprisingly common assumption that government is about service delivery, overlooking all the things which governments do which are not that and underplaying the place of government in a wider political system. The other is that ‘accountably’ is having to carry a very heavy weight: it is presented as ‘the equal’ of safety and efficiency, but only in relation to the provision of better services. That really matters, of course, but it is a long way from being the only thing that matters for the governments of 21st century democracies. But all that also illustrates, of course, the strength of this approach – by setting out assumptions and approaches so clearly, it becomes possible to have the debate in the right place.