information architecture

You are currently browsing articles tagged information architecture.

There’s a lot of animated chatter among some of my favorite journalists over the redesign of their publication’s site. Last week, the Atlantic Monthly rolled out what appears to the casual reader as a slight update of the IA, along with some major changes to the way that blogs are integrated. Reader reaction was anything but casual; anger and suspicion seemed to be the most common reader emotions, shared, at least in part, by the writers. The Washington Post’s Ezra Klein nails the goal of the redesign, “Seems like a bet to re-center the Web site around the Atlantic as an institution rather than leaving it as a web hosting service for a couple of bloggers.” Which seems smart, actually.

The Atlantic online redesignThis clustercuss is the redesign. (I can’t find a picture of the “before,” but it wasn’t really too different, to the casual observer).

The real problem: The redesign isn’t radical enough.

It simply shifted content around — a sure-fire bet to piss off regular readers. The redesign doesn’t address bigger problems around findability, readability, navigability, whatever you want to call a lingering sense of not being able to get around easily. It also breaks from a common blog convention: homepages that includes lengthy content for each post (UPDATE: they’ve changed this). The biggest change is that they’ve moved away from individual blogs as linear, ever-expanding solo narratives, which I think is interesting. What they’re moving toward is less clear.

According to spirited commentary by the Atlantic writers, the redesign was driven by the arcane calculus of advertising. I won’t pretend to know how online ad placement works in a place like The Atlantic, but what I do know is that someone told them to spread their fresh content around, and it’s kinda half-spread.

I am a big Atlantic reader. I subscribe to the print edition, and I regularly read three of its bloggers — Ta-Nehisi Coates, James Fallows and Andrew Sullivan. I subscribe to their feeds, so I don’t go to theatlantic.com unless I want to comment on Coates’ blog, or read comments, which means I’ll head there a couple of times a week, but when I get there I’ll be deeply immersed in a thread.

To me, the true opportunity was to leverage the sprawling, smart conversations that these writers continually create — to create a sort of salon among the readers and writers. To Klein’s point above, you’d think a virtual salon would be exactly the kind of thing that would “re-center” the brand. Breaking out of the conventional blog model is a reasonable first step. Blogs are long threads, and maintaining individual threads needlessly inhibits wider-scale conversation. So they’ve taken that half-step away from threads (which are a helpful organizing principle for readers), but the salon is nowhere in sight. And this is a problem.

I’ve followed Khoi Vinh’s excellent blog, Subtraction, for a long time. A couple of years ago, he became the Design Director of the New York Times website, and in the meantime the site has really changed, for the better, mostly, I’d say. This week he’s doing a Q&A about his work, the NYT, design, and all of that.

As I’ve always been curious about what he does in his role, and the structure of the NYT.com UX department, I was glad to see that someone went there right off the bat:

As the design director, my responsibility is to oversee the creative aspects of these continual improvements. Each one is a project of its own with some range in scope, from very short and discrete to long and drawn out over many months. And each project requires one or more of the members on my team: information architects (who are charged with organizing the features and the flow of information so that people can make use of them most intuitively), design technologists (who do the actual coding of many of these sites, using HTML, CSS, JavaScript, Flash, etc.) and/or visual designers (who handle the overall look and feel, including layout, typography, color, proportion, etc.).

You could say that all put together, the final product of our efforts is the user experience, or the sum total of the content and the framework as it’s used by visitors to the site. Of course, it’s not true that my design group is the only team responsible for creating this experience; it’s really the result of contributions across the board, from editors and reporters to project managers and software engineers and many more.

More here.