We identified and carried out user research with two type of users: callers and NCC agents.
The team spent two sessions speaking directly to NCC callers who wished to take part in our survey. In total we spoke to 15 callers, the majority of whom were made up of older, retired people and this provided specific insights into this segment. However, given the self-selecting nature of the survey, additional insights were gained by speaking with the team leader in Income Services to gain some insight into other segments that were missing as they declined to take part in our telephone survey.
We wanted to understand the caller’s journey when interacting with the NCC, the ways they considered contacting the Council and if they used the internet. We asked five short questions:
This information was used in numerous ways including in the creation of our personas. Thse were made up of a combination of research surveys that we carried out with callers to the NCC; hypothetical traits that we gleaned from speaking with agents and the Income Services team; and observations we made whilst shadowing calls at the NCC and Corporate Contact Centre.
“I was calling to make sure that people had seen my email, that’s why I called. I often don’t get a response from email or online forms.”
‘I called in straight away as I received a letter this morning.”
“I’ve used the rent account on the Hackney web site but I find it confusing so had to call in to ask about my transactions and what is owing.”
“I used the Hackney.gov.uk to look up events.”
“I used the Hackney website to buy visitor parking vouchers.”
The whole team of user researchers, designers, delivery managers and developers took part in shadowing sessions with the Neighbourhood Contact Centre (NCC) agents to experience first hand the way that they work and the frustrations that they experience. This exercise was invaluable in demonstrating how agents carry out their jobs, the software they use and the workarounds they have devised. There were also opportunities between calls to quiz why they do things the way they do. We shadowed five different agents and listened to 36 phone calls.
We found that agents each receive their own personalised version of an Excel spreadsheet. On this spreadsheet, the agents enter details of each call they answer: eg reason for the call, identity of the caller, actions the agent took are recorded as manual comments. However, data can be patchy. Also, agents experience a number of frustrations during the process: for example, having to switch into Universal Housing to take a rent payment. The Team Leader aggregates data from these spreadsheets manually each week or month to generate various reports. This is a time-consuming exercise that's susceptible to human error and limits further interrogation. Also, without spending even more time creating visuals, it can be difficult to interpret the data.
We also obtained key data from six interviews with NCC agents during Discovery. These insights were gathered from 20 minute interview sessions. The 15 questions that we asked in our sessions were developed as a result of our shadowing exercise and were designed to help us probe and understand how the agents worked, which computer systems they used, what the agents perceived as the most frequent calls, what they described as a perfect call and the frustrations they experienced.
The 15 questions asked were:
“It takes so much time to print rent statements from UHW and UHT, which is very lengthy for such a straightforward thing”
“It is time-consuming copying and pasting information from one system to another and populating multiple systems with the same information.”
“It is a struggle to get hold of Estate Officers on the phone”
“PARIS has such a short session time and then when it times out you don’t actually know until you start taking a payment.”
“I really like the spreadsheet that comes up with the estate officer name and telephone number when you enter the postcode.”
“The Patch list spreadsheet is useful when I need to look up a contact number”.
In addition to shadowing the NCC, the project team also shadowed three Corporate Contact Centre agents to experience how they work, with a keen interest in their use of a CRM solution embedded in their service. We found that CCC agents do not record all of their calls in the CRM by any means. This particularly applies where a call is resolved through other software: for example, parking fines are taken in Liberator and agents do not spend additional time identifying the caller in the CRM and writing notes that they have taken a parking fine. And probably rightly so. We wanted to avoid this for the NCC and were keen to produce a piece of software that more fully met its needs.
At the start of Discovery, we were looking at the broader area of contact with the NCC. For this reason, we also interviewed the administrator responsible for handling emails to the service. This is certainly an area that could be improved and made less time-consuming in the future but, for the purpose of this project, was ruled out of scope.
The key things that we learned from the research was: