Our friends in AC/DC saluted “those about to rock,” but nobody really salutes those about to build websites and information structures. That is, in my humble opinion, because not enough people think about information architecture. How many consumers of news–and by news I mean ALL information–spend time to think about how it reached them? The only thought some readers might have is that some “son of a bitch” who wrote the story has some bias or that they were paid off to write the story that way. (Yes, calls like that do come into newsrooms.) The average user–if there is such a being–spends about as much time thinking about information architecture as they do thinking about how the burger they ate for lunch made it onto the bun or how the electricity illuminating their bedroom lamps reaches there home. In fact, most people probably spend more time thinking about the bun question (no chuckling) and their lamp.
Since I’m a reforming newspaper guy, let’s use a newspaper operation as an example. How does news get to the reader?
Easy answer:
News happens.
Reporter writes story.
The end.
If only it could be that simple. (It can be that simple, but we’ll get to that later!) Newspapers are overly complex organizations that involve reporters, photographers, editors, advertising salespeople, graphics designers, accountants, telemarketers, delivery people, pressman, electricians, maintenance personnel … and plenty of other people who I’m a neglecting. (Apologies to those folks and a “thank you” for your hard work.) The point being that it takes an infrastructure of people, technology, equipment and more to bring news and information to the newsstand or doorstep. This structure has been developed over centuries, but many readers still don’t understand the mechanisms involved in the delivery of their newspaper.
With the relative youth of multi-media content on the web, that same average user–whomever he or she is–has less of an idea of how everything works. But it’s not just the user and consumer who is ignorant when it comes to making information flow online. Members of news organizations are often just as baffled and that is why “information architects sometimes find it necessary to justify their roles to managers” (Hoffman; 2006). Well, that is assuming that some organizations are forward thinkers enough to hire people whose job it is to plan this delivery and structure. Dollars are so tight in today’s media companies that “conceptual” jobs are a luxury. (Hoffman; 2006) If a person (or line on a spreadsheet) is not delivery physical, tangible product–be that copy, photos, ads, etc.–then her or she is viewed as an expensive luxury. Instead, as Hoffman mentions, information architects are individuals who carve out that role for themselves.
The reason people don’t spend time thinking about information architecture is because it–information-is always there. Did we value sites like Google back when we only knew of Infoseek? No, because we didn’t know Google existed so we couldn’t miss it. Think about how you feel when you finally get over a cold or, if it helps you relate better, a hangover. Think about what you get back after a power outage. While it is unlikely you spend hours or minutes pondering how medicines helped your body fought off illness or what needed to be done to the power grid to give life to your espresso machine or dvd players, the fact those things were missing did impact your life.
Just as news consumers don’t need to understand how story assignments are passed through a newsroom or how circulation audits are conducted or, well, most anything else other than they want news and the newspaper has it, bosses don’t need to understand everything information architects do … just the value of doing it. Wodke’s citing of Peter Merholz’s example of Wily Coyote (sic) trying to buy an anvil online is hilarious. It’s not just because the idea of Wile E. Coyote surfing ACME.com for an anvil, but it’s because the outcome of Mr. Coyote’s blueprinted plans remind me of how news how users view information architecture. The robust nature of multi-media content doesn’t allow us to set a snare trap and catch a reader … it’s just not that easy. Mr. Coyote never thinks that the Road Runner might take a different route or that he’ll stop before eating the birdseed or, well, anything else. It’s not that information providers have to consider every possibility, we just have to think that there’s more than one option and prepare for it (Wodke; 2001).
The Twinkie tagline used as the title for this entry sums up how people view information delivery. How did the information get there? They don’t, for the most part, care so long as it’s there. Do they need to know? Not really. Do we want them to know? Of course we do because we want them to understand how hard we labored to deliver this glorious information to them … that’s sarcasm, but it’s so true. With that said, I’m going to go grab a burger, likely one with cheese, and not give a thought to where it came from … too late.
Wodke, C. (2001). Defining information architecture deliverables. Boxes and Arrows.
Hoffman, A. (2006). Information architects: Web builders with a sales bent. Monster.com.