Information Architecture


12
Nov 09

Use link titles as a check on your architecture decisions

Recently at work, there was a discussion about link titles, their utility, when to use them, when not to and so forth. Link titles are those attributes you insert into a link tag that helps set expectations for users of where a link will take them. Conceptually, they’re easy to understand and rationalize. The hard part is actually writing them. I’m certainly guilty of writing banal descriptions that would make you wonder why I included one at all. But since no one ever calls you on them, it’s easy to let them slide. But over the years, I’ve come to realize that the seeming chore of title tags is actually an excellent check on your site’s information architecture. Let me explain.

Since title tags are an exercise in telling people what they’ll find behind a link before they actually go there, the act of writing it requires you to justify the relevance of the link in the first place. If you’re at Apple’s website on the Macbook page, you might see a link to their Macbook Pro page. Makes logical sense, right? If you’re interested in a Macbook, you might be interested in stepping up to a Pro model. A title tag might say “Step up to a Macbook Pro for added performance, storage, memory and more.” The sentence establishes relevance and a reason why you should click or not click. Job done, move on.

Let’s take another example, however. Let’s say you’re on a university’s annual report site, on any page. There’s a global link to the chancellor’s site. You write a link title that says… what? “Go to the website for Chancellor so and so.” No, that’s too obvious. “Get information about Chancellor so and so.” No, that’s not relevant to the annual report as a whole. “Get Chancellor so and so’s impressions on the year’s events.” No, if that information existed, it would be part of the annual report site itself.

The above reasoning hints at the utility of link titles. Writing them forces you to double check your architecture. Why does a link exist on this particular page or in the global nav? Is it relevant to include here versus over there? How does the inclusion of this link in this area on this page help the visitor accomplish their goals or further their aims?

All of these questions should have been asked early in the process, but things slip through or circumstances change. Writing link titles help verify that you’re user experience goals are kept intact and on track. Try it, it works.


9
Apr 09

There’s A Happy Medium Between Centralization & Decentralization

One of my main points of advice for higher ed websites is the idea that operationally, a decentralized management approach to the web does not work well. The opposite–centralization–does. But that doesn’t mean some aspects to a decentralized approach can’t or shouldn’t be employed. It just shouldn’t be the foundation for how to manage the global operation of the site. That spells trouble.

So where does decentralization make sense? The obvious answer is content. Higher ed sites are large, if not huge, relative to many websites and the thought of centralizing that amount of content into a few hands doesn’t seem practical. The sheer workload would jeopardize the distribution of time sensitive information. Plus, no content person wants to work in a sweat shop environment were quality takes a backseat to simply getting the work out. And beyond even those practical concerns, will a content person be as passionate about every subject that comes across their desk as the people who live and breathe it?For those reasons, content ought to be unleashed. Continue reading →


3
Jan 09

What Higher Ed Sites Could Learn From Barack Obama

One of the main arguments I hear against my mantra of centrally maintained websites for higher ed is that a decentralized approach allows academic departments the flexibility to market their programs based on their students’ specific characteristics and needs. Academic department’s tell me that their particular students are special and different from all other departments’ students. Therefore, their website has to have a custom design in order to stand out. Continue reading →


31
Dec 08

How To Turn Around A Problematic Site

There’s no shortage of criticism about the University of Denver website. As its web designer, I get grief about it from colleagues, students, parents and friends. Even I think its pretty bad, but the challenge to improve it is enticing. When I accepted my job a year ago, I didn’t fully appreciate how ingrained the status quo was in terms of the existing website. I figured I could ride into town, inject my outsider’s perspective and years of experience and get things turned around. Well, as you might imagine, I was naive. It’s been difficult, time consuming and just plain draining to steer the website toward a new course — one that, to me, is a slam dunk generally speaking. That said, I wanted to outline the steps I saw that needed to be accomplished when I joined the team in order to turn criticism into praise. It’s a short list and could use more detail, but here are the major milestones. Continue reading →


24
Dec 08

The Step Before Defining A Website’s Goals

“Redesign the (fill in the blank)’s website,” upper management directs you. “No problem,” you obligingly respond, “I’ll get right on it.” But then what? How do you undertake something seemingly innocuous, but in reality big, complex and fraught with politics? Continue reading →