Those who practice user-centered design might say that Information Architecture (IA) is all about organizing information in a way that is most useful and meaningful to end-users. Indeed that’s a big part of it, but certainly not all. If that were really all there was to it, we could just call it Information Organization.
But Architecture implies more; it implies both art and science, both process and product. It implies planning, design, and construction. It implies a number of different components and systems integrated to create one cohesive whole. It’s a multi-faceted thing wherein we find multiple forces pushing and pulling on one another. What’s needed by the business and what’s viable? What’s wanted by the users? What are the capabilities and constraints of the technology platform? Of the organization? Its teams and individuals? A great IA must consider and balance all of these forces.
I did my first job as an IA on a project to build a new employee portal for a package distribution company. The Project Manager at IBM said I’d be filling a role called “Information Architect”. Now, this was a very large and complex project with multiple C-level stakeholders and very ambitious goals. And it was a very big company – a global company. 400,000 souls – 90,000 of which would certainly be registered just after go-live.
I remember thinking, Geeze, how many people is that, really? If you stacked 90,000 employees feet on shoulders, they’d extend at least 85 miles or more. That’s Mount Everest… 15 times. And then I thought about the lifetime of the portal and how many more people might interact with it over the years to come. I thought to myself, “Self, where do you even start with something like this?” And then it occurred to me to start by seeking an answer to the secret question that was weighing heavy on my mind…
What the hell is an Information Architect, anyway?
Nine years, several projects, countless sleepless nights, a few death marches, and at least ten thousand Google searches later, I’m still chewing on that question. My quest has taken me through library and information science, business strategy, governance, creative design, usability, graph and network theory, brain science, game theory, software engineering, philosophy, and even down into the nucleus of a cell where all those little A’s, G’s, C’s and T’s form the source code for life itself.
What is an Information Architect? What is Information Architecture? What is Information?
It’s like a Zen Kōan. The more I grasp for the answer, the more it seems to squeeze through my fingers like water. The more questions I answer, the more questions arise. It’s mind bending, but maybe it’s not supposed to be. Maybe it’s just supposed to be a title on a business card for a guy that can help you build a website. And sure – it has been that for me, but it’s been much more. And sure, it’s been a long while since I was thrown into the fire of my first portal project and branded an IA. Yet every day still brings a new lesson. Every day – a new question.
What is an Information Architect?
I’m not sure I have a good answer yet, but I have some interesting stories to tell and I figure I bess get to tellin’ because maybe… just maybe… there’s someone out there who just got thrown into the fire and is typing the same question into Google now.
Howdy friend. These are the IA Files.