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.
Since our last update, the adoption of GaaP products has accelerated. We are now supporting more than 400 services from 120 organisations across the public sector.
Ashley Stephens takes a look at the work we’ve been doing behind the scenes, some of which will be showcased at Sprint 18 by teams across government.
The health sector is starting to use GaaP products. Arms length bodies and NHS hospitals and trusts are among the early adopters. In this blog post we’ll look at the benefits our products are bringing to the health sector.
We’ve been inspired by the innovative ways in which councils are using our products - below are some examples, and we'll hear from the people using our products who explain how they meet the needs of their users.
Lisa Keenaghan is the Digital Service Manager at the Disclosure and Barring Service. In this post she talks about how using the Government as a Platform (GaaP) product suite has helped to transform the DBS service.
In this post we talk to 2 service teams about how GaaP products have made things better for their users.
One year on from the launch of the Government Transformation Strategy, Ash Stephens introduces a week of stories from teams across government showcasing the benefits and maturity of common components.
In this post Anais Reding discusses how over 100 services across 26 departments and agencies are now using GaaP tools, guidance and components.
We’ve learned that if we can make it easy for service teams to improve and publish accessible forms, these teams will make things better for millions of people. So we’re starting an alpha to explore what this might look like.
We ran a discovery to work out what Government as a Platform components we should look at next. In this post, we talk about our findings and why we're now looking into how services, particularly those without access to a software development team, can more easily collect information from their users.