Information Architecture

HI All ,

I have collected some data while reading about IA in UX Just thought sharing this in forum.This is about the basic about IA in UX .


What is Information Architecture?


Information Architecture is the creation of a structure for a website, app, or other products that allows users to understand where they are— and where the information they want is— in relation to their current position.


Bad Information Architecture is like a maze — it forces users to complete a journey to find the required information. When users can’t find what they are looking for right from the start there’s a huge possibility that people will abandon a product.


The eight principles of Information Architecture

There are lots of things which should be taken into account when building the Information Architecture for a digital product. In an attempt to summarize the most critical requirements for IA, Dan Brown created eight principles that can be used as a reference:


  • Principle of objects: Content should be treated as a living, breathing thing with a lifecycle, behaviours, and attributes. Different content has different attributes and behaviour’s. An architect should start every project by identifying the kinds of content that will be present.
  • Principle of choices: It’s important to create pages that offer meaningful choices to users. At the same time, the range of available choices available for the user should be focused on a particular task. Too many choices can overwhelm a user and negatively affect their experience using a product. More options mean more cognitive effort, and more effort can sometimes mean more anxiety.
  • Principle of disclosure: Show just enough information to help people understand what kinds of information they’ll find as they dig deeper. By limiting the information they see at any one time, you allow your user to better absorb what they’re seeing. If users are interested in the information, they can dive deep into it by moving from preview to detailed information.
  • Principle of exemplars: Show examples of content when describing the content of the categories. For example, when browsing categories on eBay, each category is represented with an image of a product that falls into that category. This makes it easy for users to identify the category.
  • Principle of front doors: Assume at least half of the website’s visitors will come through some page other than the homepage. That means that every page should include some basic information so they know where they are. It also means every page should include at least top-level navigation so users will know what they can do next.
  • Principle of multiple classification: Multiple classification means that there should be different ways for your users to browse the content on your site. Different people are likely to use different methods for finding the information on your site. For example, some users may use search function to find the content while others may want to explore through browsing.
  • Principle of focused navigation: Focused navigation means that navigational menus should not be defined by where they appear, but rather by what they contain.
  • Principle of growth: Assume the content on the website will grow. The amount of content you have on a site today may be only a small fraction of what you’ll have tomorrow, next week, or next year. Make sure the website is scalable.

These principles are a great place to start when learning what it takes to create a solid Information Architecture for a project. While these principles are tailored to creating IA for a website, it’s possible to adapt them to other digital or even non-digital products

Hope you like this i will share some more this is collected from some websites about IA .

Hope this helps .


Thanks

Ashish


Hi Ashish,

Nice information, although really generic, not specifically related to OutSystems.

You might also want to give credit to the original author of article "A Beginner's Guide to Information Architecture for UX Designers".

I share the link to the original document here, so if people are interested to read more about Information Architecture.

Regards,

Daniel

Thanks AD and Daniel for the information!