[Sigia-l] explaining IA

[Jon Lebkowsky]

I can relate to the evolving explanation thing. I had avoided using
terms like "information architecture" and "user experience" until
recently, because I was focusing more on the broader development work
of our small consulting company. We didn't really think potential
clients (in our case mostly small to medium organizations) would get
those terms as part of our elevator speech or as line items on the
budget for site development.  I recently had an epiphany about that,
though. I decided that clarifying the meaning and value of IA could
have a very positive impact on project communications going forward.
So far that seems to be the case.

~ Jon

> -----Original Message-----
> From: sigia-l-bounces at asis.org 
> [mailto:sigia-l-bounces at asis.org] On Behalf Of David Malouf
> Sent: Wednesday, February 14, 2007 7:55 AM
> To: sigia-l at asis.org
> Subject: Re: [Sigia-l] explaining IA
> 
> Now, depending on your audience, what is the difference between:
> IA, Business Analysis, System Architect, User Experience 
> Architect, User Interface Designer, Usability Engineer and 
> Interaction Design?
> (to name a few).
> 
> Now I could see how this question may be irrelevant to your 
> needs right now, but just since this is a discussion list and all
...
> 
> It does sound like your phrasing below could be any of that. 
> Nothing particular very "I" in the IA definition you propose.
> 
> -- dave

Jon Lebkowsky
jon.lebkowsky at gmail.com

Consulting:
http://weblogsky.com/consulting-social.html

* Partner, Polycot Consulting: http://polycot.com
  jonl at polycot.com
* Blog: http://weblogsky.com