Differnce between user interface andinteractiondesign?

27 Jan 2008 - 12:22am
6 years ago
2 replies
479 reads
Becubed
2004

> So in that sense they are a truly UI designer.

I dunno, that sounds like a visual designer to me -- which, in my mind, is someone who's able to skillfully adapt the craft of graphic design for an online medium.

Comments

28 Jan 2008 - 11:09am
Pierre Roberge
2005

At my current job, I have worked with an interface designer and the way
he approached the design of the B2B we are building is from the
developers' perspective. He looked at the data-model and the functions
the developers developed and put all those fields and functions on
screens grouping them based on their nature (all the customer
information on one screen, all the policy information on one screen,
...). Then he created navigation to go from screen to screen. He used
generic standards he found on useit.com to guide his design and always
tried to make sure that the application was easy to use for a first-time
user.

He did not looked at the business process, nor talked to the users. So,
his design was not inflected in any way causing the users to complain
about having to navigate from screen to screen just to get a complete
mental picture of a customer or to complete their sales process. Also
since he did not research users, he catered to first-time users only
which was not optimal since people are using the system all day along to
sell insurance.

The end result was a generic software that did not reflect how people
think about the work and perform their work. His screens were
consistent, buttons were in the same place from screen to screen, he
carefully chose the font size and screen resolution based on statistics
he found on the web.

To me, the difference between user interface and interaction design is
the process. Both of us, decide where to place widgets on the screen,
how to navigate from screen to screen. IxDers start with the users
(top) and design layout and behavior (functionality) to serve real
people. Interface Designers start from the bottom up. Since they don't
analyze users, the business process nor meet the takeholders, they need
to wait for business analysts or programmers to tell them which fields
and functionality the system will have so they can start spreading
widgets on screens based on generic guidelines.

Of course, this is only anecdotal. :)

Pierre Roberge
User Experience Designer - Business Analyst
etfs

----------
etfs inc. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon this information by
persons or entities other than the intended recipient, is prohibited. If
you have received this in error, please contact the sender and delete
the material from any computer. Unless otherwise stated, opinions
expressed in this e-mail are those of the author and are not endorsed
by the author's employer.

etfs inc. L'information transmise ne s'adresse qu'au particulier ou a
l'organisme a qui il est dirige. Il peut contenir des renseignements de
nature privilegiee et/ou confidentielle . Si le lecteur de ce message
n'est pas le destinataire vise, ni l'employe ou le mandataire charge de
la livraison au destinataire vise, il est par la presente avise que
toute dissemination, distribution ou transcription de cette
communication est strictement interdite. Si vous avez recu la presente
communication par erreur, veuillez nous en aviser immediatement par
courriel et detruire le document de tout ordinateur le contenant. A
moins d'avis contraire, toute opinion exprimee dans le present courriel
est celle de son auteur et n'est pas endossee par l'employeur de la
personne qui l'exprime.

29 Jan 2008 - 5:31am
Adrian Howard
2005

On 28 Jan 2008, at 16:09, Pierre Roberge wrote:

> At my current job, I have worked with an interface designer and the
> way
> he approached the design of the B2B we are building is from the
> developers' perspective. He looked at the data-model and the
> functions
> the developers developed and put all those fields and functions on
> screens grouping them based on their nature (all the customer
> information on one screen, all the policy information on one screen,
[snip]

Of course if the underlying data-model and the functions don't map
well to the business processes and the way the user needs to interact
with the system the designer is pretty much doomed anyway - the
intervention needed to happen earlier...

Cheers,

Adrian

Syndicate content Get the feed