I was reading a great post by Russell Beattie recently on handheld stylesheets and the great implementation that Opera have launched on their community portal recently. It took me back to my (not so distant) days finishing up my Masters degree with our digital project. As you may guess, my group did a mobile project.
It was a great little project and it really allowed those of us who’d been working in web for so many years to apply our skills to a different platform and develop some really interesting learnings. For me, I was pretty amazed by what we found with regards to Information Architecture and Interaction Design.
Being a university project, of course there was a lot more research involved than you’d usually have the budget of the time to do for a commercial build. This allowed time for me to definitively show that there were very, very few ID conventions when it comes to interface design for mobile web content.
Recently I had cause to use a closed card sorting with the objective of ‘validating’ a proposed Information Architecture model (and some labeling). Argh. I think I will do what I can to avoid that approach in the future.
Card sorting in the initial stages of the project is a noble pursuit, in my opinion, and one that is bound to help you learn more about your users, how their heads work, and the problems that they’ll have with your site. Not to mention their ideas around what your content should be, and how it should be organised and what it should be called.
An IA Validation card sort happens a little way down the track when you think you know what your sitemap is going to look like, and what things are going to be called. You probably even have some draft wireframes that you’re not ready to commit to, but that you developed as you were thinking through the conceptual model for your IA and getting into the nitty gritty of the sitemap.
Once upon a time, I used to think that a card sort at the beginning and a card sort at the end of the IA scoping process was good practice. For my mind, I think that the second user testing exercise needs to be something related to the wireframes… maybe paperbased prototypes (or maybe even interactive prototypes?!), but definitely something that puts your IA into a context… a context beyond a few titles on some cards, that is.
There’s been a whole lot of talk lately about ‘ugly design’ and the perception that ‘it works’. The often quoted examples are My Space, eBay, Craigs List, and Del.icio.us. As someone who spends too much time thinking about design and trying to apply user centred design principles to the projects I work on, I find this somewhat annoying.
First up, let’s define what we mean by design. There are really two different aspects to ‘design’ that people are referring to – there’s the design that I’m most interested in which is the information and interface design. Then there’s the design that is most often talked about, that’s the visual design. Both of these types of designs are important when it comes to thinking about this idea of ‘ugly design’ and why, sometimes, it appears to work.
Information/Interaction Design: no one likes bad information design. Bad information design means you can’t find the information you’re looking for because its badly placed, or doesn’t exist at all, or the ‘flags’ (or scent) you need to help you find the information are hard to find or non existent. When you come to a site like this, you leave. And you don’t come back, unless you absolutely have to. The internet is abundent with information and making information that people are looking for easy for them is an essential part of making your site somewhere they’ll visit and return to, and recommend to their social network. Good information design (which includes information architecture) is entry level to having ‘a site that works’.
Interaction design, when poorly executed, is also a source of frustration for users, and a good reason for them to seek out an alternative to your site. Interaction design is poorly executed when it doesn’t allow users to perform the tasks that they wish to perform on your site with thel least amount of effort. Taking the time to identify these tasks and to ensure that they are implemented efficiently means that your site becomes ‘easy to use’, which is compelling reason to choose your site over other alternatives.