[Sigia-l] "Who Really Turns Off JavaScript?"

[Stewart Dean]

On 15/11/05 4:29 pm, "Skot Nelson" <skot at penguinstorm.com> wrote:

> 
> On Nov-15-2005, at 6:10 AM, Stewart Dean wrote:
> 
>> By the sounds of it you're getting to close to the technology. As an
>> information architect I feel it's vital to keep a few steps back
>> from the
>> technology
> 
> That's a pretty pure definition of information architect, I think. I
> certainly would consider, for example, the appearance of a pop-up
> dialog box in a user's face would definitely fit into my definition
> of it, and this would mean worrying about whether or not JavaScript
> is being implemented.

It would? I don't think this is true. Let me explain why. A pop up is a
behavior of the user interface. It is what happens. From a user experience
point of view it's part of our job to say if we want that to happen or not
and what happens when it does.

What you've done is jump from what happens to how it happens. I'm saying
that you don't need to worry about that and, if anything, how a pop up box
appears is a distraction from creating the user experience.

It's not so much a pure definition, just how things have evolved for me over
the years. 

> But I suppose it could be labeled "Interaction Design"
> instead....maybe. I think there's quite a bit of crossover between
> those to labels in any case.

I say forget the technology for at least most of the time. My view is
everything is technically possible given enough time and money and that any
user experience can be implemented in many different ways so worrying about
Javascript is pointless unless you're going to be the one doing the
programming.

I'm saying being distanced from the technology leads to better user
experience as you make less compromises and think what you want to happen.
As soon as you start thinking 'and then we can have a Java app there, a bit
of flash there and we can use Ajax to update that bit' you're not thinking
like a interaction designer or information architect but you're thinking
like a implimentor/engineer and your priority is no longer with the user
experience.

Engineers and implementers don't create bad user experiences on purpose, it
just arises because of their focus. The same is true if you focus on the
business, the visual design or anything else over user experience. It's just
human nature. My view is that if you have to do two roles then you need to
effectively hand the job over to yourself, changing hats and changing your
mindset.

Stewart Dean