Building the Blueprint: Information Architecture – Part B

Image Credit

Moving Forward: The Benefits

In Part A of this project, I discussed the meaning of an information architecture, as well as an introduction to my next project. If you have not read that yet, check out Part A here. Let’s talk about some of the benefits an information architecture has to offer. The article, “Top Benefits of Information Architecture for a Better User Experience (UX) Design” highlights these benefits as creating a better project scope, correcting product gaps, and gaining a complete view of the product. I agree with these three benefits, so I’ll discuss them further.

Improving the Scope of Your Project

An information architecture improves the product scope by identifying how to get from one point of an app or website to another. By highlighting the hierarchy and navigation that will exist within the product, it is possible to develop an understanding of how a user will move throughout the app or website.

Identify Gaps or Missing Content

Once the product scope has been improved, it is possible for a designer to identify any gaps or missing information within the product. By doing so, those gaps can be filled and the product can be improved to provide the most optimal user experience.

Understand the Product as a Whole

After both of the previous steps have been taken, a complete view of the product can be gained. The blueprint of the product can be passed on to designers, engineers, to stakeholders, and even potential users to gain an understanding of how the product will work and what the navigation will look like.

After I developed the existing information architecture for Roscoe’s website, as well as a proposed new one, I began to develop one for a potential companion mobile app. Though designing an IA for an app is a bit different than developing one for a website, almost everything remains the same. The major difference is the difference in the display of the navigation from a website to an app, and the way that the content is condensed.

This is the IA that I developed for a companion app for Roscoe, NY’s website. As you can see, some of the information has been condensed to be contained within the app.

The information in an app is typically displayed much differently than on a website, so it is important to take that into account. Furthermore, if a website is linked to another site, this specifically needs to be taken into account when developing an information architecture for an app. Consider what information can be brought to the app, external links can be distracting to a user, but can also provide helpful information where necessary.

Trying Your Hand At It

Try your hand at building an information architecture of your own! Although it may look and seem intimidating and too complex, I promise you it is easier to do than you think!

Leave a comment