Nobody understands information architecture

It’s the other public face of information science, besides librarianship. Except that everybody knows what a librarian is, even if they’re usually wrong.

And nobody knows what an information architect is. Though we did get our own parody Richard Scarry Information architect.

![[Pasted image 20260219140707.png]]

I would say that I’ve been mad about this for a decade, except that honestly I’m just happy to be included. Mostly IA isn’t much of a public face, because the public doesn’t notice IA unless they’re mad at it. So a public face for a small part of the world, usually people who work on websites.

It’s not like this invisibility is shocking. Like Bates herself points out in “The Invisible Substrate of Information Science,”

“most people outside our field do not realize that there is a content to the study of form and organization. I believe that this is one of the chief reasons our field is commonly thought to have no “there” there. The average person, whether Ph.D. scholar or high school graduate, never notices the structure that organizes their information, because they are so caught up in absorbing and relating to the content.” And, in fairness to them, they are not interested in the structure. We are interested in the structure.”

So, this is a problem IA has inherited from information science. It’s a public face, but sort of on the DL. It’s kind of on a need-to know basis. 

What IA is, is sort of a secret.

This is not unique to us. In his play, The Doctor’s Dilemma, George Bernard Shaw wrote, “Every profession is a conspiracy against the laity.” A lot of the conversations about credentialism in libraries is a conversation about the nature of this conspiracy. Who are we keeping out by insisting on degrees? By maintaining the difference between library staff and librarians?

At least in IA, we haven’t established greenbelts of training and credentials, it’s something else. Maybe just knowing it exists. 

Welcome to the conspiracy. 

Did the conspiracy start at Xerox PARC?

In the late 1960s, Xerox decided to create a new research division in California. It was physically and spiritually miles away from Xerox’s corporate headquarters and existing research laboratory. This new research center was supposed to invent brand new technologies. 

And invent they did, work here led to laser printing, ethernet, object-oriented programming, the whole idea of a GUI (instead of a computer controlled through typing), the metaphor of the desktop, the mouse, and a lot of other stuff about semiconductors that I don’t understand. It was a place to try things. 

But what interests me the most about it was how it started. In 1969, the president of Xerox, Peter McColough, declared that Xerox would control “the architecture of information.” 

Later, one PARC engineer said, “It was a great phrase, because no one knew exactly what it meant. So there were quite a few interesting things you could do and simply cite that as the justification.’” (Hiltzik, 2000)

So here’s the thing: I think we’re doing the same thing. I’m in this picture and I don’t like it. I strongly suspect that nobody knows exactly what information architecture is, and we’ve grabbed onto a good phrase, that would let us make it up, to get jobs doing things we like to do. 

This isn’t just us. The opening paragraph of a 1992 paper, “What do software architects really do?” opens with an anecdote:

“Mr. Beck, what is software  architecture?”   “Software architecture?”  replied Kent, “well, it is what  software architects do.”   “So then, what is an  architect?”   “Hmm, ‘software architect’  it’s a new pompous title that programmers demand to  have on their business cards  to justify their sumptuous emoluments.” (Kruchten, 2008)1 1 Idk if anyone who uses the phrase “sumptuous emoluments” should talk about pomposity, glass houses etc.

So maybe nobody knows. Sobering, considering this is my livelihood, but that can’t be right. Because there’s not nothing here. Right? Information architecture is indistinct, but information architects are not. We have meetups. We have a Richard Scarry parody cartoon! We know who we are. 

And I might posit that we are a group of people all bothered by the same things.  We might not agree on what it is, but we know why it’s needed. So never mind with the what. Instead, I would ask, “Why information architecture?”

References

Bates, Marcia. 1999. “ The Invisible Substrate of Information Science. ” Journal of the American Society for Information Science and Technology 50 (12): 1043–50. https://doi.org/10.1002/(SICI)1097-4571(1999)50:12%253C1043::AID-ASI1%253E3.0.CO;2-X.

Kruchten, P. (2008). What do software architects really do? Journal of Systems and Software, 81(12), 2413–2416. https://doi.org/10.1016/j.jss.2008.08.025