[Sigia-l] So, how did you become a [Information Architect|UsabilityEngineer|Interface Designer|etc.]?

[Ted Han]

On 6/26/05, Alexander Johannesen <alexander.johannesen at gmail.com> wrote:
> This whole thing has made me wonder what exacly is it that we *value*
> in all the things we do; the title, or the work? And here's the thing;
> why the *hell* does it matter? An information architect architects
> information. Want a title? Get a doctorate or a PhD.

I phrased my initial question in an attempt to avoid this particular
confrontation.  I'm not interested in which is more important in IA, i
think it's somewhat immaterial.  After all i think everyone on the
list agrees that it's members are talking about something of substance
and that they have jobs with titles which relate to this matter of
substance.  Whether it's the chicken or the egg which is paramount
doesn't help me in the slightest.  And yes, if i wanted a title, i
would have gone straight into grad school.  ::shrugs::

> My story in coming to IA is long and bouncy. I'm not an IA by wanting
> to solve a given problem in certain fields accompanied by a long hard
> education with letters added to my title and such. It came through
> seeing the need and a want to do things better.

I think people in the "real" world really do a disservice to academia
with statements like this.  The politics, business, and all manner of
other things are just as full of meaningless titles and nomenclature. 
Good academics are in their fields just as you put it, by "seeing the
need and a want to do things better."

Anyway, thanks for the note, if there are more specifics you'd like to
relate, i'd be interested to listen :)

-T