Or, more specifically, "What is the role of an Information Architect?"

A lot of people have been trying to answer this question lately. Whole books have been devoted to the topic. Still, I've found one of the oldest books in the genre, the Mythical Man Month, to give the best insights of what an information architect is and isn't. One reason I prefer this book over its more recent siblings is that it addresses the role of architect alongside the other roles, without a bias towards architect, strategist, implementer, or user. Another is that, having been written 25 years ago, it isn't trapped up in the current issues of the web. While some might see this as giving the book less relevance, I find that it provides less distraction, helping separate the core of information architecture from the idiosyncrasies of web development.

I'm still working on my definition of the role of information architect, culling from these sources and my own experiences, and I'll be posting it once it's complete.