During the design process information architecture is often carried out by an information architect and/or a team of UX designers, developers, and other professionals.  As a content professional, it’s best not to stand at arm’s length. It's important to understand the basics of information architecture and how it impacts your content strategy and user experience.

What is information architecture?

Information architecture (IA) is the system and structure designed to organize and label content on your website, app, or product. It is often visualized through wireframes, spreadsheets, and diagrams. It is the way the content is ordered as well as the labels given to the content, and the differing pieces of information. The IA is created with this knowledge as well as an understanding of the product owner’s intentions and the user’s requirements. 

Put simply information architecture looks at the organization, labeling, navigation, and search for supporting usability, functionality, and findability.

When designing IA, it is important to consider questions such as:

• What content do we currently have?
• What labels/names do users use and how do we reflect this in our website?
• How will the pages all be related to each other?
• What metadata and taxonomy are needed?
• How will navigation and browse work?
• How will search work?
• How will the information be laid out on the page?
• What do the product owners want users to do/find?

Taxonomy and content strategy

When it comes to content strategy, it can be equally important to focus on the taxonomy of the content. But what is taxonomy? 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) which we find our way around using navigation.

With this understanding, the content strategy looks at what the needs of the organization are, the desires of the users (what are they looking for), and what sits in between. Using a strong, logical, and intuitive taxonomy structure will knit these needs together in a way that makes sense.

What is content architecture?

Content architecture, if you like, is the umbrella term used for encompassing the way that content is organized, structured, labeled, and linked together. Effective content architecture is essential to creating a great content management experience for editors, content managers, and content strategists who need to load, manage and organize the content on an ongoing basis. More importantly, solid content architecture is essential to creating a positive user experience for those consuming the content.

Focusing on creating content architecture that works will benefit your organization by increasing your content team’s agility and empowering them to rely less on developers to find and organize content. When the content team has a clean and easy-to-navigate backend of a website, it benefits the front end as the team can easily grow the content on its front end over time.

What is the relationship between IA and content?

Effective, thought-through information architecture is the backbone of a well-designed website. When developing a website considering how it is used (internally and externally), the content strategy, and how it can function for both sides is vital.

With an understanding of how the content is organized, labeled, and navigable, the content strategy can play a big part in informing this and vice versa. Developing a content taxonomy that makes searching and finding content intuitive can improve the user experience. Not only that, a content strategy that works with the established taxonomy can show up gaps in content. Possibly showing where there is space for more content that speaks to what users want to see. Delivering great content, well organized and easy to find.

How to make the most of content strategy and IA 

Content strategy shouldn’t only be thought about once the website is built - it should also be considered at the beginning of the development. Why? As the organization evolves and grows, so will the content strategy. With a well-established content taxonomy, the IA can be tweaked and worked as things change. Just as much as the content strategy is changing, the information architecture should also.

And never forget that information architecture isn’t only about what the end users need, effective IA creates a back end that is simple to use, load, tag, and sort for the content team. Keeping the website up to date, content frequently updated and added to. Easing the flow of great content delivered to users. Everyone is happy!

Wrap Up

Content strategists and information architects aren’t miles apart. Each is working to make the very best website for the end user. Information architecture uses taxonomy to make order of the information, where content strategy can drive this taxonomy, helping to label, name, tag and order the content in a way that makes sense to the user and the website owner. And even to preempt what might be needed in the future.

Information architecture is so much more than finding your way around a website or app. IA should be considered the foundation of a great user experience. The planning and consideration that goes into how information is organized labeled, and named. Once this foundation is laid, the user interface is what sits above and allows users to access the information. Navigation is one way that designers can point users in the right direction. But without correct labeling and naming (or even searching) navigation can only get us part of the way.

Let’s go into detail about what information architecture and the role navigation really plays. 

What is information architecture for a website?

Probably the easiest example of navigation is on a website. We are familiar with websites and how navigation can make or break a user experience. A website's information architecture (IA) can be considered to be made of two main components:

• Identification and the definition of the site content and functionality.
• Underlying organization, labeling, and structure that will define the relationship between the site's content and functionality.

