Local Government Digital Service Standard - TeaCamp #6: Assisted Digital
Dec. 8, 2017
As a network for digital practitioners in local government, LocalGov Digital is on a mission to raise standards in web provision and the use of digital by councils across the country.
The London Peer Group is aiming to focus on raising awareness of the Service Standard across the individual 32 boroughs of London, through a series of TeaCamps. Unboxed is supporting the London Peer Group by providing sponsorship and support.
The 6th TeaCamp in the LGDSS London Peer Group series has arrived. It’s been a short while since I’ve been able to attend a TeaCamp, due to being away with char.gy during the last couple of dates (Are you a local council looking for an on-street electric vehicle charging solution for your residents? char.gy may just be for you...).
The hot topic of this month’s TeaCamp is Point #12 of the Service Standard: Encourage maximum usage of the digital service (with assisted digital support if required).
With introductions and parish notices done, Hackney Council share a very brief update on some of their recent happenings, including a collaborative cross-council sprint.
For this session, we’re very lucky to have Ben Carpenter from Government Digital Service (GDS) join us.
Ben is the Inclusive Services Lead and Assisted Digital Lead and has experience of taking part in over 70 digital service assessments. That’s quite a track record. We’re eager to hear what Ben has instore for us this afternoon.
So, to begin… What is “assisted digital”?
GDS define assisted digital as “... help for people who can’t use digital government services on their own.”.
Central government provide a full range of online public services and they want to help people to be able to move through these services and achieve what they need to achieve. Assisted digital is the help that must be provided alongside these online public services for the people who need to use them, but don’t have the skills, expertise or access to be able to do so on their own. It’s all about interacting with people so they can use a digital service.
(Image via GOV.UK)
Support is usually available through offline channels, such as:
- Over the phone
Why assisted digital?
Assisted digital is:
- A service standard requirement
- Good service design
- Good transformation
- Part of “digital by default”
- A manifesto commitment
As Point #14 of the GDS Digital Service Standard, assisted digital support must be provided to pass a service assessment for most services, making this a major factor. There’s a risk that some teams may not even begin to think about assisted digital until around the Beta phase, but it’s an element that should be considered from the Discovery phase, being a key channel of how a key set of users are going to access your service.
In practice: Exercise #1
We’ve reached the first practical exercise of the session. “Get into small groups and think of a service idea”, instructs Ben, “Then sketch out the user journey of this service”.
In a small group with some fellow TeaCamp-ers from Hackney Council and Barnet Council, we’re armed with pile of post-its, a Sharpie and the idea of a venue booking service for a town hall. From initially hearing about the service offline through to booking the venue, we begin breaking down this user journey, with each step on a post-it.
Designing good assisted digital
Designing for good assisted digital is ensuring that your team is doing the right research and putting this in place — researching with the right people in the right way.
For example, include people with the lowest level of digital skills in your pool of users. These are the people who may have the hardest to meet support needs, so it’s beneficial to engage with these people from the very beginning. Also, we need to make sure we’re recruiting these people in the right way. It’s highly unlikely that users with low levels of digital skills are going to be recruitable through digital channels, so we need to go out and meet them in public areas to engage further — libraries, parks, shopping centres, relevant charities, social housing providers, etc.
We then need to build services for users’ end-to-end journeys, from their perspective. This means considering the offline elements of a service. The journey doesn’t always start online (i.e. taxing your vehicle), so we need to take this into consideration. The aim is to ensure that every person can successfully get from ‘A’ to ‘B’.
In practice: Exercise #2
It’s now time to get back into our groups for the next exercise — building an inclusive service.
Ben shares the persona of Cathy — our user. “Cathy doesn’t have a smartphone, but she does have a very old PC. She’s not motivated to buy the latest technology, but she’s very literate having used to work in a role that required email. She’s terrified of using government services though, due to being penalized in the past.”
Our task is to take our services from exercise #1 and “stress test” these with Cathy. “Her level of digital skill is ‘unwilling’, so keep this in consideration”.
6pm has quickly arrived and it’s time to wrap up the session. Ben concludes by sharing a powerful statement: “There’s no such thing as an ‘assisted digital user’ – we’re ALL assisted digital users.”.
Really useful, practical advice from @benaldo on #AssistedDigital at today’s #LGDSS teacamp for London gov peeps @LocalGovDigital @gdsteam @Agilesphere @PA_Consulting @LoGovPlatform @LDN_CDO pic.twitter.com/rRIPp2ePxa— Natalie Taylor (@NatalieRobson) November 30, 2017
The next TeaCamp is taking place on Thursday 18th January, 4-6pm at Draft House Tower Bridge.
If you’re interesting in attending, please just send an email to David Durant at GLA (email@example.com) or come and join the #london-peer-group channel in the LocalGov Digital Slack.