[Sigia-l] Building an Information Architecture Team

[Russ Unger]

> Ziya wrote:
> 
> > A business analyst, a database architect, a librarian, a
> > statistician, an interface designer, a usability 'engineer' 
> > or those with even fancier titles such as user experience or 
> > interaction designers would normally contribute in one 
> > fashion or another to the general architecture of a site. BUT 
> > they would hardly be pleased to be included in what you call 
> > an "information architecture team." They all have their 
> > titles and fiefdoms to cultivate.
> 
> True and oh, so sad. And how many aspects of methodologies, 
> organizational structure and compensation schemes work to 
> further silo the "team" into their own sub-specialties and fiefdoms?

Isn't all that a bit harsh?  Certainly, experience may show that, but
the growing acceptance--if not need--for Information Architecture would
really dictate that we should be more open and accepting of people from
other backgrounds, since I'm guessing that a lot of us have come from
any of the titles or backgrounds listed above.

It would seem to me that the best way to affect this acceptance would to
be accepting of others as well.

Don't get me wrong, though, I certainly understand where this stems from
and have seen it myself, but I've also been really proud and pleased to
have been the part of an "information architecture team".

Sorry for the intrusion; just my $.02.

Russ

---
[This E-mail scanned for viruses]