Collecting feedback and improving user experience

We described back in June how we were testing and using feedback to inform the content on the site in its beta stage.

This has continued post launch. We’ve been gathering comments from customer service staff, services and website users. Nottinghamshire.gov.uk features a short survey (only four questions) asking users what they came to the site to do and whether they found what they’re looking for.

Despite our careful proofing before publishing pages, this feedback has highlighted some ‘quick fixes’ such as spelling errors and broken links, as well as more substantial suggestions on the site design and navigation. We’re logging all comments on Trello, assigning them to team members to action and archiving them when complete.

We’ve also been using HotJar – a (paid-for) tool that measures user behaviour – to monitor how the pages are being used. From the heat maps it provides, we can see the most popular areas of a page and how users are scrolling and clicking through the site.

Hotjar screenshot

One example of how I’ve used this information is on the Rufford Abbey and Sherwood Forest Country Parks pages, where I could see that viewing the car parking charges was a hot area of activity. Although they were in a prominent position on the page, the information was only available as a PDF download. When I needed to create a new page for the parks’ festive opening hours, this gave me an opportunity to improve this content and create calendar views for car parking charges.

I’ve also been using the HotJar recordings to see how users are using our what’s on/events listings. Being able to see how users on different devices and browsers are navigating this section of the site has allowed our team to make improvements, such as reducing the default number of events shown when browsing on mobile to reduce the scrolling length.

These HotJar tools do have limitations; you can’t interact with the user or ask any follow up questions as you can when user testing in person. However, there’s also less chance that you will influence their behaviour. For our team, it has been an effective method to gather a significant amount of data about users’ actions and opinions of the website, which we are using to improve the overall user experience.

Posted by Lucy Pickering, Digital Content Officer

A problem with behaviour OR Usability informing your content

Post-It notes on piece of paperWe blogged back in April about our work in usability testing which helped to shape the design of our beta site that you can see here: beta.nottinghamshire.gov.uk.

Our testing hasn’t stopped. We’re collecting user feedback which we’re implementing into future iterations of the site. The site is being developed for the people of Nottinghamshire and this blog post shows how their views are shaping the site in terms of usability and testing. Sometimes we think we know the correct label due to gut feeling. However, as we found out recently, you can’t beat a bit of good old fashioned consensus and testing.

As a Senior Digital Officer at the Council (and having worked across many different websites) I tend to think that I know what people want or expect to find behind a link, a button or a title on a page.

We were working on the Adoption content and were looking at what you might title the page on the process of adoption. ‘Adoption Process was my first instinct. Next I asked my peers what they thought it should be – and from there we formed a clear opinion of what it should be titled. This, however, is not the ending.

We have a clear process for these things within the Digital First team and that is why we always test assumptions. Sometimes assumptions on how people will navigate a site can be right, but it is often valuable to remove yourself from the process and find out what real users think. The website is after all being built for the people of Nottingham and not just the Council.

We decided to test out our assumption about the page title through a simple process, but one that was invaluable and has informed some of our user testing and decision making on additional elements of the website content.

We simply wrote down three choices on a post it note and sat in an area of the Council with high footfall. Post it notes in hand, I asked people under which heading they would expect to find out about the process of adopting. The three choices were:

  • Steps to adoption
  • How to adopt
  • I want to adopt.

Sitting there, I thought I knew that everyone would choose the right one in ‘How to adopt’ which of course is the best heading for this type of content. Wrong!

Out of all the people surveyed, they picked the heading that I thought no-one would choose which was ‘I want to adopt’. Not only this, but they also gave informed reasons without prompting as to why they would choose this heading to find the information provided. The distilling of this feedback was down to people having considered all of the information prior to adoption and now they want to physically go through the process of adoption and would expect to find the information on what to do next within this area.

Additionally, and most interestingly, one of the people I surveyed had previous experience of our adoption process having already adopted a child in Nottinghamshire (I didn’t know this until after I had surveyed them) and they chose the header of ‘I want to adopt’ also.

It just goes to show that you can sometimes rely too heavily on your opinion and experience, but it’s the people who use these tools that can surprise you with the answers they give and how they use the tools you’ve provided them.

Posted by Paul Roper, Senior Digital Officer

Moving to beta

Screenshot of beta website homepageOur work to move to a new nottinghamshire.gov.uk is at an exciting stage – we’re going into public beta.

We’ve been working on understanding user and organisational needs, and whether the content we have on the current site meets these. And we’ve been prototyping and testing (interaction and visual) design. Behind all this we’ve been learning to live our Digital First principles and ethos and preparing the technology we need to move the site forward.

