Information Architect

[Jim Barrow]

The original post had nothing to do with educating people.  Information Architects seem to have been around for a while.  I just wanted to know how the roles and responsibilities of an IA matched up with that of a TW.

>From: Gene Kim-Eng <techwr at genek.com>
>Date: 2007/12/21 Fri PM 03:37:34 CST
>To: techwr-l at lists.techwr-l.com
>Subject: Re: Information Architect

>Well, there are some people who hear "engineer"
>and think "Casey Jones."
>
>Trying to respond to peoples' ignorance about what
>"technical writer" means as opposed to "data entry
>clerk" by inventing a new title is futile.  Unless you
>educate people about what you do, a few years
>down the line people will hear "information
>architect" or "technical communicator" and just
>think "data entry clerk with delusions of grandeur."
>
>Gene Kim-Eng
>
>
>"Jim Barrow" <vrfour at verizon.net> wrote in message news:mailman.5.1198247506.2537.techwr-l at lists.techwr-l.com...
>> Yes, and not necessarily.  Most of the threads posted here have dealt with calling oneself a technical writer, which may lead some 
>> people to think that we are nothing more than data entry clerks, rather than skilled writers, analysts, GUI experts, etc.  In 
>> trying to create a job title that encompasses the depth and breadth of what we do, Technical Communicator or Information Architect 
>> was suggested.  In this thread I'm pointing out that IA has seemed to gain traction as someone who does the things we have been 
>> quietly doing all these years.