It's probably overly simplistic, but I just use Web Designer usually.
I still think that anything 'architect' is a bit pretentious unless
you're putting up buildings. Interface Designer is a close second
for me, but I find that it doesn't come-off as well unless I'm
there in person to explain
I don't know that there's a hate-on in progress, but I do think that
there is a spirited debate, and a much-needed one.
My problem is with the term User Centered Design itself. I agree
that it's become over generalized. But every time I hear it, I ask
myself, As opposed to what?
In my work, I
Maybe I am being narrow-minded, but I just don't see these other
distinctions as being valid approaches. Stakeholder-centered,
tech-centered, etc. I really feel this is over-complicating things.
If you agree with what I said earlier about design defining what
you're trying to do and then dealing
This is an issue that I've struggled with for years now, and
obviously many of you have as well. I think the sheer number of job
titles and their overlap is testament to this confusion: IxD, IA,
HCI, Interface Designer, Usability Engineer, Web Designer, etc.
I'll preface by saying that I tend
I think I understand what you're talking about, but in general terms
I think it's just a task based rather than hierarchical navigation.
Using your example of a car site, you would ask, Do you want great
handling or durability? instead of asking Do you want Pirelli
Tires or Goodyear All Season