Moving to public beta means we’re now ready to share this work – still at an early stage – more widely so we can begin to gather feedback and iterate as we continue with the build over the next few months.

What do we mean by beta?

We’ve defined what we mean when we say beta along the lines of the Government Digital Service definition. We’re using it to mean: “a web page, service or site is still in a testing phase and is a developing prototype going through testing and rapid iterations.”

The beta we’re putting public now is still very much a prototype and we’ll be aiming to, in the words of the Government Digital Service,  “build a fully working prototype which you test with users. (…) continuously improve on the prototype until it’s ready to go live, replacing or integrating with any existing services.” In our case this means preparing content and improved (appropriate) transactional capability across the Council’s 500 services.

Our beta is very small right now – the start of a structure, a few areas of content, little integration with other systems – but we’ll be building on this over the next couple of months. It will run in parallel with our current website (this remains the official digital channel of the Council for now) as we transition services over during the summer ahead of a full go live with the new site in September.

Why make it public?

Both our digital design philosophy and principles describe how we want to work openly and with our customers.

Putting the beta live now may well show up things that don’t work or could work better – and that’s great! We’d rather know about that stuff and work on it more before the beta transitions to be the official website of the Council.

How long did it take?

We moved into private alpha at the start of the year after implementing Umbraco and completing initial work on our content inventory.

Much of the work on beta has happened in a couple of sprints over the last month. The first covered the usability testing on the three design concepts and analysing the results while the second covered a fast build based on what we learnt.

Last week we went into private beta, sharing the site with stakeholders and Council staff.

The site will remain in public beta until September when it becomes the official Council website.

What’s different from the current site?

Lots!

The beta site is responsive and optimised for use on different devices. We’ve thought not only about how the site displays and the priority of content on devices but also about user behaviour on these devices (touch navigation, for example) and the context of visits.

Our design prototype testing explored what sort of information architecture works best for our customers and we’re building a mixed navigation of both container and tagged content (hat tip to GOV.UK here for inspiration on designing this interaction).

We’ve kept the ‘top tasks’ style prioritisation on the homepage but in order to move people more quickly to the right content and this will work dynamically in time to reflect activity on the site at a given time. But recognising that most of our visitors come straight to a deeper content page from an external search engine we’ve designed a path through the hierarchy that makes the least stops on the way to where people need to be, while still signposting clearly. You can check this out through the ‘browse this website’ tab on the tasks box on the beta homepage.

We’ve prioritised the customer need on each of the page by getting site furniture out of the way as much as possible and making content as focused as possible by telling people what they want to know as clearly and concisely as we can (still lots of work to do on content though!).

But we’ve also recognised there is organisation needs to be met, and that the Council isn’t only a service provider but a part of the local community. This means we’re trying out a chunky footer on each page that brings in news, events and social content. Common ‘homepage’ features that people don’t see when they land deeper in the site by using ‘Google as the homepage’. We need to explore this idea further to see if the chunky footer works for user and organisation but we’d like this to be contextual in the future – so the news, events, social and democratic content you see is directly related to the service content above.

These are just a few of the changes we’ve made so far but there’s lots more to come. We’re all really excited to learn more about how people use the site and what works (and what doesn’t)!

What happens next?

We’re encouraging people to try out the beta and provide feedback. To help with this we’re using Google Analytics but also Hotjar – capturing mouse patters and generating heatmaps as well as gathering qualitative data through a short survey. The survey appears shortly after you land on our site or you can find it here.

We’ll be taking what we learn from this and over the next few months we’ll be transitioning from the current site to the beta being the official channel so we’ll be signposting from one to the other in preparation for that. We’ll also be continuing to work with customers, services and our other access channels as part of this work.

There is a lot more work to do to add in functionality that will allow the site to work in the ways our customers expect, integrate with our transactional services and get the content to the standard we’re looking for.

We don’t expect the new nottinghamshire.gov.uk will look exactly like our beta does currently when it goes live in September – visual design, interaction design and content will all change over the summer with more work by the team based on evidence of usage patterns and usability testing.

For now – we’re just asking you to give it a go and we looking forward to hearing what you think!

Some things to try on the beta:

~

Sign up for the latest updates on our Digital First progress through emailme.

Posted by Sarah Lay, Senior Digital Officer (Digital Team Leader)

First steps in design

We blogged recently about the usability testing we’d undertaken on three design concepts with The Insight Lab detailing the methodology and headline results. Here’s some more detail about the three prototypes we put to the test.

~

An integral part of Digital first involves developing a new nottinghamshire.gov.uk. With this new version of our website we want to design something that looks good, works well across a range of devices and most importantly, is incredibly simple to use.

