Our services are diverse and so are our users. When our users come into contact with the justice system, it can often be at highly stressful moments, such as:
- getting a divorce
- applying for probate after a death
- seeking an injunction for domestic abuse
- appealing an immigration decision
Each touchpoint in our users’ journeys can be life changing, which is why it’s so important for us to learn about our users and create services that meet their needs.
The better we understand our users, the more likely we are to design and build services that work well for them.
Improving our research skills and practice
As a user research team, the research we do is varied. While one of us is testing new designs for a service in its alpha stage, another is understanding the in-court experience. One of us might be working on a cross-cutting discovery to improve how we capture reasonable adjustments, another might be doing research to understand and improve a new digital service.
Our user-centred design community meets every month. We’ve found our community sessions over the past year have helped us identify common user needs across our services and helped us to share best practice.
We have a monthly user research community of practice hour, and dedicated personal development time, to make sure we’re constantly improving our skills and providing the best outcomes for our users.
Our first user research crit
We recently held our first user research ‘crit’, inspired by our content design colleagues. The aim was to share user research from different projects, reflect on our own practice and get feedback and advice, in a timebound and structured session:
- User researcher volunteers a piece of work to share
- Volunteer brings the work up on screen and presents the context
- Volunteer explains what sort of feedback they're looking for from the group
- Everyone listens and writes on sticky notes
- The critmaster initiates discussion
Here are our main takeaways from the session:
Context is everything
Each piece of work shared in the session was different. Understanding the context for the research and the problem the team was trying to solve is an important part of the puzzle.
Be format agnostic
Format agnostic means we share research in a variety of formats, and we found that this worked well. Sometimes we want feedback on recruitment briefs and research plans. Sometimes we want to discuss research outputs.
Our team plays back research findings in a range of ways, including:
- video clips
- short reports
- summary emails
- confluence pages (team workspaces)
Make collaborative recommendations
Our work helps teams to make the right design decisions to meet user needs. It was great to share some success stories and learn how user researchers are involving different teams to improve services.