March 15, 2023
3 min

IA vs User Flow: Understanding the Differences and How to Use Them Together

Optimal Workshop

Click, click, click, BOOM! There it is. That thing you were looking for. You couldn’t find it on other websites, but you found it here, and it was easy. You feel like a hero. You thank the website and you leave with a sense of achievement.

What if you could replicate that feeling on your website? What if you could make every user journey so satisfying? By combining information architecture and user flow, you can.

But what are they and how are they different? In this article, we’ll explain how they influence website design and how you can (and should) use them together in your project. We’ll also discuss different user flow research techniques, how they inform great information architecture, and how it doesn’t have to be difficult or time consuming.

What is Information Architecture? 🏗️

Information architecture is the system and structure you use to organize and label content on your website, app or product. It relates closely to user experience design, but it’s slightly different. Think of it as the structure or framework upon which user-facing assets are built.

That being the case, if your information architecture has flaws, your website design will have flaws. It determines how information will be accessible, usable and relevant on your website and should be treated as a critical element of your project. How can we ensure that we have our content organized efficiently to promote seamless interactions?

The answer is research. Without research you’re just guessing. The problem with guessing is that, well, you’re guessing. You tend to organize, categorize and label things the way that you (and maybe your team) would organize things. It’s biassed and subjective. In reality, people process information in all sorts of different ways and good information architecture should reflect that. You’ll often hear us say ‘test early and test often’. This mantra helps to avoid any little niggles during the user experience design process. Card sorting and tree testing are a couple of techniques that you can use to test early.

Card sorting is a research technique that asks users to categorize different pieces of information or content. It’s best used when you have specific, information-related questions. For example, you may want to categorize products in an online store in the most logical way. Or you may have a mountain of blog post categories that need refining. Whatever it is, the benefit of a card sort is that you end up with consensus of how your users expect to see information. Card sorts can even be performed remotely using tools such as OptimalSort.

Tree testing examines how easy it is for your users to find information using a stripped back, text-only representation of your website - almost like a sitemap. Rather than asking users to sort information, they are asked to perform a navigation task, for example, “where would you find today’s best deals?”. Depending on how easy or difficult users find these tasks gives you a great indication of the strengths and weaknesses of your underlying site structure.

As the base structure of your website or app, information architecture has a fundamental influence on how well users access and use your content. It makes sense then that when designing it, you should receive real-world user feedback early on in the piece. Fortunately, there are great online tools like Treejack to quickly and easily test your site structures, categorization and labels.

What is User Flow? 🌊

User flow describes the steps involved for a user to complete a certain task. It lays out what needs to happen for a user to get from starting point to a defined finish line. Why is it important? Because we want that journey to be as efficient as it can possibly be. If it’s not, the user will be left frustrated and dissatisfied, no matter how beautiful the website design is.

At the heart of user flow is, you guessed it, the user. A path that seems obvious to designers might be confusing to an end-user. It’s important to distance yourself from the project and put yourself in the user's shoes. Even better - watch the user. How do they react to a fork in the road? How do they get back on track? Where are they stumbling?

User testing is a great way to observe user flow. But what are you testing? Normally you test based on a user flow diagram. A user flow diagram is generated based on insights from your research from card sorting, tree testing, and questionnaires, for example. It visually outlines the possible paths a user can take to achieve a certain task. The basic structure of a user flow diagram considers the following:

  • A critical path
  • Entry points
  • User end goals
  • Success metrics (time to completion, number of clicks)
  • Steps the user will take in between

Once you have created a user flow diagram you can test it with your users. User testing can be remote or in person and uses a variety of techniques depending on the constraints of your projects. You may consider testing something rough and conceptual like a paper prototype before producing more detailed prototypes.

How to Use Information Architecture and User Flow Together 🤝🏻

By doing the work upfront to create great information architecture you put yourself in a great position to create great user flow. After all, information architecture is designed based on user research. Performing content audits and creating content inventories help to inform early content decisions, followed by user research techniques such as card sorting and tree testing. This research has a direct influence on user flow, since information and content has been given meaning and structure.

