[IxDA Discuss] Software companies actually using UCD

Juan Lanus juan.lanus at gmail.com
Sat Jul 1 06:17:05 PDT 2006


Cool factor? Cool to whom?

For anything to be adopted it must be cool for those who will use it
(as opposed to the designers, or the developers, or the computer
itself, for example).

This is the underlying idea of the UCD, its cornerstone.
Designing for the user is not acting a predefined ceremonial steps
like having meetings and wearing persona's caps. Sometimes it can be
done in isolation maybe while watching the sun setting behind the sea.
This is how innovation comes to life. No use testing, no focus groups.
You can't walk the streets asking people what they think about a flock
browser, or anything else, like al iPod before it was released.

Anyway, do it alone or in massive rituals, UCD is simply the oppposite
to self-referential design and those who don't do it usually hav in
trouble.
My point it that everybody designs for the user. Maybe the wrong one
but the user.

If you are in a company, and doing something not-so-small then you use
a methodology.
Here is where other differences show. With the same tools, different
people do different things according to their involvement, the
environment, and ultimately the "ambiental talent".
That's why mileages vary. This might be the answer to Daniel's
question about 'the *other factors/elements* that impact product
success.'

Also, I've noticed that size matters. There are methods and tools
published by big companies that only apply for the biggest projects.
I'm seeking a method for smaller ones. In all cases, what's always
true is that the more design you set before starting development, the
better and the sooner satisfaction is achieved.
--
Juan Lanus
TECNOSOL
Argentina



More information about the discuss mailing list