When a user lands on your website they won’t see the information architecture, rather, they will be interacting with the user interface (UI). While the IA itself is not visible while using the user interface it most certainly impacts the user's experience (UX). 

The IA should be planned and the content structure visualized through diagrams, spreadsheets, and with wireframes, prototypes, or comprehensive layouts. Designing with the IA in mind web designers can create a better user experience. The user will not see the structure of the website but they will quickly discover the way the content has been divided up and then connected visually. And how well the information architecture matches these expectations will influence their UX.

When this interaction is not a great experience, users may leave feeling that your website content or functionality is not what they needed. They may end up feeling disappointed with the experience due to poor organization, naming, or structure.

What’s the difference between IA and navigation?

Ensuring that the information architecture is thought through, considered from the end users’ perspective, tested, and planned is essential to building a great website from the ground up. Great navigation is what cues users to move on to the next step in their journey and ultimately will determine their experience.

Navigation is but one part of the story and tools to help users find their way through a website, app, or other product. 

Information architecture can be broken down into three main areas to consider when building a great user experience:

• Navigation: How people make their way through information (website content)
• Labels: How information is named and represented.
• Search: How people will look for information (keywords, categories)

When put like this it does seem pretty straightforward. Information architecture isn’t just how your information is navigated (on a website or app) but how it is labeled, the taxonomy, and the searchability help users find what they need from the information architecture.

How do the IA and navigation work together best?

An information architecture that has been planned, considered, researched, and structured with understanding and the intention of the needs of users and the owners will be robust and at its very best intuitive.

With an information architecture that has been organized well the navigation doesn’t need to work as hard. With correct labeling and organization of the content, navigation acts as a visual guide on your product to help users find their way to what they want. Imagine well-named road signs that are expected and easily seen. It makes finding what (where) you want much easier, even on a dark night.

Coupled with robust IA navigation will provide intuitive pathways for users to complete tasks. For instance, if you want your users to find where your contact information is, making certain that there is a navigation tab at the top of your website labeled ‘contact us’ which then has what might be expected (address, phone number, map, and even an email contact form) will make sense for users and the owners of the website.

Wrap Up

Whilst navigation is a key component to users finding their way through your content information architecture is so much more than navigation. IA is the foundation of a great product, naming, labeling, organizing, and planning your information in a logical and expected way. Navigation is the sign that directs people to the content they want. And from there to the task or product they are looking for. If there is navigation without thought through information architecture, they may look in the wrong place, becoming lost and abandoning their task altogether.

We all know that building a robust information architecture (IA) can make or break your product. And getting it right can rely on robust user research. Especially when it comes to creating human-centered, intuitive products that deliver outstanding user experiences.

‍

But what are the best methods to test your information architecture? To make sure that your focus is on building an information architecture that is truly based on what your users want, and need.

‍

What is user research? 🗣️🧑🏻💻

‍

With all the will in the world, your product (or website or mobile app) may work perfectly and be as intuitive as possible. But, if it is only built on information from your internal organizational perspective, it may not measure up in the eyes of your user. Often, organizations make major design decisions without fully considering their users. User research (UX) backs up decisions with data, helping to make sure that design decisions are strategic decisions. 

‍

Testing your information architecture can also help establish the structure for a better product from the ground up. And ultimately, the performance of your product. User experience research focuses your design on understanding your user expectations, behaviors, needs, and motivations. It is an essential part of creating, building, and maintaining great products. 

‍

Taking the time to understand your users through research can be incredibly rewarding with the insights and data-backed information that can alter your product for the better. But what are the key user research methods for your information architecture? Let’s take a look.

‍

Research methods for information architecture ⚒️

‍

There is more than one way to test your IA. And testing with one method is good, but with more than one is even better. And, of course, the more often you test, especially when there are major additions or changes, you can tweak and update your IA to improve and delight your user’s experience.

‍

Card Sorting 🃏

‍

