Difference between Usability and Interaction design

dkcy · 11-23-2003, 03:15 AM

Questions
- Has anyone implemented interaction design before?
- How was it different from the field of usability in practical implementation?

I had done a very rough implementation of interaction design
- that is, creating an interaction document before coding the UI

It seems to work.

**LazyJim** · 11-23-2003, 04:14 AM

You mean you made it in plain unformatted HTML (with links and headings NOT <font> or graphics), and checked out how easy it is to use before adding the grahical interface and layout?

dkcy · 11-23-2003, 04:25 AM

nope, actually the project is not for web UI

- I just draw all the controls buttons and document how the user should interact, something like paper protoyping
my approach is kinda of trial and error.

btw, if you are planning it for web, how would u approach the UI design?
Perhaps i could hear from your own experience on how u implement

**LazyJim** · 11-23-2003, 05:51 AM

You first have to consider what the UI is an interface between.
The answer is its the interface between purpose of the site and the user.

So if you have designed your requirements and spec properly u'll know those two things intimately. (the later of the two is very hard in the context of the web!).

For example, in a project you've been working on you may have identified the primary user is "business executives and managers"; and the purpose of the site is "aid sales of our consistency service".

Now you know your interface must be...
clear, fast to use, show the sales-pitch part of the site quickly, easy access to contact info, professional and modern style.

Now I'll take each in turn...
Clear: good colour contrast, soft visuals, clear large fonts, obvious interaction feedback (mouseovers).
Fast to Use: quick to download, clearly labeled, uncluttered, common recognised interface, consistent throughout, "don't make me think".
show the sales-pitch part of the site quickly: make the whole site a sales pitch and/or guide the user to the right information.
easy access to contact info: clear button/link to the info, and clear info on the actual contact page, also the contact page should be devoted to only giving contact info.
professional and modern style: modern attractive but subdued visual appeal and graphics. (not flash as this would conflict with the other requirements).

dkcy · 11-23-2003, 06:21 PM

I find that a programmer find very difficult to design from specifications and requirements.

I have seen software turn up unusable although the project teams design it to specifications and requirements.

Quite often,Programmer has to double up as a UI designer as well. And mostly due to inexperience and lack of understanding in usability, the UI ends up unusable or require patches from costumers complaints.

In the case of interaction design, it apply the approaches of goal-directed design which is to achieve the user goals instead of the stakeholders

What do you think?

**LazyJim** · 11-24-2003, 04:19 AM

yes user-centered design is they best way - it is what the the stakeholders need anyway!

Johan007 · 01-05-2004, 08:38 AM

Quote:

Originally Posted by LazyJim

Clear: good colour contrast, soft visuals, clear large fonts, obvious interaction feedback (mouseovers).

Fast to Use: quick to download, clearly labeled, uncluttered, common recognised interface, consistent throughout, "don't make me think".

show the sales-pitch part of the site quickly: make the whole site a sales pitch and/or guide the user to the right information.

easy access to contact info: clear button/link to the info, and clear info on the actual contact page, also the contact page should be devoted to only giving contact info.

professional and modern style: modern attractive but subdued visual appeal and graphics. (not flash as this would conflict with the other requirements).

Yep thats good stuff I will agree.

Quote:

Originally Posted by LazyJim

yes user-centered design is they best way

... I think this means listen to the users needs and problems but dont confuce this with letting the user dectate what should be on the website!

Its good to write down (on paper or word processor) the primary goals and any secondary Goals.

This will help you write down the navigation hierarchy. This will get you into depth and breath debates. It all depends on how large your website content is and sort these into logical groups. You want your users to find information but not have to burrow down loads of levels of navigation often hiding the content BUT you don’t want to present them with loads of links on 1 page.

AcRoNym · 01-05-2004, 09:22 AM

scope doc

**LazyJim** · 01-05-2004, 09:34 AM

Acro you are very good and blurting out short phrases and single words aren't you?

**LazyJim** · 01-05-2004, 09:45 AM

Quote:

Originally Posted by Johan007

Quote:

Originally Posted by LazyJim

yes user-centered design is they best way

... I think this means listen to the users needs and problems but dont confuce this with letting the user dectate what should be on the website!

YES! haha I forgot to point out that!
The designer listens to the needs of all stakeholders and users, but creates a solution to satisfy the most important factors, not often how the user thinks they want it.
A design that focuses on helping the users, will have a much greater potential for reaching the stakeholders' goals.

Quote:

Originally Posted by Johan007

Its good to write down (on paper or word processor) the primary goals and any secondary Goals.

Yes, all Real Designers should do this.