Just finished up reading Designing Interactions by Bill Moggridge. While it meanders at times, and seems to be repetitive at points, it is a fine read. Written by one of the founders of interaction design and the term itself (the term is properly attributed to Moggridge and Bill Verplank), it is a survey of the history and future of Interaction Design. Designing Interactions is a who’s who of interaction design, with interviews cleverly woven into the story as told by Moggridge. The author approaches interaction design much (and not surprisingly) in the same way that Ideo does (Moggridge being a co-founder of arguable the most innovative industrial and interaction design firm). A very wide view of interaction design is presented, though Moggridge carefully articulates his personal breakdown of IxD in the last chapter of the book. In closing, great read. The early history is particularly fascinating and inspiring. I highly encourage anybody interested in interaction design to snag this book.
Archive for the ‘IxD’ Category
Designing Interactions
Tuesday, April 24th, 2007Karim Rashid and Such
Tuesday, March 27th, 2007I was lucky enough to get to see Karim Rashid speak last weekend. I suppose if I were a few years younger I would have left feeling very inspired as Karim is very convincing when he pontificates about designers being a changing force in the world. I am so over inspiration at this point and am more interested in the juicy details. At any rate it was a good talk and certainly well received by the college students in attendance, and it got me thinking about a few things.
Branding.
There is no better example of somebody who has branded themselves better than Karim. I have long thought branding yourself (or your style) is an important part of starting a design business right from the get-go. Having said this, and having a firm understanding of the concept, I have never been able to pull it off myself. I have had two mildly successful design businesses (neither were so wildly successful that I wasn’t easily lured away) and have struggled with the concept. Why is this? Generally, I needed every client that I came in contact with and was willing to do just about anything to get them, and keep them onboard even if it meant sacrificing my style. It should be noted that while I’d sacrifice my style, I’d rarely if ever sacrifice my design ideals — appropriately sized logos, consistent fonts, and such. While it seems logical, it initially is a big risk to create things that fit squarely into your style, but don’t mesh with the clients goals. I’m sure it gets easier after you get a few works out there and start getting hired because the client likes and wants your style. Good examples of successfully branded designers/photographers are: electricheat.org, nopattern.com, Dan Winters, David LaChapelle.
Usability.
While Karim is a very visual person, it seems that most of his process starts from a place of usability. In other words, it seems that he often strives to make products more user friendly when designing. After looking at a great deal of his work, I’d have to say that he doesn’t always hit this mark but you can see many of the arguments behind his designs. This begs two questions in my mind:
1. How much of the user experience is strictly usability?
There are many elements to the user experience and usability is only a small part of that. O.K., maybe a little bigger than small, but it’s not the whole deal. As outlined by David Liddle, there are three phases in adopting a new technology: enthusiast, professional, and consumer. In this instance, I am only interested in the last, the consumer phase. In the consumer phase of adoption, usability becomes a smaller part of the equation than say the professional phase. Sure the object needs to function as advertised, but it plays a much larger role in the lives of a consumer. The product needs to be something that the consumer can identify with — it has to be part of their style. Sure it needs to work (at least as good as anything else of equal price), but it also has to be cool. In the past, I’d agree with Liddle when he says that a technology moves up the chain from enthusiast to professional to consumer, working out the kinks of usability in the process. However, I’d argue that in today’s world, services and products can start at the consumer level through the use of rapid prototyping. So, when designing one of these products or services, where does usability fit in the picture? Do you sacrifice usability to make something cooler, or more visually stimulating? Is it left up to the consumer to decide just how well they need something to work? These are some of the questions that the industry must answer as the demands of products and services as a whole increase and the time to market decreases.
2. How many risks does one take to change the way an object is used by the masses?
So, somebody asks to you to redesign their service-based web site. Where do you start? Do you simply do a redesign, collect your check and move on? I have always been, and always will be interested in making things work better. As Karim stated, we live in an interesting time, because the design of many things is stagnant and it is up to us as designers to get products and services out of their rut (totally putting words into his mouth, but that’s what I took from it). That being the case, are you willing to take the responsibility of changing the way something works? In short, you should … but you better be right, or close. The best example of this is the Apple iPod. It had all the same functions of any other mp3 player, but it completely changed the way we use the mp3 player. It required an investment from the end-user to learn a new way to do things. And, the end-user was willing to do this because it was just so damn cool. In generally big corporations are very nervous about making big changes to their product line or service. And when they do, the changes happen really slowly. This is all going to change over the next 10 years as start-ups (like Google) and giants (like Apple) become hugely successful by challenging how things work. With the quick rise and progression of technology I am expecting to see a lot more businesses take chances.
It is indeed an interesting time to be alive and thinking about the issues of design in the world. As technology changes, so too does everything else.
To Button, or Not To Button
Saturday, March 10th, 2007We are in the process of updating all of the gallery modules for the online courses at HerbergerOnline. There are several improvements that will be made during the overhaul. I designed and coded the originals. They are scalable and pull images and text dynamically from external jpgs and txt files respectively. They are however, procedural and require an individual compile for each gallery. They also lack the ability to print.
So, I decided that since there was so much work to be done, we might as well re-address design choices to enhance the user experience. The biggest was certainly the redesign of the previous and next buttons on the interface. The initial buttons were a hack job to be perfectly honest. They had an over state and that’s about it. They didn’t disable when there were no options available, and though you could tell where you were in the gallery via the “image __ out of __” information, this was still a huge design flaw — updating was a must.
The question is basically this; If a button is not functionally available, do you leave it on screen and visually disable it, or do you get rid of it all together?
The argument for leaving it, is that in doing so you are presenting the user with the information of potential functionality — I may not be able to do this now, but I will be able to do so in the future. This could aid a user who may be apprehensive about moving forward (in our case), for fear that a return view might be disallowed. The argument for taking it away altogether, is simple, if there’s not an option, the option shouldn’t be available as it may create confusion.
In the end, I think my decision came down to trust. I believe that users are at the point where they should not only be able to trust the application, but should expect to only be given options the are functionally available or inform a decision. I truly believe that the deduction to the smallest common denominator (for lack of better description) reduces potential confusion. In other words, I believe (without scientific evidence) that something not being available creates less questions than something being available and not functional. An office vote had 4 on the side of removal, and 3 on the side of disabled. (note: it was mainly old men that voted for the disabled — I’m just sayin’)
I will say that this is a case-by-case basis and the decision should be based on whether the information about potential use is important to the user, now or in the future. Photoshop is a good example of where disable tools and menu functions convey important information to the user. In some cases, this information will lead the user to an action that must take place before potential use is made functional. For instance, Hey, why aren’t these disabled effects available to me? Well, maybe if I shift over to RGB mode I can change that. Sure enough! In this instance, a disabled button gave me the information I needed to take action.
To conclude, I believe that if there is no extra information being conveyed by a disabled button or function that is potentially essential to a user engaged in a decision making process, then that disabled button or function has the potential of creating more confussion than clarity. In other words, a disabled button needs to have a reason to be there, otherwise get rid of it until it’s of use.