Here’s an excellent article written up at the ASIS&T Bulletin, by some talented and thoughtful folks in Europe (namely Andrea Resmini, Katriina Byström and Dorte Madsen). I’ll quote the end of the piece at length.
Even if someone’s ideas about information architecture are mind-boggling, if they do not discuss them in public, embody them in some communicable artifact and get them to be influential, they are moot. This reality is the main reason behind the upcoming peer-reviewed scientific Journal of Information Architecture, due in Spring 2009. For the discipline to mature, the community needs a corpus, a defining body of knowledge, not a definition.
No doubt this approach may be seen as fuzzy, uncertain and highly controversial in places. Political, even biased. But again, some overlapping and uncertainty and controversy will always be there: Is the Eiffel Tower architecture or engineering? The answer is that it depends on whom you ask, and why you ask. And did the people who built it consider themselves doing architecture, engineering or what? The elephant is a mighty complex animal, as the blind men in the old Indian story can tell you, and when we look closer, things usually get complex.
The IA community does not need to agree on a “definition” because there is more to do. An analytical approach must be taken on the way the community sees itself, with some critical thinking and some historical perspective. The community needs to grow roots. We hope the Journal will help along the way.
I especially like the Eiffel tower example. And putting a stake in the ground saying let’s not worry about a definition, we have more work to do. This is the sort of mature thinking we need at the “discipline” level, where people can focus on the academic, theoretical framework that helps evolve what the bulk of IA folk do at the “practice” level. (Of course, that flow works in the other direction too!)