Testing FAQs with people who don’t use your site

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.

Sitting inside any beautifully crafted and designed digital product, there must be a fully functional and considered information architecture.

‍

As much as information architecture shouldn’t be developed in a vacuum. Neither should the design and look of digital products. In fact, a large proportion of the function of digital designers is devoted to supporting users locating content they need and driving them towards content that the product owners want them to find.

‍

Incorporating visual markers to make sure that certain content is distinct from the rest or creating layers that demonstrate the diverse content on a product.

‍

If you do not have quality content, it is impossible to design a quality digital product. It all comes back to creating a user experience that makes sense and is designed to make task completion simple. And this relates back to designing the product with the content planned for it in mind.

‍

8 Principles of information architecture, according to Dan Brown 🏗️

‍

As a designer, the more you know about information architecture, the better the products you design will meet your user requirements and deliver what they need. If you work with an information architect, even better. If you’re still learning about information architecture the 8 Principles according to Dan Brown is a great place to begin.

‍

If you haven’t come across Dan Brown yet, you have more than likely come across his 8 principles. Dan Brown is one of the UX world's most prolific experts with a career that spans most areas of UX designs. He’s written 3 books on the subject and experience across a multitude of high profile projects. Aiding large organizations to make the most of their user experience.

‍

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

‍

It’s highly likely that you’ve already used some, or all, of these IA principles in your designs. Don’t be shy about mastering them, or at the very least be familiar. They can only help you become a better user experience designer.

‍

Wrap up 🌯

‍

Mastering the 8 principles, according to IA expert Dan Brown will see you mastering the complex tasks of information architecture. Understanding IA is key to creating digital designs with a content structure that is functional, logical and just what your users need to navigate your product. Design without good IA doesn’t work as well, just as a content structure without a well designed interface will not engage users.

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.