March 6, 2023
4 min

Navigating the Complexities of Information Architecture vs Data Architecture

Thanks to an ever-growing digital world, businesses are spoiled for information and data. The more complex the business, the more information there is and the more complicated the business requirements are. But where there are challenges, there is opportunity. That’s where information architecture and data architecture come in.

Information and data architecture both seek to make sense of the plethora of information a business handles. However, the two have different roles to play in the way businesses use, move, maintain, and present data - both to internal and external stakeholders. So what are they and why should businesses take note?

Defining Information Architecture 🗺️

Information architecture is the structure used to organize and label content on websites, mobile applications and other digital environments. Its primary purpose is to enhance user experience by ensuring information is structured in an accessible, usable and relevant way.

Information architecture seeks to understand user needs and goals by analyzing both existing and required information, then building an information framework in a logical and user-friendly way. It deals with three main components:

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

Whilst this information sits in the background, it’s the layer upon which you build the design of your digital products.

Information architects bring data from file systems and databases to life by building meaningful narratives and stories. Outputs can include site-mapping, information architecture diagrams and content inventories. These outputs are supported by user research techniques such as card sorting, tree testing, user surveys and first-click testing.

Defining Data Architecture 💻

Data architecture bridges the gap between business needs, goals, and system requirements related to data handling. It sets out a framework for managing data assets, the flow of data and the maintenance of data systems. As such, it has a slightly more macro view than information architecture and concerns itself with emerging technologies such as artificial intelligence, machine learning, and blockchain.

Where information architecture centers around the end-user interaction, data architecture centers around practical handling and operation of data processes i.e. collection through to transformation, distribution, and consumption. Because of this, data architecture must take into account the businesses ability to scale operations, integrate with third party systems, support real-time data processes and the reduction of operating costs. Modern data architecture may point to artificial intelligence to tackle some of these challenges.

The Importance of Enterprise Architects in Information and Data Architecture 🏗

Enterprise architects are big-picture people. Data architecture and information architecture both fall within their remit, and they often oversee other data management job specialities within an IT department.

As a leader (and often, visionary) within a business, enterprise architects shoulder the responsibility of ‘mission critical’ projects. As a result, they tend to have several years experience with IT systems, backed by a bachelor’s degree in computer science, IT management, data science or similar. Many will hold a master’s degree and specialty certifications.

The role involves collaborating with senior business leaders, solution-delivery teams and external stakeholders, and requires creative problem solving and excellent communication skills. Therefore, enterprise architects very much steer the ship when it comes to information and data architecture. Combining high-level business strategy with knowledge of ‘the nuts and bolts’ of IT data systems and processes, they command an annual salary in New Zealand between $150,000 and $200,000 per annum..

Continuous improvement within any business that has substantial IT infrastructure calls for serious investment in enterprise architecture.

Designing and Implementing an Effective Information and Data Architecture 𝞹📈🧠📚

Once overarching business goals are aligned with the scope of data and system requirements, information and data architecture design (or redesign) can begin.

Crucial to the design and implementation process is developing an architecture framework. This is a set of guidelines that lays out principles, practices, tools and approaches required to complete the design. It supports system design decisions, assigns key tasks and provides project guidance throughout the design process. The framework essentially aims to unite disparate teams and maintain business and IT alignment.

The choice of architecture design is also critical. It should consider scalability, performance, maintainability and adaptability to emerging technology. Which is why cloud platforms feature so heavily in modern data architecture. Cloud architects will navigate the architecture design and technical requirements of cloud-based delivery models, which offer the solution to those scalability and adaptability challenges. They are responsible for bridging the gaps between complex business problems and solutions in the cloud. Modern data architecture tends to involve some form of cloud delivery component.

Throughout implementation, data and information architects will work closely with designers and engineers until testable architecture is ready. User research and testing will be carried out, and a feedback loop will commence until requirements are met. Users, as always, should be at the center of your digital product.

Summing Up the Complexities of Information and Data Architecture 🧮

Whilst the difference between information and data architecture can appear nuanced on the surface, they hold unique roles when delivering a cohesive, user-friendly digital product.

