Why did Information Architecture lose its sheen?

It’s a pity that not many people talk about Information Architecture these days and that Information Architecture has lost its sheen. A friend recently pointed out that he is hearing the term after almost a decade.

In this information age that we are in, I believe it is more important than ever. The rate at which we get, consume, and process information and what we do with it has a huge impact on the overall User Experience.

So for anyone interested in getting better at UI and UX, I suggest getting a first-principles understanding of Information Design, Information Architecture, and the way the mind processes information (Cognition).

By, first principles, what I mean is to break it down to the first principles and build it grounds up. So start with the fundamental question. In the context of your design, ‘What is the Information’ and ‘How is the user processing that information?’

First principles thinking is about breaking down a problem statement into the basic elements by asking questions and creating solutions by combining basic elements in an innovative manner. First principles thinking removes all assumptions when looking for the solution of the problem. (Reference)

A text on an interface is information. So is an interaction between components and also the audio feedback that a user interaction results in.

All are information but of a different kind. The mind has to and will process each of these. Some it does consciously, and some subconsciously.

Every information processed, builds onto the perception about the product/service the user is using.

So why did IA lose its sheen?

The answer to this can perhaps be in the rise of 2 things.

Firstly, the rise of short-term courses. From introductory sessions to workshops to bootcamps. A lot of these courses are designed to give in bite sized learnings that are more associated with its immediate application. Information Architecture often takes a back seat. Not much time is spent in detail on it.

Secondly, it is to do with the rise of tools in the Design industry that put a lot of emphasis on building the craft and the tool that enabled you to do that. So there was the emphasis on the final output more than the process of getting there.

As a part of my work, I get to review multiple portfolios every week and I speak to many designers who are trying to break into product companies. When I ask about the process, the most common thing shown for Information Architecture is the task flow diagram and a basic site map.

Very few actually speak about other aspects of Information Architecture like user intent, user past experiences, information processing, etc.

What should we do now?

In a world of instant everything from food to feedback to gratification, we need to step back and often looker deeper into crafting meaningful experiences. One way of doing so is to re-emphasise on Information Architecture as a core function of every UX team.

This often requires to spend more time in thinking through in detail and in flows. It requires teams to be open to discussions and criticism beyond just the UI.

Most of the times, the Design Audits become a visual design check exercise. This needs to change.

Tools will come and go. The deeper understanding of Information Architecture will stay. Only when we spend enough time in thinking through the Information Architecture, we will truly be able to craft the experiences we aspire for.