I was wondering what others thought about our mailing list, is it not hard
to read and scroll through posts? On the one hand, I could conform to the
current standards of the format (which humans are very good at,
thankfully?), but isn't design about making things easier to use, and in
terms of present trends, full of beauty and goodness?
I am doing some research to see if it is possible to write
usability/accessibility checklists split up on all the layers in a web
project: Design (layout, typography, colors), frontend coding(semantics,
standards), backend considerations (web friendly urls etc),
content(writing strategies), etc.
Each and one of the checkpoints for each list will then be split up in
importance, what is recommended, what would require extra time, when in
the project it should be implemented (try to implement userfriendly urls
a week after launch), aswell as references to section 508 and WCAG etc.
We all know about "Door Handles > Affordance > Usability." Here is an icing on cake. [IMHO] http://brighthandle.com/ Comments welcome. I'd love to see know this idea can be streched
to future products [offline products with internet connectivity] and what could be the role of
UI designer [Or some Designer - but dont get me started on that]
May I have your advice please? I would like to explore issues surrounding Intellectual Property and Usability Testing.
I am currently providing User Experience Research and Design services for a start-up in Winnipeg, Manitoba, Canada. Time after time, we revisit the notion of Intellectual Property (IP) and Usability Testing. For example, does IP exist before Usability Testing or not? If so, who owns the IP?
I'd like to recommend that everybody read the new edition of Cost-Justifying Usability : An Update for the Internet Age.
I just finished reading the majority of it, and thought that it was an excellent read. While it is a "usability" book, it's a valuable resource for interaction designers also, particularly if they have to ROI activities.
In addition, there was an excellent chapter that detailed how to think about improving internal social return on investment.
So my role on our design team has recently been tending towards data-mining
and analytics. I've been able to get a *lot* of interesting answers to questions
using a combination of direct SQL queries, Perl, and Excel.
In thinking about the ease-of-use of a product or application, there
seems to be an assumption with some designers that give and take must
happen as it relates to efficiency and intuitiveness. (IOW, You have to
design for one at the sacrifice of the other, at least on some level.)
Where does this idea come from? Why can't we design and build something
that is both efficient and intuitive?