Why GDS and tech industry collaboration must underpin Government as a Platform
By: Carlos Oliveira on
5 minutes to read
As GDS regrouped after a series of high profile exits, including Bracken himself, and the dust settled on their remit of delivering digital exemplars more and more focus appeared to be going into the direction of Government as a Platform
As a technologist I am full of admiration for the work that Mike Bracken oversaw during his time in charge of the Government Digital Service (GDS). It is impossible to argue with their design principles that focus on user need, agile development and open standards. However, having now been a part of the TechUK Public Services Board for around 15 months and latterly in my role as Vice-Chair, it is fair to say that GDS has had an uneasy relationshipwith some of the largest suppliers of technology to Government.
As GDS regrouped after a series of high profile exits, including Bracken himself, and the dust settled on their remit of delivering digital exemplars more and more focus appeared to be going into the direction of Government as a Platform. Yesterday’s spending review confirms that GDS and GaaP will take an even more prominent role in the Government’s digital transformation over the next 5 years with a doubling of their budget to £125m per year and the following tweet from the Cabinet Office:
So, if GaaP is here to stay what does this mean for the technology industry and what role will GDS play in delivering it? The most recent GDS blog on Government as a Platform by Felicity Singleton was extremely encouraging as it is the first time I have seen GDS recognise the role that the technology industry at large will have to play in making this initiative a long-term success.
One phrase in particular caught my attention:
“If we create platforms based on open standards and interoperability, we automatically create competition and drive innovation. That means more providers and lower costs.”
I fully support the drive to encourage new entrants into the market and lowering the barriers to entry. However, I do challenge the idea that it is the role of GDS to create every one of these platforms and would instead suggest that they should instead look to define what is required from each. Publishing the specifications for each of the platforms and encouraging industry to respond will allow GDS to achieve three key objectives:
Decrease the time-to-market for the platforms by potentially leveraging what already exists in the market.
Help new and existing suppliers understand the rules of engagement for their digital services so that they are clear that when building a new solution, it is integrated into GaaP from the outset.
Maximising the investments already made in Government IT by enabling incumbent suppliers the opportunity to rework their products in-line with the new platform definitions.
I fully appreciate that there will be some platforms where GDS is the only organisation able to effectively lead the design and build due to its cross-departmental reach. However, I sincerely hope that it is not GDS’s intention to build each and every one of them and that is where industry must be included.
The role of GDS with regards to GaaP should be that of a Product Owner in an Agile development project. Working with users (departments, civil servants etc.) defining their needs and translating those into stories and deliverables that the technology industry can deliver against. This is a complex, long-term project and it needs the centralised skills and talents at GDS to pull it all together. Equally it needs the scale and reach of some of the worlds largest technology providers and the innovation and agility of smaller SME’s like ourselves to ensure that it can be built and delivered in the most economical way possible for the taxpayer.
Only by GDS and the whole industry collaborating can GaaP be delivered and that should be inclusive of all suppliers, both big and small, as the blog states:
“Everything’s built on standards and designed to interconnect. You swap out the old and snap in the new. Users don’t need to notice, or even be told (unless the service offered to them is changing).”
By allowing existing service providers to update their interfaces to comply with the standards of GaaP, Government has an opportunity to asses a variety of options for each discreet platform and to decide on the most appropriate solution. The equation is still a classic Build vs Buy but in either scenario the key factor, interoperability and integration is front and centre, there is no compromise on that.
From our work in the US, I know that this shared approach continues to build within all western governments, with a focus on collaboration and structure. As noted on whitehouse.org:
“The shift to a shared platform culture will require strong leadership at the government-wide and agency levels. Agencies must begin to look first to shared solutions and existing infrastructure…”
This shift truly begins to level the playing field, allowing more disrupters to emerge for the greater good of citizens and public sector employees who are looking for enablers to improve the interaction within government.
Ultimately the successful delivery of GaaP requires all of the stakeholders, GDS, the departments, existing suppliers, new entrants and start-ups to work together towards the GaaP common goal. Each one has a role to play and something unique to bring to the equation and it is this eco-system that must underpin the entire project delivery.
About the Author
Founder of SPINR, Carlos has been advocating how the use of a SOA approach based around API's can provide the platform for true transformation in the Public Sector. Aside from SPINR he is also the Chair of the techUK Local Public Services Committe that aims to improve the engagment between the public sector and the IT industry.
Before you go...
why not check out our latest whitepaper
'Funding Cloud Services in Public Sector Organisations'