While we pride ourselves on building digital solutions that make it easier for citizens to interact with local authorities, we also want our products to be just as easy to use for the staff members at those authorities. In this blog post, Bekki Leaver, our Head of Product, talks about how we’re currently working on enhancing the admin user experience of SocietyWorks’ digital solutions.
An often neglected facet of designing digital services and the tools that enable them is the experience of the staff user. In SocietyWorks’ case, staff users of our products would be the council staff and sometimes external contractors who use both the administration interface and the front end of our solutions.
Giving equal priority to the admin user experience alongside that of the end user is something I’ve got a keen interest in, because during the course of my professional career I have seen the remarkable benefits to organisations that well thought out staff interfaces and tools can have.
When you’re on the phone to a contact centre and they’re apologising for their slow or unresponsive system, that’s poor customer and staff user experience. When an employee is having to copy and paste fields from a spreadsheet into another tool, that’s poor staff user experience. When you have to know the foibles of a piece of software on top of your area of expertise, that’s poor staff user experience.
For many years the expectations staff have of the tools and software they are required to use in their roles have been low. Using archaic HR platforms to request leave was just something you put up with, but as the workforce changes, and staff become more digitally literate, doing complex, previously unachievable things online every day, their expectations are higher and their tolerance for bad experiences is lower.
The value of good staff user experience parallels that of good customer experience; lower barriers to entry, higher satisfaction, improved relationship. There are also the benefits of better efficiency where intuitive, easy to use interfaces speed up interactions while also involving less training.
Improving the user experience for a product is never a finished task, with expectations changing all the time. Here at SocietyWorks, there’s a lot we would like to do to enhance the staff user experience of our products, which have advanced at a fast rate over the last few years.
Take FixMyStreet Pro for example, which now provides staff users with greater access to more controls and options through its administration interface.
As we continue to grow and expand the administration features and functionality of our products, we are keen to make sure that any improvements we make for the benefit of staff users are guided by those users themselves.
We’ve reached out to a group of authorities that use our solutions to participate in some research involving the staff users of the tool(s), exploring their roles, how our technology fits into their responsibilities and how they use the solution(s) on a day-to-day basis. I’ll be talking to them about their daily tasks, what other tools they might use and where things could be made better for them.
The results of that research will then inform our decisions on improving our products, not just in the case of what it can do, but where information and controls are and how staff users can interact with them. We’ll then set about designing new features, experiences and interactions, with regular testing and feedback opportunities before a phased implementation.
I’m expecting some pretty significant design changes, so watch this space!
Image: Will H McMahan on Unsplash
Our new report Citizen reporting in the UK 2022, which explores whether and how citizens make reports about problems in their local area, has been published.
Based on a nationwide YouGov survey commissioned by SocietyWorks, the report aims to help councils and other public sector organisations that need to take reports from citizens about a variety of issues to stay informed of ever-changing expectations.
Among some of our key findings, we discovered that the majority of citizens surveyed said they haven’t reported a problem in the last few years due to experiencing previous disappointment caused by unresolved reports.
We also learned that only 22% of respondents wanted a dedicated mobile app for making reports, while 43% would prefer a website that works well on mobile devices.
Alex Parsons, senior researcher at our parent charity mySociety, with whom we collaborated on this research, said: ‘Citizen reports of problems both help citizens feel guardianship over their area, and alert authorities to problems. Managing the feedback loop and the expectations of citizens is important because problems being reported and not fixed makes citizens less likely to report again.
‘The philosophy of our services is that citizens should not need to understand how overlapping systems of government work to report problems, and this is validated by strong support for a tool that can route the request to the right place.
‘Making it easy to report problems and keep citizens informed about progress improves the relationship between local councils and citizens and means citizens don’t need to follow-up through other methods.’
Councils that are keen to transform their service delivery for citizens can carry some key priorities forward from this research to help them harness the full potential of proactive citizen-made reports, without increasing the burden on customer services teams.
At LocalGovCamp, our designer Martin ran an interactive exercise that took attendees through a ‘consequence scanning’ exercise, as a way to predict and mitigate all the outcomes, both positive and negative, of a proposed piece of development.
In this case, the service under discussion was a fictional parking violation reporting app.
Let’s just repeat that, in case of any angry reactions: fictional!
So, what could possibly go wrong with a piece of tech designed to encourage residents to grass on fellow citizens for their poor parking? You can see how it played out in this video:
Now you’ve seen a consequence scanning exercise in action. If you’d like to understand more about the process, read on: this is how Martin explained the whole idea to us here at mySociety, with more detail on the underlying principles:
We’ve been working on a few sensitive projects recently – specifically our work expanding FixMyStreet Pro to cover issues of a more social nature, like noise reporting, antisocial behaviour, that sort of thing.
As experienced as we are with the ‘make a report by sticking a pin in a map’ style of interaction design, we recognise the need for extra care when applying this to issues that are about people, rather than things. There’s an increased risk of building a tool that results in unintended negative consequences; especially where the service concerns an area already prone to controversy.
mySociety Board member Jonathan Flowers put us in touch with Connected Places Catapult, who had been using ‘Consequence Scanning’ for this very thing, and we realised it was just what we needed.
It’s a structured system for drawing out the consequences of a new idea, and giving people a say in what actions are used to mitigate or address them. It originated from the Doteveryone thinktank, and CPC have taken it forward and customised it for their needs.
In Consequence Scanning, consequences are classified as either intended or unintended, with the important distinction that intended consequences aren’t always positive, and unintended consequences aren’t always negative.
The process is delivered in a workshop format and works best with a good mixture of participants with diverse views and backgrounds, directly involved in the service on both sides. This means ideally both service users and service officers should take part and be prepared to be honest about consequences. For this reason it’s important to create a safe space where information can be shared honestly and openly.
The process is split into three parts:
Part one: What are the consequences?
Part two: What are the positive consequences we want to focus on?
Part three: What are the unindented consequences we should mitigate?
This system works best on a new, but defined idea. If it’s done too early in the design process, the consequences end up being very general, or people bring their own assumptions and often focus on the wrong things. It’s best to bring it in once scope has been defined.
The primary function is to identify the consequences and not to “solutionise” the mitigations, but the group should be free to discuss possible mitigations where they feel it’s important.
We’ve been using Consequence Scanning in our work on noise reporting and antisocial behaviour, and it’s also proving useful for our internal anti-racism action group, where we want to understand the potential unintended results of any future development in terms of who our services reach, and who they exclude.
Image: Drew Graham
FixMyStreet allows people to upload images along with a report. This can quickly provide the authority with more details of the issue than might be passed along in the written description, and lead to quicker evaluation and prioritisation of the repair. For problems that are hard to locate geographically by description (or where the pin has been dropped inaccurately), images might also help council staff locate and deal with the problem correctly.
In 2019, 35% of reports included photos. Accounting for several other possible factors, reports with photos were around 15% more likely to be recorded as fixed than reports without a photo. In absolute terms, reports with photos were fixed at a rate two percentage points higher. This varies by category, with photos having a much stronger effect (highways enquiries and reports made in parks and open space) in some categories, and in other categories photos having a small negative effect in the resolution (reports of pavement issues and rights of way).
In general, these results suggest that attaching photos is not only useful for authorities, but can make it more likely that reporters have their problem resolved. There is a significant reservation that photos are much more useful for some kinds of reports than others. In terms of impacts on the service, when photos can convey useful information that helps lead to a resolution, users should be encouraged to attach them. Where photos are less helpful (such as problems encountered mostly at night), other prompt suggestions or asset selection tools may help lead to more repairs.