The Ministry for Primary Industry’s (MPI) customers have some of the most varied information needs — possibly the most varied in New Zealand. MPI provides information on how to follow fishing rules, what the requirements are to sell dairy products at the market, and how to go about exporting honey to Asia. Their website mpi.govt.nz has all the information.
However the previous website was dense and complicated, and MPI’s customers were struggling to find the information they needed, often calling the contact center instead — one of several indicators that people were lost and confused on the website.
Ruth Hendry, Head of Strategic Growth at Springload, recently spoke at UX New Zealand, the leading UX and IA conference in New Zealand hosted by Optimal Workshop, about how new IA helped MPI’s broad range of customers find the information they needed.
In her talk, Ruth takes us through the tips and techniques used to create an IA that met a wide variety of user needs. She covers the challenges they faced, what went well, what didn’t go so well, and what her team would do differently next time.
Background on Ruth Hendry 💃🏻
Ruth was Springload’s Content Director; now she’s Head of Strategic Growth. She has broad experience in content, UX, and customer-led design. A data nerd at heart, she uses analytics, research and testing to drive decision-making, resulting in digital experiences that put the customer at the forefront.
At Springload Ruth has worked on large-scale content and information architecture projects for organisations including Massey University, Vodafone and Air New Zealand. She got into the world of websites in her native UK, working on Wildscreen's ARKive project. After she arrived in Aotearoa, she spent four years looking after Te Papa's digital content, including the live broadcast of the colossal squid dissection. She's Springload's resident cephalopod expert.
She finds joy in a beautiful information architecture, but her desk is as messy as her websites are tidy.
Contact Details:
Email address: ruthbhendry@gmail.com
LinkedIn URL: https://www.linkedin.com/in/ruth-hendry-658a0455/
Food recalls, fishing rules, and forestry: creating an IA strategy for diverse audience needs 🎣
Ruth begins her talk by defining IA. She says, “If IA is the way information is organized, structured, and labeled, then an IA strategy is the plan for how you achieve an effective, sustainable, people-focused IA.”
Considering this, applying an IA strategy to the Ministry of Primary Industries (MPI) website was a challenge due to its diverse user groups. MPI is responsible for a range of things, such as publishing food recalls, looking after New Zealand’s biosecurity, outlining how much fish can be caught, how to export products, and even how to move pets between countries. Needless to say, the scope of this IA project was huge.
The current state of the website was challenging to navigate. In fact, one customer said, “It’s hard to find what you need and hard to understand”. MPI Contact Center staff often found themselves simply guiding customers to the right information online over the phone.
So, in solving such a massive problem, does having an IA strategy work? Ruth says yes! And it can have a huge impact. She backs up her strategy with the results of this project before broadly outlining how she and her team achieved the following improvements.
The project achieved:
- 37% decrease in time spent on the home page and landing pages
- Customers found where they needed to go, faster, using the new IA and navigation elements
- 21% decrease in on-page searches
- People could find the content they need more easily
- 53% reduction in callers to MPI saying that they couldn’t find what they needed on the website
- Users could more easily get information online
Developing an IA strategy 🗺️
Ruth attempts to summarize 14 weeks' worth of work that she and her team delivered in this project.
Step one: Understanding the business
During this step, Ruth and her team looked at finding out exactly what MPI wanted to achieve, what its current state is, what its digital maturity is, what its current IA was like (and the governance of it), how the site got to be in the way that it was, and what their hopes and aspirations were for their digital channels. They conducted:
- Stakeholder interviews and focus groups
- Reviewing many, many documents
- Domain and analogous search
- Website review
Step two: Understand the customers
In this step, the team looked at what people want to achieve on the site, their mental models (how they group and label information), their main challenges, and whether or not they understood what MPI does. They conducted:
- A review on website analytics and user needs
- In-person interviews and prototype testing
- Card sorts
- Intercepts
- Users surveys
- Treejack testing
Step three: Create the strategy
This talk doesn’t cover strategy development in depth, but Ruth shares some of the most interesting things she learned (outlined below) throughout this project that she’ll take into other IA strategy projects.
Why it matters 🔥
Throughout the project, Ruth felt that there were eight fundamental things that she would advise other teams to do when creating an IA strategy for large organizations with massively diverse customer needs.
- Understand the business first: Their current IA is a window into their soul. It tells us what they value, what’s important to them, and also the stories that they want to tell their customers. By understanding the business, Ruth and her team were able to pinpoint what it was about the current IA that wasn’t working.
- Create a customer matrix: Find the sweet spot of efficient and in-depth research. When an organization has a vast array of users and audience needs, it can often seem overwhelming. A customer matrix really helps to nail down who needs what information.
- Card sort, then card sort again: They are the best way to understand how people’s mental model works. They are critical to understanding how information should be organized and labeled. They are particularly useful when dealing with large and diverse audiences! In the case of the MPI project, card sorts revealed a clear difference between business needs and personal needs, helping to inform the IA.
- Involve designers: The earlier the better! User Interface (UI) decisions hugely influence the successful implementation of new IA and the overall user journey. Cross-discipline collaboration is the key to success!
- Understand the tech: Your IA choice impacts design and tech decisions (and vice versa). IA and tech choices are becoming increasingly interrelated. Ruth stresses the importance of understanding the tech platforms involved before making IA recommendations and working with developers to ensure your recommendations are feasible.
- Stakeholders can be your biggest and best advocates: Build trust with stakeholders early. They really see IA as a reflection of their organization and they care a lot about how it is presented.
- IA change drives business change: You can change the story a business tells about itself. Projects like this, which are user-centric and champion audience thinking, can have a positive effect throughout the business, not just the customer. Sometimes internal business stakeholders' thinking needs to change before the final product can change.
- IA is more than a menu: And your IA strategy should reflect that. IA captures design choices, content strategy, how technical systems can display content, etc.
Your IA strategy needs to consider
- Content strategy: How is content produced, governed, and maintained sustainably going forward?
- Content design: How is content designed and does it support a customer-focused IA?
- UI and visual design: Does UI and visual design support a customer-focused IA?
- Technical and functional requirements: Are they technically feasible in the CMS? And what do we need to support the changes, now and into the future?
- Business process change: How will business processes adapt to maintain IA changes sustainably in the long term?
- Change management and comms plan: How can we support the dissemination of key changes throughout the business, to key stakeholders, and to customers?
Finally, Ruth reemphasizes that AI is more than just designing a new menu! There’s a lot more to consider when delivering a successful IA strategy that meets the needs of the customer - approach the project in a way that reflects this.