Card sorting is a user research method that allows you to discover how users understand and categorize information. It’s particularly useful when you are starting the planning process of your information architecture or at any stage you notice issues or are making changes. Putting the power into your users’ hands and asking how they would intuitively sort the information. In a card sort, participants sort cards containing different items into labeled groups. You can use the results of a card sort to figure out how to group and label the information in a way that makes the most sense to your audience. 

‍

There are a number of techniques and methods that can be applied to a card sort. Take a look here if you’d like to know more.

‍

Card sorting has many applications. It’s as useful for figuring out how content should be grouped on a website or in an app as it is for figuring out how to arrange the items in a retail store.You can also run a card sort in person, using physical cards, or remotely with online tools such as OptimalSort.

‍

Tree Testing 🌲

‍

Taking a look at your information architecture from the other side can also be valuable. Tree testing is a usability method for evaluating the findability of topics on a product. Testing is done on a simplified text version of your site structure without the influence of navigation aids and visual design.

‍

Tree testing tells you how easily people can find information on your product and exactly where people get lost. Your users rely on your information architecture – how you label and organize your content – to get things done.

‍

Tree testing can answer questions like:

• Do my labels make sense to people?
• Is my content grouped logically to people?
• Can people find the information they want easily and quickly? If not, what’s stopping them?

‍

Treejack is our tree testing tool and is designed to make it easy to test your information architecture. Running a tree test isn’t actually that difficult, especially if you’re using the right tool. You’ll  learn how to set useful objectives, how to build your tree, write your tasks, recruit participants, and measure results.

‍

Combining information architecture research methods 🏗

‍

If you are wanting a fully rounded view of your information architecture, it can be useful to combine your research methods.

‍

Tree testing and card sorting, along with usability testing, can give you insights into your users and audience. How do they think? How do they find their way through your product? And how do they want to see things labeled, organized, and sorted? 

‍

If you want to get fully into the comparison of tree testing and card sorting, take a look at our article here, which compares the options and explains which is best and when. 

According to Abby Covert, author, teacher and community leader in the field of information architecture (IA) : ‘IA is the way we arrange pieces of content to make sense when experienced as a whole. By this definition: there is information architecture in everything. Mindblown?’

‍

😮 (That’s a resounding yes from an IA rookie like me.)

‍

In this issue of CRUX we go in search of information architecture and have some surprising encounters in the worlds of emoji, elevators, walking tracks, games and more. We meet UX designers, developers, researchers and even a Senior Park Ranger. It seems you can have your ‘IA hat’ on without even realising it. That’s the power of information architecture.

‍

Some highlights from this issue:

‍

• UX research and strategy specialist, Q Walker explores the world of emoji from an information architecture perspective and sparks curiosity along the way. Have you ever wondered why clock emojis are organized under travel and places? 🤔

• We talk to Senior Park Ranger David Rogers about the thinking behind creating and building New Zealand’s national walking track network and reveal how information architecture can also live ‘in the wild’.

• UX developer Ben Chapman delves into the classification systems of libraries over time and ponders the pros and cons for users of moving information online.

• We talk to Sam Cope, Lead UX Designer at Wētā Workshop’s Interactive division about what it takes to drive design decisions with the end user in mind - something crucial for any video game’s success, whether it’s a blockbuster or something more niche.

• And much more about information architecture in unexpected places….

‍

The stories and people in this issue of CRUX certainly captured our imagination and attention - we hope they inspire and even surprise you too.

‍

Get comfortable and settle in for a great read. Welcome to CRUX #6.

‍

A plug for the next issue

‍

Do you have a burning idea to share or a conversation you’re dying to kickstart that’s of interest to the world of UX?  Now’s your chance.  We’re already on the lookout for contributors for our next edition of CRUX for 2022.  To find out more please drop us a line.

Testing and comparing multiple variations of trees will help you nail down an effective navigation structure before you implement it, saving time and costly mistakes. Treejack's comparison feature allows you to compare two tasks from two different Treejack studies without leaving the results page. It helps make comparing your variations easier and faster by putting results side-by-side for you to explore simultaneously. 

The image above shows a common workflow of how Optimal Workshop tools can be used together to improve your navigation structure. 

