Monday, March 14, 2011

From the "Ah, the Irony" Department

We bought this can opener yesterday. It's the kind that doesn't leave sharp edges on the can or lid. We were amused to find it packaged in one of those rigid clamshell packages--you know: the kind with the really dangerous, sharp edges.

Do you know the recommended method for opening rigid clamshell packages to avoid injury? With a can opener.

If only we had one.

Friday, March 4, 2011

Design for Disability

"In the context of an environment or society that takes little or no account of impairment, people's activities can be limited and their social participation restricted. People are therefore disabled by the society they live in, not directly by their impairment." --Graham Pullin, "Design Meets Disability"

Monday, February 21, 2011

I am not a tool

Or am I?

This year's theme: TOOLS.

I've been in several meetings where IT people have asked what tool we use for usability, or Agile, or design. I am surprised that people assume that having a tool gives you the ability to implement these practices effectively.

  • For Agile, we don't use Rally: we use spreadsheets (SharePoint lists, to be precise).
  • For Design, we use everything from Dreamweaver to Notepad to paper and digital cameras. 
  • For Usability, we use everything from Morae to paper. Yup, paper.

Get it? It's not the tool. It's the process, skills, and oversight of both. In other words:

  • Having Project doesn't make you a skilled project manager.
  • Having Word doesn't make you a best-selling author.
  • Having a toolbox doesn't mean you can build a home that would meet code.

Learn what it's about first. You are the tool.

Sunday, January 30, 2011

No caption needed.

I don't believe this warrants any discourse about WHY it's a poor form design choice, does it?


Wednesday, October 13, 2010

What is "user testing"?

We get a lot of references to doing "user testing", and there seems to be a vague notion of what that means. At a basic level, there are two types, and they are very different. Here's how I explained it in a recent correspondence with a project sponsor:
...there are two types of testing that should be required of our customers: usability testing and user acceptance testing. They have different purposes, and different processes.

Usability testing is a one-on-one test with a facilitator and a participant....The goal is to identify barriers to users completing what they need to do in the system. This testing usually happens before the design is finalized....It is scripted and structured to quantify specific usability issues that will negatively impact implementation success and user adoption.

User Acceptance Testing is a test phase, usually after QA testing by the internal test team, where project sponsors and users are given access to the test system ,and are asked to do their normal tasks using the system and report back any functional problems. The goal is to identify what would prevent us from launching. Usually this happens well after the system is built, just before "go-live". It is usually not moderated but may be scripted.
So, if you do usability testing, it should identify major issues up front, which is much less costly to mitigate. Then UAT will likely only identify minor issues that would prevent launch. If you don't do usability testing, UAT will uncover more severe issues requiring more expensive mitigation, such as code refactoring.

Certainly usability issues may be uncovered--and should be addressed!--during UAT. But UAT is not a replacement for usability testing early in the process. Early, you are focused almost exclusively on the usability and accessibility of the system BEFORE the code is carved in stone.

Different and equally valid goals, and neither should be short-changed.

Wednesday, October 6, 2010

Mixed blessing

Got another call today from someone who wants to have me "look at their new web site design" and help them make it usable. I am so glad that the awareness is there, but now I have to explain how asking for one person's opinion doesn't allow you to check the box next to "usability" on your project plan.

Friday, October 1, 2010

Best Alert I've Seen This Month

From Google Calendar:


At some point, sites may have to stop support for outdated browsers, and this is a humorous and graceful way to do so.