[Sigia-l] Building an Information Architecture Team

[Brett-Luxaco]

Not too sure why you wouldn't see a team of IAs on a project. In my
experience, more than one often gets better results. I have worked on a 3
person IA team last summer, and yes we all had different sections to work
on, but we often came together to discuss through issues and potential
solutions and in the end gave the client better options than if one person
tried to tackle it themselves.

Brett Taylor

----- Original Message ----- 
From: <david_fiorito at vanguard.com>
To: "SIGIA-L" <sigia-l at asis.org>
Cc: <lquiroga at hawaii.edu>
Sent: Tuesday, December 09, 2003 12:20 PM
Subject: Re: [Sigia-l] Building an Information Architecture Team


> Hmmm.  Sitting here in the real world I am a member of an IA team made up
> of *gasp* Information Architects.
>
> All sarcasm aside - I would be more than happy to answer questions
> off-list but I wanted to reply to the list to show everyone that IA teams
> are not just a mythical beast roaming somewhere in the imaginations of a
> few authors.  In fact we have multiple IA teams here at Vanguard - in the
> real world.
>
> Wenjie - feel free to email me with any questions you might have.
>
> Cheers,
>
> Dave Fiorito
>
>
>
>
>
>
> Listera <listera at rcn.com>
> Sent by: sigia-l-admin at asis.org
> 12/09/2003 02:29 AM
>
>
>         To:     SIGIA-L <sigia-l at asis.org>
>         cc:     <lquiroga at hawaii.edu>, (bcc: David Fiorito/IT/VGI)
>         Subject:        Re: [Sigia-l] Building an Information Architecture
Team
>
>
>
>
>
> "Wenjie Qin" wrote:
>
> > I couldnot find any IA team in the real world on the web.
>
> I don't know much about the book you mentioned, but in the real world of
> today's economy it's rare in the extreme to find *multiple* IAs working on
> one project who would constitute an information architecture *team.*
>
> Since the definition of IA is very contentious for a variety of reasons,
> it's also difficult to pin down who would be included in an IA team if you
> could realistically form one.
>
> 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.
>
> ----
> Ziya
>
> Any problem that requires walking on water
> as a solution is a problem ill-stated.
>
> ------------
> When replying, please *trim your post* as much as possible.
> *Plain text, please; NO Attachments
>
> Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
> ________________________________________
> Sigia-l mailing list -- post to: Sigia-l at asis.org
> Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
>
>
>
> ------------
> When replying, please *trim your post* as much as possible.
> *Plain text, please; NO Attachments
>
> Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
> ________________________________________
> Sigia-l mailing list -- post to: Sigia-l at asis.org
> Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
>