Recent Discussions

JOB: Interaction Designer, London

We're looking for an Interaction Designer to join us as soon as possible,
to design PC and mobile software for Nokia and other clients.

Candidates will have solid interaction design skills and be great at both
coming up with ideas and refining them to specification-level detail.

The position is initially a two month contract, potentially leading to
permanent. It is based in central London with some travel to Europe.

CFP: TUXS 2004 (Toronto User Experience Summit)

TUXS 2004 CALL FOR SUBMISSIONS

The Toronto User eXperience Summit (TUXS) 2004 is a multi-disciplinary and
trans-industry gathering of user interface designers, software developers,
graphic designers, human factors practitioners, engineers, industrial
designers, teachers, information architects, researchers, and professionals
in other areas seeking to gain an understanding of how to better craft and
mange the interaction between people and any kind of designed environment.

TUXS 2004, scheduled for May 11-13, is a forum for professionals to learn,
discover, and refine the techniques and method

Wireframes and Use Cases

I'm working with systems analysts who are familiar with use
cases and only recently have been introduced to wireframes. They
are used to receiving business requirements and then developing
use cases out of those.

There is some debate on when is the appropriate time to
introduce wireframes into the process. My reponse was, it
depends on the project.

Re: Error messaging best practices

Ryan,

37signals' Design Not Found archives might be helpful here. Lots of good
(and bad) contingency design examples.
http://www.37signals.com/dnf/snapshots/

For my part, I think delivery depends on the nature of the error
messages. If you're only showing one error that's easy to remember, find
and correct, then a simple dialog box is sometimes enough. Multiple
errors though (like blank required fields) are more elegantly handled by
annotations on page.