Chris Fahey is in the middle of publishing a series of blog posts on the topic of class and web design. (In part two, he asks What class are you?.)
Interesting topic (and somewhat taboo, here in the States, at least).
Last year, Jared Spool wrote an essay about a disruptive intranet redesign in which he used the analogy of finding your well lived-in home entirely changed on waking up one morning (Designing Embraceable Change). In it, he discusses how to make it easier for people to embrace changes in their information spaces:
To design for embraceable change, the design team has to be well aware of the existing Current and Target Knowledge points, as well as the new points. Field studies are the ideal technique for learning the existing points, whereas usability testing will give a detailed understanding as to whether the new design has an acceptable knowledge gap. These two techniques are essential for any team who needs to tackle this difficult problem.
File under useful: CSS 2.1 Reference : Cultured Code
There’s a lot of buzz in the interaction design world about the new Brown University website. Seems like they’ve broken out of the now-traditional, near-clich
Thomas Vander Wal explores the design implications of text strings (Domain of Digital Design Includes Strings). I used to think I was the only one who cared about the text in a file name or a url, but actually of course a lot of people do. Unfortunately, most CMS’s still produce butt-ugly urls, and I have to admit that I don’t have a well defined process in our user experience practice for defining the url structure for a site. Sometimes we specify the url paths in our content matrices, but not always. Now that people are more aware of the SEO implications of their urls (and the interesting but strange fact that Google views a hyphen but not an underscore as a word delimiter), there’s more attention to this level of the user experience. And that’s a Good Thing.
LukeW (from Yahoo) explores some ideas for Refining Data Tables at UXMatters. (Nice illustrations, too!)