The foundational work in designing information architecture leads to user flow diagrams which, as we discussed, are helpful tools in creating seamless user flow. They bridge the gap between information architecture and final user experience by visualizing pathways of specific tasks. By performing user tests on prototypes, the researcher will inevitably find speed bumps, which may highlight flaws in information architecture.

Information architecture and user flow are integrated. This means there should be a constant feedback loop. Early research and categorisation when building information architecture may not translate to seamless user flow in practice. This could be due to integration factors outside of the digital ecosystem you’re designing.

User flow and information architecture are complementary components of creating exceptional website design. Designers should make a conscious decision to apply both in synchrony.

To Sum it Up 🧾

Understanding the relationship between information architecture and user flow is important for any website design. Information architecture provides the organization and structure of content, where user flow applies that structure to how users execute certain tasks in the simplest possible way. The two are intertwined and, when used effectively, provide a framework to ensure seamless, user-friendly website design.

User research and user testing heavily influence the design of both information architecture and user flow. We want users to feel a sense of accomplishment rather than frustration when using a website. Achieving this requires an investment in understanding user needs and goals, and how they consume and categorize information. This is where research techniques such as content audits, tree testing, card sorting and user testing become invaluable.

We’ve always placed high value on solid research, but don’t be put off by it. The research techniques we’ve discussed are highly scalable, and you can be as involved as you want or need to be. Sometimes you don’t even have to be in the same room! The most important thing is to get outside of your team’s bubble and gain real user insight. Check out our information architecture services to ensure you’re on the right path towards powerful, user-centric website design.

Publishing date
March 15, 2023
Share this article

Related articles

min read
Information architecture cheat sheet – 2020 edition

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.

An image from Nielsen Norman Group of a user journey map.

An example of what a user journey map looks

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.

A wireframe example of a webpage.

Here’s an example of a website wireframe

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.

min read
Information Architecture vs Navigation: Creating a Seamless User Experience

When we first think of a beautiful website or app design, we rarely think of content structures, labels, and categories. But that’s exactly where great design and seamless user experiences begin. Beneath fancy fonts, layout, colors, and animations are the real heroes of user-centric design - information architecture and navigation.

Information architecture (IA) is like the blueprint of your website or app - it’s a conceptual content structure of how content is organized and arranged to create seamless interactions. And as useful as your information may be, if your navigation is flawed, users won’t be able to find it. They’ll simply leave your site and look elsewhere.


So, how does navigation and information architecture complement each other to create seamless user experiences?

Understanding Information Architecture

Information architecture refers to the practice of organizing, structuring, and labeling content and information to enhance the user's understanding and navigation of a website or application. It involves designing an intuitive, user-friendly, and efficient system to help users find and access the information they need easily. Good IA is essential for delivering a positive user experience and ensuring that your users can achieve their goals effectively.

IA is often confused with navigation structure. Navigation is a part of IA, and it refers to the way users move through a website or application. IA involves more than navigation; it encompasses the overall organization, labeling, and structure of content and information.

There are three key components of IA: organizational structure, content structure, and navigation structure. The organizational structure defines how information is organized, including the categories, subcategories, and relationships between them. The content structure refers to the way information is arranged and presented, including the hierarchy of information and the types of content used. The navigation structure outlines the pathways and components used for navigating through the information, such as menus, links, and search functions.

Some of the critical navigation components used in IA include menus, site maps, breadcrumb trails, and search functions. Site maps provide a visual representation of the site's structure, while breadcrumb trails show users where they are in the site's hierarchy. Search functions allow users to find specific information quickly.

Navigation: A Vital Element of Information Architecture

Navigation refers to the process of providing users with a means of moving through a website or application to access the information they need. Navigation is an integral part of IA, as it guides users through the organizational structure and content structure of a site, allowing them to find and access the information they require efficiently.

There are several types of navigation, including utility navigation and content navigation. Utility navigation refers to the elements that help users perform specific actions, such as logging in, creating an account, subscribing, or sharing content. Content navigation, on the other hand, refers to the elements used to guide users through the site's content, such as menus, links, and buttons.

Both types of navigation provide users with a roadmap of how the site is organized and how they can access/interact with the information they need. Effective navigation structures are designed to be intuitive and easy to use, minimizing the time and effort required for users to find and access the information they need.

