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.

Information architecture (IA) isn’t the easiest space for a newcomer. The myriad terms and technologies can often be quite tricky to understand on their own – not to mention how they all fit together.

We wanted to help, so we’ve put together a comprehensive cheat sheet/glossary that you can use whenever the topic of IA comes up.

Information architecture

Information architecture is the structure used to organize and label content on websites, mobile applications and other digital environments. At a very basic level, IA determines the paths people take to get to the content they’re looking for and where they might get lost.

IA isn’t actually one “thing”, but a number of different elements:

• Labels: How information is represented
• Navigation: How people make their way through the information
• Search: How people look for information

It’s also the layer upon which you build the design. This means that for your users, they’ll never likely see the IA – but they will feel the effects of the decisions you make when designing it. Your IA should help people find what they’re looking for, regardless of where the IA exists. It’s as important for desktop users as it is for mobile.

Experience architecture

The term ‘experience architecture’ refers to a wider set of practices or terms that includes information architecture. Experience architecture covers IA, interaction design and experience design. It’s similar to how user experience (UX) is just one element under the wider customer experience (CX) umbrella.

Note that just as the field of information architecture has information architects, experience architecture has experience architects; people responsible for planning and executing experience architecture deliverables. Typically, the experience architecture role is quite varied in that it requires expertise in user-centered design, human behavior and interaction design.

User journey

A user journey is basically what it sounds like – the experiences someone has when they interact with something. It’s also most commonly used to describe these experiences and interactions in a software context.

User journeys describe the steps users take to complete a task when interacting with a website or other digital service. For example, for a photo storage app, the user journey may look something like this:

1. User runs out of storage space for photos
2. User finds new photos app on app store
3. User installs new photos app
4. User creates account
5. User begins uploading photos from device

Typically, you’d create a user journey in the discovery phase of a project, as you can use this tool to visualize what the users need and to influence wireframe and information architecture development.

Depending on your needs, your user journey may be quite a bit more detailed, with overarching categories ‘before’, ‘during’ and ‘after’ to show where the user is with regards to using the product. You can also add in ideal emotions at each stage.

Wireframing

Chances are if you’re using a website or mobile app, it was a wireframe at some point in the past. Wireframing is essentially a way to design digital applications at a structural level, a way to map out broadly where different elements like content and functionality sit before adding in visual design.

Wireframing is to websites, apps and other digital applications what the rough first sketch of a building is to a finished skyscraper. It’s foundational, yet entirely important to nail down broad strokes ideas before investing more heavily in design.

Why might you produce a wireframe? In addition to using it as a way to prototype ideas prior to the visual design process, wireframes are an important method of getting stakeholders and other teams onboard.

Labeling system

In the world of information architecture, labels represent a relationship between your users and content. The idea behind labels is to communicate information to users without using too much space or requiring much work on the user’s part.

Let’s take a look at an example. ‘About us’ is a label that represents a larger chunk of information. On a website, this could be information about the people who work at the organization, what the office space is like and the work that the organization does. You wouldn’t want to present all of this information to a user on the homepage, so instead, you use a label like ‘About us’ to trigger the user’s association with that term. Once they’ve seen the label, a user can decide whether they want to proceed. In a nutshell, a label should be used to communicate information clearly and efficiently.

Labels are understandably important, and things can go awry when the people designing websites and other digital applications don’t adequately consider the importance of correct labeling. Perhaps more than most other parts of a website, poor labeling is an easy way to spot websites where user needs haven’t been appropriately considered.

Search system

Search is how your users go about looking for the information they require, whereas a search system is essentially a search engine: a way to sidestep the act of navigating through a website and search directly for information. One of the biggest misconceptions when it comes to designing digital applications is that search is the answer to all navigation problems. Search systems are often seen as a way to avoid developing user-focused navigation systems, as the common thinking is that users know what they’re looking for and so will just plug terms into a search bar.

This isn’t actually true, and there’s a great quote from Larry Page that neatly summarizes this argument: “The ultimate search engine would basically understand everything in the world, and it would always give you the right thing. And we’re a long, long way from that”.

Search engines often become bandages for websites with inadequate browsing systems. When considering adding a search engine to a website, consider how much content you actually have. The last thing you want to do is have to maintain a search engine when the browsing experience meets user needs.

When a search engine is appropriate:

• Websites with large quantities of content (50+ pages)
• Websites with long, dense pages
• Any situation where browsing will take significantly longer

Metadata and taxonomies

In the world of information architecture, 2 terms that get thrown around and mixed up more than most others are taxonomy and metadata. Here’s a breakdown of what both of them mean, and how they relate to each other.

Metadata makes content findable and understandable for users and computer systems, it’s data about data. Rachel Lovinger describes it as “information about the content that provides structure, context, and meaning”. Photos typically have significant quantities of metadata attached to them, information like where the photo was taken, the date the photo was taken and the device the photo was taken on. Metadata is particularly important to search engines, helping to surface the right content based on what the user is searching for.

