Navigating the Complexities of Information Architecture vs Data Architecture

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. 

‍

1. 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.
2. 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.
3. 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.
4. 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!
5. 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.
6. 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.
7. 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.
8. 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.

‍

‍

When I first heard the word ‘taxonomy’, I had no idea what it meant. I remember enthusiastically nodding my head at my boss about how awesome it is while frantically Googling it under the table. We’ve all been there early on in our careers. Although, what I found left me feeling even more confused — something about classifying animals? Whether you’re as confused as I was all those years ago or just in need of a refresher, this quick guide to all things taxonomy will sort you out.

‍

What is a taxonomy in information architecture?

‍

In information architecture, taxonomy refers to how information is grouped, classified and labeled within a shared information environment. The overarching structure of that shared information environment is the information architecture (IA) and we find our way around it using the navigation. Think of an IA as a house. The taxonomy determines which pieces of furniture belong in each room and we navigate around the house via doorways and hallways. It all fits together to create one shared environment.

‍

For a website architecture example, think of an online shoe store. The shoes might be organized and labelled by color, size, style, season or collection — that’s the taxonomy. The overall picture of where those groups of shoes live is the IA and in our pursuit of new shoes, we might navigate that structure via a navigation bar at the top of the page. In the amazing Grand Taxonomy of Rap Names visualization below, we can see how the information is categorized, connected and labeled through the lines and the colors. There’s no structure or hierarchy to it yet; that would be the next step in the process to build the IA.

‍

‍

Creating a taxonomy

‍

There are so many different ways to carve information up into a taxonomy and the key drivers for determining that are your content and, of course, your users. Your taxonomy needs to make sense to your users.You may be starting from scratch with a new website or you may have inherited a taxonomy that for whatever reason just isn’t fit for purpose. The first step when creating an initial taxonomy is to do a comprehensive audit of your content. Ask yourself, is your content relevant? Is it up-to-date? Is it all necessary? Are there opportunities to delete or condense content? Once you have your content sorted, you’re ready to move on to the next step of running a card sort with users.Running a card sort early in your taxonomy creation process will allow you to build it up from an evidence based foundation. There’s no point guessing then testing and potentially going back to square one, when you can co-create with your users and then test that informed approach to validate and further evolve your thinking.When you’re designing your card sort, you’ll need to decide if you’re going to do an open, closed or hybrid sort. Here’s a very high level look at what each type involves:

‍

• Open: participants sort cards into groups and name their own categories
• Closed: participants sort cards into categories determined by you
• Hybrid: participants sort cards into categories determined by you AND they can also make up their own.

‍

This early in the taxonomy creation process, it’s best to start out with an open card sort. Not only will this tell you how your users expect your content to be grouped, but will also provide insight into the language and labels that they would expect that content to be associated with. You never know, an open card sort may even surface something you hadn’t considered. At this stage of the process, it’s important to be open to ideas and new possibilities and an open card sort will do just that.Once you’ve settled on the type of card sort you’ll be running, you’ll need to test which can be done through a tool such as Optimal Workshop’s OptimalSort. OptimalSort enables you to run unmoderated card sorts remotely (or print out cards for a moderated/in-person card sort!). After your participants have completed your card sort, you can access the benefits of OptimalSort’s powerful result analysis functions.

‍

Learn more about running a card sort and more through our 101 guide.

‍

After you’ve run your initial open card sort with users, you should have everything you need to create the first iteration of your taxonomy. Consider everything you learned during the card sort and cross reference that with your business goals and any tech constraints you might be facing. Don’t stress too much about nailing it this time around — remember this is the first iteration and as you test more and learn more, you can make changes. Build out your taxonomy in Post-it notes with a team and then whack it into a spreadsheet to make future testing and iteration activities easier.

‍

How to test a taxonomy

‍

Now that you have the first iteration of your taxonomy, it’s time to have a go at structuring those groups into an IA and running a tree test. A tree test works like a card sort but in reverse — it allows you to test your thinking by working backwards. Optimal Workshop’s Treejack is an online tree testing tool that helps you assess the findability of your content without any visual design elements. All you need are clear objectives for what you’d like to learn more about and a spreadsheet version of your draft IA (told you it would come in handy! ).

‍

Learn more about Treejack and tree testing through our equally handy 101 guide.

‍

Another way to test your taxonomy thinking is to run another card sort. However this time, a hybrid or a closed card sort might be more suitable. A closed card sort would be useful if you’ve got evidence to suggest that your group labels are making sense to users but you’re not 100% sure what belongs in each group. A hybrid sort will let you go one step further and tell you if your content does in fact fit within those labels and if not you’ll also pick up some new ideas to iterate your taxonomy further.