Think of a sliding scale where business operations sit at one end, and users sit at the other. Data architecture addresses challenges closer to the business: aligning business requirements and goals with how data flows through the system. On the other hand, information architecture addresses the challenges related to how this data is organized and interpreted for the end user.

At the end of the day, both information and data architecture need to work in harmony to satisfy the user and the business.

Share this article
Author
Optimal
Workshop

Related articles

View all blog articles
Learn more
1 min read

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

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.

Learn more
1 min read

Are small links more attractive to people as icons or text?

"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...):

When text and icons wins

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...

Chalkmark first click text

...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)

When icons go wrong
Learn more
1 min read

Why is information architecture important to UX design?

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.’ Information architecture (IA) is found in every digital product, from websites and apps to an intranet. 

For the purposes of this article we focus on the importance of information architecture to user experience (UX) design because IA is fundamentally important to the success of your user experience. It determines how users will access your  content and ultimately how successful their experience is when using your product. 

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 in at the front of your design and build can help build an intuitive product. IA is the structure that sits in behind and allows the design to tell the story and the content to be found in an easy way.

The role of information architecture in UX design 🏗️

Information architecture forms the framework for any UX design project. You need to consider the visual elements, functionality, interaction, and navigation and if they are built according to IA principles. If not considered fully even the most compelling content and powerful user experience design can fail without an organized and functional IA design. Disorganized content can make finding your way through difficult, meaning users get lost, annoyed and frustrated. Frustrated users don’t stick around and most likely don’t come back.

Through solving or preempting users’ issues with research and designing powerful and effective IA it reduces usability and navigation problems. Meaning that researched, thought through and designed information architecture can save both money and time for your organization in the longer term.

What is the difference between IA and UX? 🤯

Often it can be confusing that there isn’t much difference between IA and UX design. While these terms do relate to each other and need to be considered alongside, they are not one and the same.

Information architecture (IA) is the discipline of making information findable and understandable, helping people understand their surroundings and find what they’re looking for online and in the real world” - Interaction Design

User experience (UX) design is the process design teams use to create products
that provide meaningful and relevant experiences to users” - Interaction Design

UX design is well grounded with good functional information architecture but that’s not where it stops. The user experience focus is on influencing users’ behaviors and actions through emotion and psychology. Information architecture is focussed on the users' goals and task completion. They work together to create the very best user experience. IA provides the foundation of a well organized space that is easy to navigate and UX design ensures that the overall experience meets (or exceeds) users’ expectations, through their wants, needs and desires.

The key components of IA 🧱

There are four key components to consider when building a strong information architecture:

Labeling

How information is named and represented. Labels need to communicate information to users without using too much space or requiring much work on the user’s part.

Navigation

How people make their way through information. Without robust IA which has been thought through this is the quickest way to confuse users. If they can’t find their way to the information they need, they won’t be able to complete their task. It really is that simple.

Search

How people will look for information (keywords, categories). A search system is especially important when there is a lot of content to wade through. A search engine, filters, and many other tools help users search content. Great UX design will consider how the information will be displayed once searched.

Organization

How the information is ordered. These help users to predict where they can find information easily:

  • Hierarchical is the hierarchy of the content and literally the order of importance
    the user expects to see information against what the organization needs.
  • Sequential Taking a stroll in your user's shoes can be valuable. Considering the path a user would take and the journey they make. Walking step-by-step, ensuring that as users progress through their tasks they are easily led to the next step.
  • Matrix This is a little more complicated for users as it lets them choose how to navigate on their own. Users are given the choice of content organization. For example, the searchability of a website. Where the user could choose to search by topic, size, price or any other filter or option.

Wrap up 🥙

Information architecture is a key part of a powerful user experience design. Efficient IA helps users quickly and easily move through content and find what they want.  And what do users want but to find what they want, complete their task and get on with their day!

Provide an IA that functions well, is intuitive to use and well labeled, coupled with UX design that is smooth, attractive and responds to users needs, wants and desires and you’ll have a winner on the day.

Seeing is believing

Explore our tools and see how Optimal makes gathering insights simple, powerful, and impactful.