A local authority website is a container for a vast amount of information about diverse services which often have little relation to each other aside from the organisation delivering them. With more content and transactions moving to digital services, we set out to design an experience that lets the user concentrate on the task at hand, and giving them access to other content when relevant while getting everything else out of their way.

A website with so many pages needs many interface elements in order to help the user navigate round it all. Things like a main menu, a breadcrumb trail, a list of pages related to the content you’re looking at, a list of pages that are commonly accessed across the site, and many more!

We wanted to ensure our new website had everything the user needed, but remained simple and didn’t become overly complex, so we set about discovering which of these interface elements and design features our users found more useful and which ones were cluttering their experience.

Designing three concepts

We decided to develop three initial concept designs, all which could be used for the new nottinghamshire.gov.uk, but all were different in particular ways.

Each design had similar interface elements, but they would be shown in different places or interacted with in different ways. This was so that we could begin to understand what was so simple to a user it could be used without them having to think about it, what was too complex, or in the worst case scenario, prevented the user from completing their task.

We also wanted to design a site that was engaging, pleasing on the eye and conveyed not just our Digital Design Philosophy, but the character and feel of Nottinghamshire as a county.

We could then test how people interacted with each site, and discover how they used (or didn’t use) certain interface elements to navigate the site and complete the task they had come to do.

Design One – The “Contemporary” design

Screenshot of design concept homepage

This design was influenced by current local authority websites, and built to emulate the type of interface people would expect to see when arriving on a council website.

This included interface elements such as top tasks, search box, a top level navigation menu and positioning content in a traditional, vertically stacked page.

We included additional information about events and news in a big, clear way in an attempt to showcase content the user may not have intended to view when they first arrived, but may find useful (but still doing this without getting in their way!).

We positioned these elements in the lower half of the screen, “below the fold”, so that they could access it if they came across it, but so that it didn’t interfere with the task they had come to complete.

This concept was designed to look colourful, big and bold, with clear, large typography used to group related links.

We saw this design as an evolution of our existing site in terms of look, feel and user experience.

Design Two – The “Modern” design

Design concept screenshotThis design took on a slightly more modern interface and used horizontal columns to showcase different types of content simultaneously.

This design was built to fill the screen of the visitor’s browser, abandoning the traditional fixed width centre column design, allowing visitors on high resolution/large devices to have a more optimal experience.

As the screen width decreases, the columns can slide and expand horizontally, similar to how modern smartphone applications (for example Twitter) work, reducing the need for users to scroll down the page to consume content.

The two right hand columns serve secondary and tertiary content across all pages, so no matter where the visitor arrives on the website, they will always have access to over-arching elements.

This was an interesting point with this design – keeping a similarity between content pages and the homepage. We often found council websites had a homepage with lots of engaging and useful content, but that moving onto a specific page would remove those broader elements (such as news and events). And with more and more of our visitors arriving directly on content pages from Google, we wanted to explore the opportunity of showcasing this content from all pages, regardless of where they started their journey.

This design also explored moving the footer to the right hand side of the screen, again, using sliding panels to expose the content. We initially set this element to be a thin border, which would expand when interacted with by the user.

We also used icons to symbolise links to our social media channels, as well as contact details and address information.  We wanted to test whether icons alone would be enough of a prompt for users to find information, for example, an envelope to signify contact us, or the letter I to signify information.

Interestingly, icons that represented brands that visitors were very familiar with, for example Facebook, worked on their own but icons we had used exclusively, such as the envelope did not successfully prompt the user to interact with that element when looking to contact us.

Design Three – The “Clean” design

Design concept homepage screenshotThis design was the most simplistic of them all. We wanted to explore just how simple we could make our website before it started to have a negative impact on the visitor.

In this design, we removed all additional content from the interface, such as news and events and focused purely on the task the user had come to complete.

The homepage lists popular tasks and online services, alongside a navigational structure that lets the visitor browse the site from left to right (again using horizontal columns) in a directory structure similar to GOV.UK.

Content pages were also very simple, and only showed visitor content relevant to that section rather than content from a broader section of our website.

This particular design didn’t allow for much opportunity to engage with the user, in terms of broader Council content and while we recognised that this was not ideal from a business perspective, it would be useful to see if this approach significantly improved the user experience for the visitor.

What we found

The findings from the user testing of these design concepts were very interesting, and confirmed some of our assumptions while completely disproving others.

The testing experience provided us with a wealth of data, helping us identify the key interface elements that we would put into the beta design and also helping us get a feel for what level of complexity users were most comfortable with.

The general findings showed us that users found design two to be too complex. While they did find it useful having access to broader content across all pages, they did get lost on the page, spending a longer amount of time looking around the page to find the next step in their journey.

