As more and more services begin to adopt our Government as a Platform components, we’ve decided to post regular updates on our progress building them. This is a list of what we’ve done so far in 2017. We’ll iterate the format of these updates to make them as useful as we can.
How Government as a Platform works
Government as a Platform makes it easy to assemble digital services out of shared components, eg service patterns, products, data and a joined up approach to hosting. This frees service teams across government to spend their time on designing high quality, straightforward user-friendly services, rather than starting from scratch.
The Government as a Platform team is looking for a Policy and engagement Lead. Ben Welby explains why the team is looking for someone with a strong business to business-to-business background and what their focus in this role would be.
As Stephen Foreshew Cain said Sprint 16 was a great day and Government as a Platform was very much at the heart of it. In case you missed it or weren’t there, here’s a quick recap on the Government as a Platform highlights from Sprint 16.
We’ve drafted some principles (similar to the GDS design principles), to define how things in the Government as a Platform toolbox should be built and run.
Seb Tallents writes about Government as a Platform as a range of products, which will form a single platform on which service teams can build brilliant transactional services.
Ash Stephens explains what the different things are that make up Government as a Platform, and he gives an update on the cross government collaborative effort that underpins this transformational programme of work.