Summary
For data to be designed for everyone, we need people who use that data to be part of the design process. This user-centred design (UCD) project analysed our current communication methods and looked where we could improve.
Setting the scene
When designing planning applications submissions data, events were hosted by the Designing Data team to bring users (of the data) into the process.
Using well-known contacts, groups were formed. Our first advisory group had around 20 experts, and our community event attracted around 40 attendees.
Looking to the future, we wanted to make sure users found our events organically. This would mean any other users with knowledge of the data could get involved independently – resulting in a more diverse audience.
During events, the team utilised the “tell a friend” method. Events were also posted on GitHub discussions.
Design issues
To access a GitHub discussion, users would need to follow a numbered link to a GitHub channel. If a user did get there, we assumed that a large group would be put off by being on an unfamiliar platform.
A get involved page was very difficult to find and was hidden in a link on an about page.
There was no google analytics, so we couldn’t quantify whether users could find information.
We didn’t post any information about our events on the website!
What we did (user research)
We spoke to a range of users from our contacts, we knew they wouldn’t represent a sample of all our potential users – but it was a good place to start.
A/B tested current designs against a new prototype with improved UI like an event calendar and an external facing considerations page.
Research findings
When viewing new designs, users were shocked that we had events and wanted to get involved. But they were unsure whether they were the right kind of audience (even though we had pre-existing contact with them!)
There were lots of needs and questions discovered, such as
Proptech 1: “How do I get you to consider [a dataset]? How do we contribute to the backlog and prioritisation?”
Proptech 2: “I don’t know how I would interact through the website.”
Statcon 1: “We mainly discuss with [Designing Data team member] to raise key issues or points.”
Statcon 2: “I find it really difficult to find digital contacts in MHCLG, we would love to engage more with MHCLG.”
Usability - “I’m not going to read all that”. Users gave up when reading the live ‘how to contribute page’
Statcon 3: “There would be value in exploring alternative ways to get in touch, outside of GitHub. Working in the open is important, but some people may not want their thoughts out in the open or may have sensitive topics to discuss.”
What we changed
Changes went through multiple stages as there were many usability issues discovered through testing
Phase 1 – after identifying how people wanted to get involved, we put that on one new condensed ‘Get involved’ page. This includes links to prioritising a dataset, developing your own, and contributing to discussions. We also redesigned the consideration page so it was an external tool rather than internal. This meant changing vocabulary and being clear if we did or didn’t have data.
Phase 2 - an event calendar was built on a CMS. This means any member of our team can add events and they would be displayed on the relevant project, consideration and ‘Get involved’ page. No longer just held in GitHub.
What’s next
Metrics! We want to see how engagement improves from our changes using google analytics and event attendee information
Phase 3 (next) – reviewing content on GitHub. What information is hidden for some users by accessing the platform? Making this information accessible for all users will be the next step in truly bringing this work into the open.
Take a look for yourself
See if you can get involved with the data design process on our website.
If you have any feedback let us know!