Designs one and three were scored fairly similar, although the simplistic nature of the design three did require visitors to return to the homepage to start a new task, as there was no links between different types of content.

Subjective questioning also found design three to be too simple, and that people preferred the look and feel of the first design, perhaps because this had a more familiar feel to it compared to the current website.

We also found that when performing a specific task, providing relevant links to other content significantly helped users browse the site and complete further tasks, for example having a link to ‘events in half term’ on the school term time page.

Certain interface elements, such as popular links and related pages were used very frequently, whereas elements such as the search box and main menu were, surprisingly, used much less frequently.

What’s next?

The next step was to take what we had learnt from both the practical experience of designing these concepts and the user testing results to design the first version of our beta site.

This design is almost an amalgamation of the three design concepts, borrowing the strongest elements (and most successful as determined in the user testing) from each design, and rebuilding them into one design that will go live in our public beta test very soon.

Once this is live, we will continue to monitor user behaviour and iterate the design to continuously improve it, so that we can move closer to the version we replace our current website with later in the year.

The design process is allowing us to discover what really works, very quickly. With constant feedback and iterations, we are able to test ideas and challenge our own assumptions very quickly, helping us get closer to a site the residents of Nottinghamshire find highly usable and (perhaps!) enjoyable too.

Posted by Carl Bembridge, Digital Design Officer

Testing our design concepts

Web cam on screenWe’ve just completed the next step in our journey toward the new nottinghamshire.gov.uk website – usability testing of our initial three design concepts.

The three design prototypes challenged our assumptions about user behaviour and sought to discover which elements really help them complete visits to our site efficiently and satisfactorily.

Dr. Emily Webber and Dr. Vicky Shipp of The Insight Lab provide this detailed post on how we approached this phase of the build and testing.

~

Why do user testing?

When designing a website it is important to consider the different types of people who will be visiting it, and the type of experience they will have. A really effective way to do this is through user testing, where we can observe people carrying out set tasks on a website or prototype to understand what they do, and what they think. This will help to assess their reactions to the website and anything that they find particularly difficult to use, which will in turn help us to see how it could be improved.

User testing can be carried out on just one design, but the benefit of comparing different designs is that people will be able to notice which features they like or find easiest to use across a range of options, and we can observe which elements work well and those that don’t. This will help to identify the strengths and weaknesses of the different designs so that we can make a more informed decision about future designs.

To help with the development of the new Nottinghamshire County Council (NCC) website, The Insight Lab were asked to run user testing to evaluate three prototype interface designs.

These three in-browser prototypes were created especially for the testing, and included a range of different aesthetic and functional elements to allow for a rich experience, which aimed to mirror the use of a fully functional site. Subtle differences across the designs, such as the location and function of menus, the placement of key pieces of content, and the colours used, would allow us to see how this impacted on people’s performance and experiences and understand which elements allowed for more efficient and effective task completion.

Who did the testing and what did it involve?

Lab-based usability testingUsing the previously identified personas as a starting point, we recruited participants across a range of age groups, locations, and with different levels of computing experience. This ensured that the sample of people who took part in the study, and their feedback and performance, were representative of the actual users of the NCC website.

The individual testing sessions lasted just under an hour and participants were asked to use all three of the interfaces to complete a series of common tasks, such as finding out about school term dates, viewing local events, and reporting a pot hole. We made sure that the order in which people completed the tasks and used each interface were randomised so that the results wouldn’t be affected by people becoming familiar with them (we call these practice effects). In this way we could be sure that the results we got were as non-biased and as accurate as possible.

To allow us to understand exactly what people did, we used software to record what was happening on the screen – where people were clicking, hovering, and the route they took to complete each task. This software also captured a video of people’s reactions to the tasks via a webcam mounted on the monitor so that we could record when people were particularly confused or confident, and map these reactions to use of particular interface elements. We also recorded a variety of metrics such as how long it took people to complete the tasks, how many times they needed to click, and which navigation elements they used.

At the end of the testing sessions we asked participants to talk about their experiences, identify their preferred elements across the three designs, and fill in a quick survey that measured how usable they found each interface. By capturing this wide variety of data it would ensure rich and insightful results.

Making sense of the data

The sessions generated a lot of data, and we needed to spend time analysing it to make sense of it. This is one of the most enjoyable parts of our job as we begin to explore and uncover meaningful insights.

In this scenario we looked at the average task completion times across the interfaces, the usability score of each interface, and the different ways that people completed the tasks.

This not only allowed us to see which design performed the best overall, but also the different design components that people used and/or struggled with and any tasks that were more challenging than they should be.