The key elements of effective navigation include clear labeling, logical grouping, and consistency across the site. Clear labeling helps users understand what information they can expect to find under each navigation element, while logical grouping ensures that related content is grouped together, making it easier for users to find what they need. Consistency ensures that users can predict how the site is organized and can find the information they need quickly and easily.

Designing Navigation for a Better User Experience

Since navigation structures need to be intuitive and easy to use, it goes without saying that usability testing is central to determining what is deemed ‘intuitive’ in the first place. What you might deem intuitive, may not be to your target user

We’ve discussed how clear labeling, logical grouping, and consistency are key elements for designing navigation, but can they be tested and confirmed? One common usability test is called card sorting. Card sorting is a user research technique that helps you discover how people understand, label and categorize information. It involves asking users to sort various pieces of information or content into categories. Researchers use card sorting to inform decisions about product categorization, menu items, and navigation structures. Remember, researching these underlying structures also informs your information architecture - a key factor in determining good website design.

Tree testing is another invaluable research tool for creating intuitive and easy to use navigation structures. Tree testing examines how easy it is for your users to find information using a stripped-back, text-only representation of your website - almost like a sitemap. Rather than asking users to sort information, they are asked to perform a navigation task, for example, “where would you find XYZ product on our site?”. Depending on how easy or difficult users find these tasks gives you a great indication of the strengths and weaknesses of your underlying site structure, which then informs your navigation design.

Combine usability testing and the following tips to nail your next navigation design:

  • Keep it simple: Simple navigation structures are easier for users to understand and use. Limit the number of navigation links and group related content together to make it easier for users to find what they need.
  • Use clear and descriptive labels: Navigation labels should be clear and descriptive, accurately reflecting the content they lead to. Avoid using vague or confusing labels that could confuse users.
  • Make it consistent: Consistency across the navigation structure makes it easier for users to understand how the site is organized and find the information they need. Use consistent labeling, grouping, and placement of navigation elements throughout the site.
  • Test and refine: Usability testing is essential for identifying and refining navigation issues. Regular testing can help designers make improvements and ensure the navigation structure remains effective and user-friendly.

Best Practices for Information Architecture and Navigation

Both information architecture and navigation design contribute to great user experience (UX) design by making it easier for users to find the information they need quickly and efficiently. Information architecture helps users understand the relationships between different types of content and how to access them, while navigation design guides users through the content logically and intuitively.

In addition to making it easier for users to find information, great information architecture and navigation design can also help improve engagement and satisfaction. When users can find what they're looking for quickly and easily, they're more likely to stay on your website or application and explore more content. By contrast, poor information architecture and navigation design can lead to frustration, confusion, and disengagement.

So, when it comes to information architecture vs navigation, what are the best practices for design? We discussed some of the best practices for navigation design in the last section i.e. keep it simple, provide clear labels, and be consistent. Great navigation structure generally considers two factors: (1) what you want your users to do and, (2) what your users want to do. Strike a balance between the two, but ultimately your navigation system should focus on the needs of your users. Be sure to use simple language and remember to nest content into user-friendly categories.

Since great navigation design is typically a result of great IA design, it should come as no surprise that the key design principles of IA focus on similar principles. Dan Brown’s eight design principles lay out the best practices of IA design:

  • The principle of objects: Content should be treated as a living, breathing thing. It has lifecycles, behaviors, and attributes.
  • The principle of choices: Less is more. Keep the number of choices to a minimum.
  • The principle of disclosure: Show a preview of information that will help users understand what kind of information is hidden if they dig deeper.
  • The principle of examples: Show examples of content when describing the content of the categories.
  • The principle of front doors: Assume that at least 50% of users will use a different entry point than the home page.
  • The principle of multiple classifications: Offer users several different classification schemes to browse the site’s content.
  • The principle of focused navigation: Keep navigation simple and never mix different things.
  • The principle of growth: Assume that the content on the website will grow. Make sure the website is scalable.

Conclusion

Information architecture and navigation are the unsung heroes of website design that work in synchrony to create seamless user experiences. Information architecture refers to the practice of organizing and structuring content and information, while navigation guides users through the site's structure and content. Both are integral to creating intuitive user experiences.