Developing a taxonomy is like any other design process. Bring users into your process as early as you can and never stop iterating, improving and learning.Oh, and about those animals — I wasn’t entirely wrong. The way we classify animals (e.g., vertebrates and invertebrates) is a taxonomy. There are taxonomies everywhere and they’re not all digital. From libraries to supermarkets, we are immersed in taxonomies. It's the role of information architects to determine how these taxonomies are presented to us and how we navigate through them — the possibilities are truly endless!

‍

Further reading

• "What is information architecture" — a guide we created to help people learn more about information architecture, including stuff for beginners and those who are more advanced.
• "An introduction to taxonomies" — an article from UXBooth's Sarah Khan that details what taxonomies are, taxonomy displays and more.

"Dear Optimal Workshop

How do you make a small link attractive to people (icon vs. text)?"

— Cassie

‍

Dear Cassie,

‍

I'm going to dive straight into this interesting question with a good old game of Pros and Cons, and then offer a resolution of sorts, with a meandering thought or two along the way. Let's kick things off with Team Icon.

‍

The good side of icons: A picture is worth a 1000 words

‍

When shopping online, the number above the little shopping trolley icon tells me how badly behaved I’ve been, and if I click on it, I know I’ll get to gleefully review all the shoes I've selected so far. There’s a whole heap of icons out there like this that people have absorbed and can use without thinking twice. Marli Mesibov wrote a fantastic article on the use of icons for UX Booth on the use of icons that is well worth a look. Marli discusses how they work well on small screens, which is a definite bonus when you’re on the go! Young children who aren’t yet literate can easily figure out how to open and play Angry Birds on their parent’s smartphones thanks to icons. And icons also have a great capacity for bridging language barriers.

‍

The not so good side of icons: We’re too old for guessing games

‍

On the flipside, there are some issues that may huff and puff and blow that cute little home icon down. Starting with there being no consistent standard for them. Sure, there are a handful that are universal like home and print, but beyond that it seems to be a free-for-all. Icons are very much in the hands of the designer and this leaves a lot of room for confusion to grow like bacteria in a badly maintained office refrigerator. Difficult to understand icons can also seriously hinder a user’s ability to learn how to use your website or application. When icons don't communicate what they intend, well, you can guess what happens. In a great piece advocating for text over icons, Joshua Porter writes about an experience he had:

‍

"I have used this UI now for a week and I still have do a double-take each time I want to navigate. I’m not learning what the icons mean. The folder icon represents 'Projects', which I can usually remember (but I think I remember it because it’s simply the first and default option). The second icon, a factory, is actually a link to the 'Manage' screen, where you manage people and projects. This trips me up every time."

‍

If people can't pick up the meaning of your icons quickly and intuitively, they may just stop trying altogether. And now, over to Team Label.

‍

The good side of text: What you see is what you get

‍

Sometimes language really is the fastest vehicle you've got for delivering a message. If you choose the right words to label your links, you'll leave the user with very little doubt as to what lies beneath. It’s that simple. Carefully-considered and well-written labels can cut through the noise and leave minimal ambiguity in their wake. Quoting Joshua Porter again: "Nothing says 'manage' like 'manage'. In other words, in the battle of clarity between icons and labels, labels always win."

‍

The not so good side of text: Your flat shoe is my ballet pump

‍

Text labels can get messy and be just as confusing as unfamiliar icons! Words and phrases sometimes don’t mean the same thing to different people. One person’s flat enclosed shoe may be another person’s ballet pump, and the next person may be left scratching their head because they thought pumps were heels and all they wanted was a ballet flat! Text only labels can also become problematic if there isn’t a clear hierarchy of information, and if you have multiple links on one page or screen.  Bombarding people with a page of short text links may make it difficult for them to find a starting point. And text may also hold back people who speak other languages.

‍

The compromise: Pair icons up with text labels

‍

Because things are always better when we work together! Capitalise on the combined force of text and icons to solve the dilemma. And I don’t mean you should rely on hovers — make both text and icon visible at all times. Two great examples are Google Apps (because nothing says storage like a weird geometric shape...) and the iPhone App store (because the compass and magnifying glass would pose an interesting challenge without text...):

‍

‍

So what comes next? (You can probably guess what I'm going to say)

‍

Whatever you decide to run with, test it. Use whatever techniques you have on hand to test all three possibilities — icons only, text only, and icons and text — on real people. No Pros and Cons list, however wonderful, can beat that. And you know, the results will probably surprise you. I ran a quick study recently using Chalkmark to find out where people on the ASOS women's shoes page would click to get to the homepage (and yes, I can alway find ways to make shoe shopping an integral part of my job). 28 people responded, and...

‍

‍

‍

...a whopping 89% of them clicked the logo, just 7% clicked the home icon, and just one person (the remaining 4%) clicked the label 'Home'. Enough said. Thanks for your question Cassie. To finish, here's some on-topic (and well-earned) comic relief (via @TechnicallyRon)

‍