Taxonomies, on the other hand, refer to structures that organize information. Unlike metadata which applies to individual pieces of content, taxonomies help to organize content into hierarchical relationships.

So how do metadata and taxonomies work together? Well, if a taxonomy’s goal is to organize content, it needs terms to be stored as metadata. Christine Benson notes that “a taxonomy organizes information, and metadata describes it”. They’re really 2 parts of the same whole.

Wrap up

Hopefully, we’ve given you a clear idea of some of the more important information architecture terms and how they relate to each other. If you want to start rethinking your own website’s information architecture, there’s no better place to start than with a comprehensive understanding of how your users think the information on your website should be structured. You can read more about one of the best methods for this process, card sorting, right here on our blog.

There is an enormous amount of information on the internet. Every page you load is crammed with it. With so much information around, it’s incredibly important to remember that for human minds to be able to actually process and make sense of it, considered, strategic, ordered information architecture is needed.

‍

Information architecture is everywhere digitally, but where does it actually live? IA sits in behind all of the digital interfaces we humans use (and even out in the real world). It ideally has been considered, researched, and implemented with humans in mind, though as we all know, this isn’t always the case.  

‍

Information architecture always has a role to play, and here we’ll focus on 4 key digital spaces where information architecture is most prominent, and likely most familiar.

‍

1. Websites
2. Apps
3. Company intranet
4. Social media software

‍

To find out more about putting information architecture into action check out our blog.

‍

1. Websites 🌐

‍

‍

Information architecture for websites can often be confused with navigation. While site navigation is super important, (think of it as the ‘skin’ that sits above the information), that’s only part of the story. Great website architecture considers and organizes user requirements, organizing the content and structure of the website with labels, search and navigation that simply makes sense and is easy to use. Done well, it will  feel simple and straightforward, guiding users through smoothly.

‍

Hubspot has a great article on IA for websites and how they can be structured. From a complex library system, to travel booking systems. Each has its own needs and can be quite deep in layers of information. The trick is to create a website structure, based on user needs, that makes sense of the piles of information and a simple navigation that sits above, making the journey to task completion as quick as possible. Working together they make any user experience feel quick, simple, and intuitive! 

‍

2. Apps 📱

‍

‍

An organization's app acts as the first point of contact. It needs to be super simple, clean, and quick to interact with. A well thought out, thorough, researched, and organized information architecture plays a big part in this.

‍

Information architecture for mobile use has a different set of rules than websites. The key consideration here is around the ease of use across a smaller screen. Navigation that makes sense for a laptop or desktop computer can be clunky in a mobile app.

‍

An app's interface needs to have fewer options, and fewer clicks to complete the task. Researching and designing an app’s IA with just the right amount of information is key. Some retail apps are simplified websites, whereas other apps exist on their own merits, with no need for a website.

‍

Bringing it back to the humans that will interact with the app is key to creating a product that delivers on user requirements and increases interaction. 

‍

3. Intranet 🖥

‍

‍

An organizational intranet is possibly less of a priority than a website or an app but is vitally important to the success of an organization. And in these times of remote or hybrid working, intranets have proven to be more valuable than ever. An intranet is more than where to stick newsletters for staff, it is an interface that can make or break the productivity or even the wellbeing of an organization. 

‍

Access to files, information, messaging platforms, and corporate requirements wherever and whenever people are working is more important than ever.  A well researched and designed information architecture can build an intranet that meets users’ requirements, increase communication and interaction and ultimately boost productivity. 

‍

Conducting UX research with staff on what they need to access, when, and how will help inform the intranet IA far more intuitively. The information available (and needed) can be huge, keeping it simple and human focused is key.

‍

Have you ever thought about how poor internal information architecture might be hurting your business?

‍

4. Social media 🤳

‍

‍

Social media software is complex in terms of ecosystem and display of information. Each social media platform has developed over time, think back to Facebook and how it looked when it initially launched. And through the uptake of users, gathering of information over time, and continual research and testing, it has evolved into what we see today. And will continue to evolve with users’ needs.

‍

Every user has a different experience based on the individuals, groups, organizations and even retailers that they choose to interact with (or haven’t chosen via advertising). The piles of information that sit behind and are brought to the interface for an individual through their choice, associations, labels, tags, interests, age, etc will present them with a unique feed. 

‍

The interface of a social media platform needs to be considered, tested, tested again, and occasionally tested or changed once launched as the interaction of users is vitally important.

‍

The information architecture sitting behind is huge in order to enable the agility to pull the right information forward in a dynamic and coherent way. Continuously learning, testing and requesting interaction from users through options to ‘hide’ posts that aren’t appropriate or respond to direct queries about what they do and don’t want to see are just some instances of continuous user research.

‍

Social media continues to be a sophisticated information architecture that is constantly updating and changing with user needs.

‍

Wrap Up 🫔

‍

Information architecture lives wherever there is information needing to be found by humans. Successful information architecture is sorted, organized and labeled in a way that is simple, intuitive, and considered. Making interaction and life simple, which in a world where there are an increasing number of websites, apps, and tools to choose from – intuitive information architecture has never been more important for your business and your customers.