How does it work?

Step 1. Let's compare tasks

First things first, sign into your Optimal Workshop account.

Step 2. Open the Treejack study

Open the tree test that you want to start your comparison from, then navigate to the Task Results tab in the Analysis section.

Step 3. Click on compare tasks

Click the ‘compare tasks’ button in your chosen task.

Step 4. Select the study

Next select the study and task you want to compare then click 'Compare tasks'.

Step 5. Compare the results

You can now compare the two tasks together and start the analysis process. Do this as many times, with as many tests and tasks, as you need to.

Send us your feedback

We’ve got a lot of exciting improvements in the pipeline and as always, we’d love your feedback. You can make feature requests, vote on existing requests and send feedback in Optimal Workshop using the Resource Centre. It's located at the bottom right hand corner of your account, just click the ? icon. 

Log in now let us know what you think!

Ever wondered what the relationship is between information architecture (IA) and UX? Simply put, IA is the foundation of UX. We outline why.

‍

What is Information Architecture? 🛠️

‍

According to Abby Covert, a leader in the field of information architecture, IA is ‘the way we arrange the parts to make sense of the whole.’ This can relate to a website, a retail store or an app. And you could even consider the way a library is sorted to be information architecture. For the purposes of this article, we will focus on digital products (apps or websites).

‍

Well-organized information architecture is fundamentally important to the success of your product. As a designer, knowing the content you are delivering and how, is fundamental to creating a UX that performs. Working with the needs of the organization and meeting the requirements of the users in a meaningful and delightful way. Organizing and structuring the information so that navigating, searching, and understanding your product is seamless is ultimately what UX design is all about. Arranging the parts to make sense of the whole, you could say.

‍

While design is about creating visual pointers for users to find their way, information architecture can be broken down into 3 main areas to consider when building a great user experience:

‍

• Navigation: How people make their way through information 
• Labels: How information is named and represented.
• Search: How people will look for information (keywords, categories)

‍

When put like this it does seem pretty straightforward. Maybe even simple? But these tasks need to be straightforward for your users. Putting thought, time, and research at the front of your design and build can increase your chances of delivering an intuitive product. In fact, at any point in your product’s life cycle, it’s worth testing and reviewing these 3 areas.  

‍

Key things to consider to build an effective IA for UX 🏗

‍

Developing a well-thought-out and researched information architecture for your product could be considered a foundation step to creating a great UX product. To help you on your way, here are 6 key things to consider when building effective information architecture for a great user experience. 

‍

1. Define the goals of your organization: Before starting your IA plan, uncover what is the purpose of your product and how this will align with the goals of your stakeholders.
2. Figure out your user’s goals: Who do you want to use your product? Create scenarios, discuss with probable users and find out what they’ll use your product for and how they’ll use it.  
3. Study your competitors: Take note of websites, apps and other digital products that are similar to yours and look at their information architecture from a UX point of view. How does the design work with the IA. Is it simple to navigate? Easy to find what to do next?  Look at how key information is designed and displayed.
4. Draw a site map: Once the IA is planned and developed and the content is ready, it’s time to figure out how users are going to access all of your information. Spend time planning navigation that is not too complex that will help users to browse your product easily. 
5. Cross browser testing: Your information architecture behavior may vary from one browser so it’s worth doing some cross-browser compatibility testing. It would be very disappointing to work so hard to get the best UX with your product, only to be let down because of browser variances.
6. Usability testing: End users are the perfect people to let you know how your product is performing. Set up a testing/staging environment and test on external users. Observing your participants while they move their way through your product uninterrupted and listening to their opinions can shed light on the successes (and failures) in a very insightful way. 

‍

Wrap Up 🌯

‍

Information architecture is the foundation of designing a great product that meets (or even exceeds) your users’ needs, wants, and desires. By balancing an organization’s needs with insight into what users actually want, you’re well equipped to design an information architecture  that helps build a product that delivers a positive user experience. Research, test, research, and test again should be the mantra throughout the development, design, and implementation of your product and beyond.