Scalloped information architecture could be a thing

This article is day 4 of a 31 day series. A mash-up of the Inktober 2022 prompt list and UX terminology. Read more about the challenge here.

Day 4 | Inktober prompt: Scallop | UX Term: Information Architecture

I feel like I missed my window for learning about scallops. I just spent twenty minutes scanning (yes research time is limited with a daily article project) hoping that something would pop out that I could relate to information architecture. And all that happened is that now I’m not even sure if scallops are a real thing. Every article I found seems to use way too many unfamiliar words and reference seemingly impossible structures, somehow housed within a simple shell. I had no idea.

Oh.

Okay, so yeah… scallops are just like information architecture.

What is Information Architecture?

There are entire books written on information architecture. Like, big books. I have multiple bookmarks in my copy of Information Architecture for the World Wide Web by Louis Rosenfeld & Peter Morville that sits next to my desk. Yes, it’s a twenty year old book, but it still packs a punch. Even still, it’s not exactly one of those that you sit down and read cover to cover. Well, maybe you do. I don’t know your life. But if you’re reading this, I’m guessing not.

What it is, is what it sounds like it is. You’re familiar with information right? And you’ve probably heard of architecture. But what most don’t realize, when they try to simplify it by saying it’s the structure of information on a site, is that they’re about to get poked in the eye by someone who knows better if they keep talking like that.

Don’t believe me? Ask an architect if they just build structures. (I usually defer to google in these situations… like any time my daughter doesn’t believe some amazing fact I just shared with her.)

Me: “Hey google, what do architects do?”

Google: (do the voice, you know you want to) “According to targetjobs.co.uk, architects create designs for new construction projects, alterations and redevelopments. They use their specialist construction knowledge and high-level drawing skills to design buildings that are functional, safe, sustainable and aesthetically pleasing.”

If you start to think of information architecture with this level of nuance then you’re closer to grasping what exactly it is. Which is most definitely more than the sum of its parts.

Why is it important to UX?

In UX we’re looking to solve a problem for our users and address their needs. The form this typically takes is providing information. Or as the kids call it these days “content”. But what good is that content if you can’t find it? Or if you can only find part of it.

It’s like this: aaeeffhiiiilllmnnoorrsssTtuuy

Instead of this: This is really useful information.

See why structure matters?

Takeaway

Focusing on information architecture as you create your site will give you the foundation upon which to build all of your amazing content and ensure that people actually get to enjoy it. Focus on understanding the needs of your users, and building your structure to match. If you’re overwhelmed by the level of expertise needed to do this really well, you’re not alone. Information architecture is heavy duty, but worth every cent. If you ever have doubts about that, just remember the time you had your uncle Bob build your add-on. Then call a professional. And ask them how they feel about scalloped archways.