Re: [IxDA Discuss] Displaying multiple filters on a page

2010-02-12 Thread Ari Tenhunen
You are right when trying to keep the search function as simple an
elegant as possible. But we need to think about the user, what is the
purpose if this function to her/him?

I think a text search input field is a must. People should be able
make searches based on the information contained in the document
(content, introduction, author, title, filename, keyword etc.). I
think this is primary. Using categories and file types as only search
options may make it more difficult for the user to find what he/she is
looking for especially if there is a high volume of documents. 

This is not primarily an aesthetic issue, it%u2019s a usability
issue. 

Ari Tenhunen
www.nemeo.fi


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49338



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] What is a subset of the other?

2010-02-08 Thread Ari Tenhunen
This is interesting topic. And the point of view adopted by your
organization as a preferred one seems to define the shape of the
organization. So this is not just an academic question to you.

UX is a wider concept and involves things like content, aesthetics
and such in addition to usability. I think UX design is about
striving to generate desired impact to user%u2019s emotions and
memory by various means. IxD concentrates on usability and how the
system responds to user%u2019s actions. And it sure affects the
user%u2019s experience. I think TIxD and UX design complement each
other. They are more like sisters than mother and daughter. 

Avoid over-conceptualizing this. In your organization, subduing IxD
to UX design might be as bad as subduing UX Design to IxD.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49125



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Editing of profile details

2010-01-27 Thread Ari Tenhunen
Good question

Maybe there is not one and only correct answer to this question. I
think the main thing is maintaining the consistency of the methods.
Similar operations should always look and feel the same to the user
so that he can utilize his prior experience and knowledge. 

You can introduce new use methods if they simplify the user
experience. But you cannot underestimate the users ability to
understand the meaning of the interface. Sometimes simplifying may
make things worse because you have to unlearn the old complicated
methods. 

You might have to explain some methods explicitly.

It also depends on whether the service is for one-time users or for
recurring use. You can teach new tricks (not too complicated) to
regular users.

You need to step in the shoes of the weakest user (if you deem
him/her important). Specifying user personas helps. Would your granny
be able to use it? How would you descripe the main example users?

Should the user make profile updates in pop-up or in the same place?
I prefer editing things in the same place. It is natural. But I still
use both approaches. I prefer making content updates directly in the
content. Profile details can be updated in a different page or pop-up
window or layer because this data is often displayed in several places
and profile data often contains details and information which is not
shown to all user groups. Still it can be a good idea to enable
updating someprofile data directly in the actual place where it is
displayed.

You need to make the editing state visible to user so that he/she
always knows what exactly is happening and what is he/she required to
do.

I also think it is important to minimize the stages in the processes.
And if the operation has several steps, user should be told how many
steps is there going to be, what do each step mean, in which stage of
the process he is currently, and get a confirmation of succesful data
update in the end.

Whatever approach you choose - be consistent, do not assume that all
users automatically understand what to do and in which order.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=48669



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help