What did we find out?

Usability testingThrough our analysis we found that although all three interfaces designs were rated as having above average usability, opinions about the preferred interface were varied. We were able to identify the elements that were frequently used and allowed for efficient task completion, or those that were particularly well received, and these should remain in the future design.

However, it does not mean that other interface elements should not be included, as these were still important to some of the users. What is key is combining these in ways that do not inhibit or distract other site visitors.

Our findings have produced a set of recommendations that NCC can use to ensure that future designs meet the various needs of people using the website. As the aim of the testing was not to choose one interface, but to understand the way people used different features of the designs, future designs are likely to involve incorporating aesthetic and navigational elements from each of the three prototypes.

The Insight Lab is an expert-led consultancy, implementing user-focused research methods to drive the design of digital products and services that are simple, efficient and a pleasure to use. Find out more about them on their website.

Personas – representing our customers

Sample persona - Beryl CumberlandWe’ve added a new tool to our user-centered design toolkit in the last couple of weeks: personas.

Personas offer a way to realistically represent our key customer groups online and can be used to help make informed decisions on design.

They’re a good way of keeping the customer and their needs in mind as we build our digital services, although they don’t replace contact with real people to research and test what we build.

We developed our set as part of the work we did with The Insight Lab (read their post for us on open card-sorting here) and represent the major primary, secondary and tertiary groups across nottinghamshire.gov.uk as a whole.

In order to develop them we used data about current usage, contact through other channels and experience from service areas. Through a workshop we got relevant colleagues together and created a huge set of potential personas before distilling these down to a smaller set by combining characteristics and looking for shared needs or themes.

There’s some great background reading about personas and how to create them on Usability.gov.

While a small set for the site overall is useful we may develop additional personas as we build our digital services.

You can see and download an example from our persona set here (PDF).

Posted by Sarah Lay, Senior Digital Officer

It all starts with discovery – getting going on our intranet work

We’re now in the discovery phase for our intranet and employee engagement workstream. We’ve already completed content inventory work on our current intranet (read more about the inventory we did on our public website here) and to help us with other parts of the discovery phase we’re working with an external expert, Ann Kempster.

Ann has previously worked at the Cabinet Office and other parts of central government as well as on a number of digital projects elsewhere.

Here Ann describes how she’s approaching the discovery work and the activities we’re undertaking.

~

One of the work streams for Digital First includes a review of internal digital communications channels, including the intranet. That’s what I’m working on over the next few weeks.

Previously I’ve managed intranets at the Cabinet Office and I’ve also worked on delivering intranets in number of other central government departments, including the Department of Health, Defra and Communities and Local Government.

I’m really excited to be working on this project with a council that is bought into the process of digital transformation. Nottinghamshire County Council is at a very interesting point in its journey with a new Chief Executive shortly to come into post and the support for the Digital First project at all levels, from the elected council members to staff at the council.

What I’m trying to find out

Is the intranet working for users?
Does it help staff do their jobs?

Is there space for engagement between senior leadership and frontline staff?
Is there space for staff to talk to each other?

Are staff getting the right information?
Are they getting information in a format that helps them?

What about frontline staff who don’t have regular access to the intranet? How does Nottinghamshire County Council make sure they are included and receive the right information?

How am I doing this?

I’m spending a lot of my time talking to as many members of staff as I can – both through one-to-one interviews and group workshops. I’m looking for what is working well, what isn’t working so well; what tools and processes people need to do their jobs. I’m also looking for any potential blockers, things that might stop a new intranet being used.

A few themes are already starting to emerge in my early round of interviews with key internal stakeholders and I’m keen to see if these themes are backed up in the workshops being run this week.

In the workshops with frontline staff and managers, we’ll be doing some activities and exercises to look at positives and negatives of the current system and what might help them do their jobs better or easier in the future.

I’ve also been talking to other people in the public sector who are doing good work on intranets, as well as experts in the private sector to see what trends are predicted for intranets.

Then what?

All of this information – nearly 20 one-to-one interviews and workshop outputs from almost 40 frontline staff – will be analysed with the help of hundreds of Post-It notes to see where clusters and themes emerge.

These will then be synthesised into a report that will be delivered to the Council for consideration, along with findings from my chats with intranet experts. I’ll be proposing a set of recommendations and a series of objectives, time scales and metrics for success.

I will also share some of the finds, key themes and ideas in another blog post here.

~

Ann is a freelance digital projects manager and you can find her on Twitter.

If you’re interested in getting involved in testing or giving feedback on the new Nottinghamshire.gov.uk, the Council’s public website, then get in touch.