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

[Anne Hjortshoj]

It's a bit of a paradox that while we concern ourselves with labeling 
items as a career choice, it's not really necessary that we all have the 
same job title in order to be employable. In my experience, it's a 
skillset, not a job title.

I think the  number one reason for the bi-annual (tri-annual? I think 
we're down from "monthly," anyway) recurrence of this discussion is that 
as IAs, we can't resist the urge to label absolutely everything.

Re-lurking,

Anne

Donna Maurer wrote:

>Maybe I'm the only one who thinks this - but I think there is value in 
>having a title (but not obsessing about it). It means that someone can 
>say "I need an IA" and I can say "hey, I'm an IA" and we are at least 
>talking about mostly the same thing.
>
>This doesn't mean I think certification etc is necessary, but labels are 
>used for communication and are important, and as IAs surely we 
>realise the importance of good labels...
>
>Donna
>
>On 27 Jun 2005 at 12:07, Alexander Johannesen wrote:
>
>  
>
>>On 6/27/05, Listera <listera at rcn.com> wrote:
>>    
>>
>>>It's also entirely possible to deliver the *work* of an IA, without
>>>obsessing about the *title.*
>>>      
>>>
>>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.
>>
>>    
>>