Discussion Archive: December 2004

21 Dec 2004 - 9:34am
Jason Koprowski

Usability & Interface Design Job Opportunity


My name is Jason Koprowski, I am an executive recruiter from Virginia. I
thought that the members of interactiondesigners may be able to assist
me with an Interface Design & Usability job opening I am recruiting for.
With your extensive experience in the industry, I didn't know if you
would know anyone who would be qualified for the position below; My
client is looking for 2 Usability & Design Managers.

20 Dec 2004 - 4:25pm
11 years ago
3 replies
Dave Malouf

Articles in the business world about design

If people can send me either online or offline bibliography that discusses
the implicit and explicit value of design from a business perspective I
would be most thankful.

-- dave

20 Dec 2004 - 2:03pm
11 years ago
4 replies
Elizabeth Buie

"Whiteboard" goes poetic about design

As some of you know, I edit a column in ACM's "interactions" magazine
(http//www.acm.org/interactions), a column of opinion and sometimes
whimsy, aimed at designers who are not IxD or usability specialists but
who do have a clue and want to know more. The column, "Whiteboard," is
now five years old.

19 Dec 2004 - 3:25pm
11 years ago
1 reply
Danny Bluestone

RE: Discuss-interactiondesigners.com Digest, Vol 15, Issue 18

Hey Rick

Sounds like a good process. I have a question for you.

Who manages the project once a strategy and budget have been agreed?

17 Dec 2004 - 7:57pm
11 years ago
1 reply
Robert Cornejo

Multi-Mode Software

In most cases a tool or function is unexpectedly no longer available to the user when an application switches modes. The AP has a story on the accidental F-16 strafing of a NJ children's school due to pilot error and confusing software. The pilot had over 2,000 hours of logged flight time, nearly half of that in the same type of Jet. There are other scattered reports of defense-related mishaps due to poor design.

Aside from PLGR and the Blue Force System are there examples of stand-out successes in defense, security or law enforcement?

"Pilot Error Blamed in N.J.

17 Dec 2004 - 6:41pm
Nick Ragouzis

Workshop 28Jan05 Palo Alto -- User experience and Federated Identity

Designers concerned with a user's experience and the
interactions that make that possible are often also
concerned with business opportunities and its key

There is one technology that is ripe for just these
opportunities, to help users and businesses alike,
that is little understood in this community of designers:
the technology of digital identity.

This is an invitation to a workshop concerning the leading
technology in this domain: federated identity.

17 Dec 2004 - 11:00am
11 years ago
5 replies
Marc Robichaud

When to bring in technology?

What about the data model or database design? Should we be considering that
separate from the technology?

Sometimes I think the data model should be made before the interface because
an interface that strongly reflects the data model is easier to use. That
is, users can more easily create a mental model of the data. Even a
task-based interface should account for that.

However, I've also run across many projects where the data gets modeled
based on how the user wants to approach the problem. This seems to be more
of a case in search and taxonomy however.

17 Dec 2004 - 10:23am
Peter Boersma

Design process: When to bring in technology? (was RE: [ID Discuss]Software for requirements management)

David wondered:
> I just want to make sure that what he is saying above is not saying that
> design should be completely technology free throughout its
> process (even the front-end design).

You are right, I am not saying that design should be completely technology

17 Dec 2004 - 9:45am
11 years ago
5 replies
Narey, Kevin

When to bring in technology

>First I want to say, that in general, I totally agree that design and
technology should be separated >as much as possible.....

I'm interested at what point in the process we should make a decision on
what technology should be used.

17 Dec 2004 - 9:16am
Dave Malouf

Design process: When to bring in technology? (was RE: [ID Discuss] Software for requirements management)

> As with front-end requirements, software requirements should
> be kept technology "ignorant" for as long as possible.