I attended the FLOSS Extreme Usability Spring II in San Francisco last week.
In the words of the event organizers Blue Oxen and Aspiration:
“Extreme usability is a methodology that incorporates usability in a highly iterative and agile development process and that partners usability practitioners with programmers and users as co-designers and co-developers.”
Unfortunately, we were unable to take Chandler there as a project, but I had a great time working with the folks from CivicCRM. The event lived up to it’s name and was an extremely intense 3 days of whirlwind usability.
I’ve written up a short-ish report of the what our group accomplished at the sprint and the process we “invented” along the way.
The write-up in turn generated some thoughts as to the nature of usability and design, both in general and in practice. In particular, it got me thinking about how the vague and intangible nature of designing software for human beings is better suited to Extremely Rapid and Extremely Iterative design methods than the Somewhat Rapid and Somewhat Iterative approach that I’m used to.
Personal take on What is Extreme Usability?
Broader implications on What is Usability?
I also realized that while here at OSAF, we are priveleged to have such a close and ongoing working relationship between Development and Design, there are still many lessons to be learned about how to make that relationship even better.
I’m looking forward to trying out some of the techniques we experimented with at the sprint, in-house. Perhaps to iron out some of the existing design issues we have as well as to generate new ideas for areas of the UI that are still murky at best. I’d like to gain a better understanding of where Extreme Usability works very well and where it works, not so well.