In many ways, navigation and information architecture share the same traits necessary for success. They both require clear, logical structure, as well as clear labeling and categorization. Their ability to deliver on these traits often determines how well a website or application meets your users needs. Of course, IA and navigation designs should be anchored by user research and usability testing, like card sorting and tree testing, to ensure user experiences are as intuitive as possible!

min read
10 information architecture resources

Information architecture (IA) is the backbone of the web – and essentially every other digital experience. It’s the system that’s used to organize and label content on websites in apps, and it ultimately determines the paths that people take to find what they’re looking for.

IA also underpins the design. Functioning as a kind-of skeleton beneath the polished veneer of what people see, it’s the foundation. Get it wrong, and the house falls down. A poorly thought-out IA and UX may not always cause your target audience to leave a website and look elsewhere, but the odds are certainly higher.

A good IA can make all the difference. After all, would you rather stumble through a website, dropping in and out of pages trying to find what you’re looking for, or use a website with a structure that’s intuitive and reflects the people using it?

We’re always focused on the importance of good information architecture here at Optimal Workshop – after all, we’ve developed a platform of tools to help people do just that – so we thought it was a good idea to compile some more useful IA resources.

5 resources from Optimal Workshop

The Optimal Workshop blog is a goldmine for resources on information architecture. For 10 years, we’ve been busy writing our own helpful guides and resources – and sourcing information from some of the brightest minds in the industry, covering everything from site maps to visual hierarchy.

  1. Learn about information architecture – Our getting started guide is great for anyone wanting to learn the basics of IA or just as a refresher. It’s also a useful tool if you’d like to get someone onside for a project you’re about to begin. We’ve also got guides for tree testing, card sorting and more.
  2. Anatomy of a website series - Architecture, labeling and footers. Our ‘Anatomy of’ series covers some of the basics of website structure. In our first 3 articles, we cover website architecture, website labelling and website footers. Stay tuned for more to come!
  3. How to benchmark your information architecture - Before doing any work on your IA, you need to benchmark it. Here, a guest author explains how to benchmark a site navigation using tree testing.
  4. The ultimate IA reading list - A list within a list! This compilation is a community favourite, and we’re constantly adding more detail to it. It’s a great place to get started if you’d like to expand your IA horizons.
  5. How to develop a taxonomy for your information architecture – Taxonomy refers to how information is grouped, classified and labeled within a shared information environment. Learning how to create and test a taxonomy is essential.

4 resources from the community

  1. Card sorting: Uncover users' mental models for better information architecture – As Nielsen Norman Group states, “Card sorting is a UX research technique in which users organize topics into groups. Use it to create an IA that suits your users' expectations”. It’s one of the best methods to create a better, more user-focused IA.
  2. 5 information architecture warning signs in your analytics reports – Identifying IA problems is difficult – if you don’t know what to look for. While methods like tree testing are invaluable in diagnosing problems, you can also use your analytics reports! Pageviews, conversions, entrances and bounce rates are all great places to start.
  3. The difference between information architecture (IA) and navigation – “IA is the information backbone of the site; navigation refers to those elements in the UI that allow users to reach specific information on the site.” Would you like to know more?
  4. 5 examples of effective information architecture This article covers off some examples of effective information architecture, taking a look at site mapping, content inventories and audits, tree structures and more. 

Alan & Co: Information architecture in the real world

Read about how a small retailer with an online store used Optimal Workshop to improve its website just in time for the busy Christmas shopping season.

Alan & Co is a retailer with several stores and a popular online storefront. Though it still services a lot of customers through its physical stores, the online arm of Alan & Co is growing rapidly. People from all over the world purchase goods through Alan & Co’s online store.

But, despite sales going up and up, staff at Alan & Co have been hearing from customers that the online store can be difficult to use. Finding certain items is confusing and time-consuming, and many are starting to get frustrated and look elsewhere instead.

Seeing an advertisement for Optimal Workshop, the head of online sales at Alan & Co decides to give them a go and see if she can get to the bottom of the problem.

Seeing is believing

Dive into our platform, explore our tools, and discover how easy it can be to conduct effective UX research.