article archives

Big Music Website Redesigns
ONE WHOLE PAGE!

Sites get old. They start to get krufty, or out of fashion, or whatever. As web designers, there is nothing we like better than to completely redo a site. Re-strategize, re-colorize, re-semantifize. Just Redo It. Love love love redesigns. Client says, “Hey my website is running kind of slow.” Redesign! “I need to increase my traffic by 10% or I’m out of business.” Redesign! “Um, my email isn’t working right.” Redesign! See how exciting that is?

But I’ve noticed something on this one site I’ve been using for a while. The site in question, emusic.com, has recently made some incremental, positive improvements to their site. An example: in-page previewing of songs and albums. This is big a step forward from the 30 second iTunes stream of yore, which would lag, and which you would then need to delete from your library by hand, quietly informing those within 40 or 50 feet of your desk that there was a better way.

Then, tonight, I notice their album download page has been almost completely redone. The actual preview is the same (or nearly), but they have added YouTube videos of songs from this album. They have a Wikipedia entry. They’ve somehow gotten users to write actual reviews, rather than terse, meaningless loved it/hated it knee-jerk comments!

The team at emusic has taught me something. The lesson: You don’t have to redo a whole site in order to make big improvements. While the header, navigation, and footer, has been worked on, much of the site remains virtually untouched for a few years now. And it works fine.

I know the thought is intoxicating: an entire site, springing forth, fully-formed, modern, minimalist, community-centered. From the GROUND UP! One minute, same old site. Flip that switch and bask in the onslaught of blogglory that inevitably follows. As I’ve been shown, this is not the only way to meaningfully improve your user’s experience.

But now I’m all mad, cause I’m out of downloads this month.

Disclosure: I am an investor in emusic. In the sense that I regularly invest something like $9/mo into their company. Because of this generous duodeci-yearly contribution, emusic allows me to download a certain amount music from their site every month.

P.S. That band I linked to above is awesome. It’s these two guys from Belfast, and from the sounds coming out of the stage, you wouldn’t believe it was just two people making all that audio.

posted by pete on Sunday, Aug 10, 2008

Stand Tall, Boys

Matt and I were leaving the Triad Center today after the conclusion of a meeting. He was kind enough to offer me a ride over the the COB to my next appointment for which I was already late. We headed down the elevator to the parking garage, and upon disembarking, found a group of people standing around in the basement. One suited man turned to us and said quietly, “Stand tall, boys.” I was not sure what he was talking about, and was very curious as we turned the corner. There, standing in the midst of a group of people and telling a story of how someone had earned the name of “Bucket” was our Prophet, President Thomas S. Monson.

Wow.

I stopped in my tracks and gasped, “Oh my!” We stood there for a minute as he finished his story and after doing so he was whisked away by his security guards. I have pondered that chance meeting for the remainder of the day today, wondering what would have happened had I decided to walk to the COB. I probably never would have known he was even there. Even though I didn’t get to shake his hand or say anything to him, I felt his spirit the moment I turned the corner. I knew I was in the midst of the Prophet of God. I am really grateful to be working for the Church and downtown near all these great men. Are we sure we want to move our department to Riverton?

posted by rick on Tuesday, Jul 15, 2008

How To Be Creative

Mac Magleby recently retired from his post as Professor of Illustration at the U of U. Upon being asked in an interview with Susen Sawatzki of AdNews whether he’d done a “last lecture”, he presented some pages he had been handing out to his graduating classes since 1987.

The first, titled, “Creativity-How to be Creative” goes as follows:

Creativity is the act of bringing into existence that which is unknown, uncommon, or unexpected. Being creative is risky; however, where the risks are great, the rewards are greater! To be creative, you need to be comfortable feeling lost and in deep trouble. You need to enjoy absurd, contradictory, outrageous possibilities. You need to be a lover of exploring uncharted territory, and, most of all, you need enough self-confidence to fail.

Another sheet makes a comparison.

How To Be Creative:

Do preliminary research into the problem. Get a thorough background, understand the nature of the problem. Work in a restful environment. Know you can do it. Have faith the idea will come. Minimize interruptions. Relax, let ideas start to flow. Walk around. Wash your hands in warm water. Go with the flow. Add some stimulus, look at inspirational sources—books, photos, nature, etc. Join ideas together. Ask, “What if…?” Use free association. Let creativity take from naturally. Start with simple, build to complex. Don’t force it. Get away. Relax. Take another direction. Change surroundings. Add new stimulation. Use other sources as a springboard. Let the idea expand and improve. Build on that idea. Refine the idea, test it, and if it works, go with it. If it doesn’t work, reject it and repeat the process. Work hard. Don’t give up!

How Not to Be Creative:

Work in a hectic environment. Start working right away. Be negative. Tell yourself that it can’t be done. Stare at a blank sheet of paper. Get all uptight. Worry about job security. Sit in one place. Dress in a suit and tie. Sit up straight an be rigid. Keep those muscles tight. Work in a vacuum. Use no outside resources. Sit in one place. Force the idea to come. Make the problem complex. Reject ideas. Fear new, unproven ideas. Don’t take risks. Throw up your hands. Quit.

posted by rick on Tuesday, Jul 15, 2008

Reshaping Beijing – the Egg, the Boxer and the Dragon

Since we are all reading a book written by an architect, maybe it is a good idea to supply some real life examples—architectural monuments in Beijing.

Magnificent or magnificently ugly? It is your call. FYI, the locals gave them those nickname above.

posted by tim on Saturday, Jul 12, 2008

Book Review: How Designer’s Think: The Design Process Demystified by Brian Lawson (4th Edition).

A month ago, in preparation for an in-house design workshop, we handed out 30 copies of Brian Lawson’s Book “How Designers Think:The Design Process Demystified” to our designers. I first came across the first edition of this book nearly 10 years ago when I started a job at a small design firm in Salt Lake City. I had just moved from a large fairly structured company into a small, very organic company with very little structure at all. I found a first edition book on the company bookshelf and started reading.

I’ll have to admit that the first read was very difficult. The book is quite academic – the author approaches the subject from the perspective an architect who also happens to have doctorate in psychology. Most of the examples in the book discuss architecture and it can take some extra mental work to draw parallels to the profession of graphic and interaction design. In many ways, I found Lawson’s book to be very refreshing.

Lawson’s unique background allow him to approach design from a unique “scientific” perspective, while his design background from architecture, a design discipline provides a balanced perspective. It doesn’t go to far into esoteric design theory that is often discussed by practicing designers, and it doesn’t try to be to prescriptive, a fault which often appears when scientists and engineers write about design. He is able to talk in the language of design, where other authors like Don Norman and Jacob Nielson seem to speak about design in the language of science. There’s actually a great chapter in the book where Lawson illustrates the difference between the scientific approach, and the “designerly” approach. It’s especially comforting to hear it from someone who has practiced both disciplines.

I think that this unique perspective makes the book especially interesting and useful to any practicing designer. Lawson covers the essence of design, the definition of problems, and artfully describes different approaches to the design process. His model of the design process is the best I’ve ever found (chapter 3). He describes design as a “negotiation between problem and solution through the activities of analysis, synthesis and evaluation.” Other essentials deal with strategies for measuring the success and value of design (Chapter 5), and chapter 7 provides an excellent overview of the nature of design solutions, problems, and processes (chapter 7).

My favorite chapter, and the one that has influenced my work perhaps the most, is chapter 13: Design Traps. Lawson outlines several common traps that designers find themselves in. You can’t read this chapter and not have an “aha” moment, or cringe at the things which might be affecting your design right now.

I consider this book a “must read” and believe that it is one of the best books on the subject. The viewpoint is unique, and it provides beneficial knowledge that will help you in all aspects of the design profession.

We’re looking forward to the discussion next Friday.

posted by john on Thursday, Jul 10, 2008

Webslug: Helping measure the worldwide wait… sorta

Webslug claims it can “help you measure the worldwide wait.” Cool tagline, but I’m skeptical.

The time I got back on one site was infinitesimally small (less than a twentieth of a second) when personal experience shows it takes around 10 seconds. Another site showed over 40 seconds when my experience has been around 20 seconds. And finally the site doesn’t answer the question, “How fast is it at a given connection speed?” It just gives seconds to load without the context of a data rate. (The Firefox Throttle Add-On does this nicely, but only on the Windows version.)

On the upside, it does let you compare two sites to each other and collects measurements of all the sites that get tested for public review. I like these ideas, but Webslug will have to fix those deficiencies before I come back often.

One final wishlist item, the value of which was demonstrated in a presentation by Aaron Barker recently, is being able to see the difference between “page appears” (something happens to show the user that the site is loading), “page is partially functional”, and “page is fully functional” (100% loaded). If a page takes too long to appear initially, the user may get impatient and hit Refresh—which will actually delay them further by restarting the whole process. So even if it’s not fully functional there is value to getting something up there quick, even if it’s not the full meal deal. But I’m not sure an automated tool could really do that… Someone prove me wrong please!

See Webslug for yourself.

Also check Yahoo’s best practices for increasing performance on the front end. (Thanks for all your recent help on this stuff Aaron!)

posted by ted on Thursday, Jul 10, 2008

Alt Attributes: Image Description or Idea Description?

It is common knowledge that alt attributes should contain image descriptions. Unfortunately this is somewhat of an over simplification when it comes to icons or other images used as pictograms, especially when the icon is only loosely related to the action being represented. This problem can more easily be illustrated by an example:

If your web site contains a delete button represented by a trash can, you might write your alt attribute as alt=”trash can”, and under the simplified “alt = description of image” doctrine, you would be entirely justified. However, I encourage you to give this some careful thought. What is more important, that a visitor know what icon you chose to represent the delete action, or that they know what button to press to delete something? Unless you’re in the business of offering icons, I would assume the latter, and encourage you to use something like alt=”delete” instead.

What’s worse, someone who has been blind for a substantial portion of their life may not have sufficient experience with pictograms to understand what they mean based on their description. For instance, many blind users may have no idea what to make of alt=”a red circle with a line through it”. The user could guess, but do you really want to make the user guess about your interface?

I recently came upon a table which was used to show the status of various tasks. The column titles were something like “pending”, “completed” and “failed”, and the rows had labels like “registered in database”, “confirmed”, “synchronized”, ETC. To determine the status of a particular task, you would find the row for the task you were interested in and then look across the table to see which column had the dot. If The dot was in the “pending” column, it was a blue dot, green for the “completed” column, and red for the “failed” column. The alt attributes were alt=”blue-light”, alt=”green-light”, and alt=”red-light” respectively.

This is of course probably quite simple for most screen reader users to figure out, but it would be simpler still if alt=”pending”, alt=”completed” and alt=”failed” were used instead. Simpler because “looking” at a table is a little more work for a screenreader user. But more importantly, it gets back to the question, what’s more important, the icon or what it represents?

So in short, just remember that alt attributes are primarily not intended for helping the user to “see” the image, but rather for helping them get the information the image conveys.

posted by cannona on Monday, Jul 07, 2008

Accessibility on NorthTemple

UPDATE: Since this article was first written, Jason has implemented a very useful archive for Northtemple, including everything tagged with “accessibility”.

ORIGINAL POST: We have a lot of traffic coming to North Temple to read Aaron’s Accessibility Checklist (the one he vowed he’d never write). While you’re here you might check out some older accessibility posts (still working on that archive, right Jason?):

Plus a collection of short quotes and links:

(By the way, and totally unrelated to accessibility, Microsoft’s Live search helped me find all this stuff with their site search where Google failed… What’s up with that?)

posted by ted on Friday, Jun 20, 2008

Google Docs will never become a dominant word processor unless…

You guessed it, they make their interface accessible. If you are not able to use a mouse or see the screen, you are basically out of luck when it comes to Google Docs. The best you can do is read what others have wrote, and even that is a bit awkward.

Granted, it will not be easy for Google to substantially alter this situation with current popular techniques, but it should be made a lot simpler with the Accessible Rich Internet Applications (WAI-ARIA) standard being worked on by the The World Wide Web Consortium.

For those who are not aware, ARIA is a proposed standard which, among other things, seeks to bridge the gap in communication between the screen reader and dynamic web applications. It allows you to tell a screenreader user, for example, that a particular element on the page is a drop-down menu, add enhanced keyboard functionality, and draw the users attention to elements that change. It is a very promising standard which is already seeing some support in the latest versions of screen readers, and a few of the very recently released browsers.

But getting back to Google, I believe that inaccessibility will very likely hold them back in the market. It is true that the vast majority of users don’t even know what accessibility is, and if they do, they probably don’t pay it much attention. So how could it substantially effect them in the market? There seems to be a growing trend within a few companies, but more within government, to discourage the usage of inaccessible products when accessible alternatives exist. I believe that at least some of the efforts being put forth by companies to make their products more accessible can be directly attributed to these regulations and policies. Of course, I don’t wish to imply that it’s entirely a business decision, as I am sure many companies do it because they care. However, having a little market pressure never hurts.

Right now, Microsoft Office works great with any screenreader worth speaking of, and if you’re the person responsible for deciding what software your organization will use and you have a mandate to consider accessibility in your decision, MS Office has a big advantage that might be difficult to overcome.

Nevertheless, because of the afore mentioned market pressure, and because of Google’s promising history of making virtually all of their other web applications accessible, I am quite optimistic that I too will soon have the opportunity to use Google Docs.

posted by cannona on Friday, May 30, 2008

Little known facts about breaking your kneecap

Last August, my wife provided material for a post on little known facts about breaking your ankle. As implied in my recent post, where my 9-year old observed that his brother now lives on the couch, my older son has provided us with additional bone-breaking insights:

Matthew is scheduled for surgery on Friday, so I will probably be missing Cameron and company’s all-day training on visual design. (Have we mentioned before the incredible internal training opportunities we’ve had, especially recently? One of the best things about working here.) I am really bummed about missing this, but what can you do? Father First (especially if you don’t hear your son screaming in pain in the middle of the night and you still need to earn back some points!)

posted by ted on Tuesday, May 27, 2008

Using a bit of psychology on your users

I cleaned out my garage this weekend and looked through a few of my old college text books (why do we save these?). I found a book on art criticism and another on operant conditioning – reflective of my degree in Art Education and Psychology. I was reminded of the article on Coroflot about how interaction designers never start out that way and often find their way into the career. I come from varied fields having little to do with computers, but everything to do with human behavior. I’m a people watcher – portrait artist and behavior analyst, to be specific. So I’ve studied a bit on human anatomy, facial features, gestures, and a little more on operant conditioning of behavior. It’s the latter I’d like to elaborate on because it has an influential place in manipulating the user experience by using our designs to encourage or discourage user behaviors.

Operant Conditioning is best understood using the box model, B.F. Skinner’s box model. It’s a method of increasing or decreasing behavior based on reinforcement or punishment. Take a quick detour and read a simplified discussion of the Skinner box model.

Thanks for coming back. Now you know a little more about positive and negative reinforcement, punishment, and extinction. (If you still think punishment means spanking, go back and read the definition.) So the idea is that you can increase a behavior by giving something (positive) or decrease behavior by not giving something (negative). A real life example is I will give my child a half hour of Wii time if she cleans her room. The cleaning behavior increases because of positive reinforcement.* An interaction design example: the user clicks on a part of the screen that is designed to look like a metal button and they get the desired results. The behavior of clicking on metal looking pixels will increase because it provided positive reinforcement. A user could learn to use a different colored button, but consistency across a site or OS will help them learn the behavior faster. An example of negative reinforcement: a user scrolls down to hide the top 15% of the web page which is covered in banner ads. The behavior of hiding the top of a screen is increased because it stops the flashing banner ads. And last, an example of extinction: a web site has broken links. The user will stop clicking on links when nothing occurs. Because neither positive or negative reinforcement occurs (nothing happens), the user’s action of clicking on links eventually stops – and they will most likely leave the site.

This is a little more technical than I planned, but the concept is that we teach our users to use technology through providing rewards for their behavior. If not careful, we can also teach incorrect behavior by reinforcing the wrong actions, leaving our web sites and applications a messy user experience. If our users are struggling with a part of a web application, identifying how the design is teaching behavior through operant conditioning can help us resolve and correct the user experience.

Human behavior is an amazing thing that evolves as our environment changes. As interaction designers, we play an important part in teaching the users to evolve and adapt to new experiences.

Or maybe our users are teaching us...

*A bit friendlier approach to operant conditioning of your children: Love and Logic

posted by emmy on Saturday, May 17, 2008

Return of the Search Logs

A funny thing happened on the way to the search engine… Our latest batch of interesting North Temple search hits:

And one of our current favorites:

posted by ted on Thursday, May 08, 2008

text vs font in CSS properties

A question came up today that when floated around to a few people we didn’t have a good answer, so I thought I’d toss it out to the interwebs. Is there any rhyme or reason for the separation of CSS properties that start with FONT and those that start with TEXT (including a few others like color, line-height, etc). For reference here is W3C’s pages on font and text.

Since we don’t have a method for easy response at the moment I’ve created a NorthTemple twitter account to provide your abbreviated responses. As an aside, several of the team here have started twittering recently, and so we may use this NorthTemple account for other stuff in the future. Follow us and wait in eager anticipation for that future day =)

posted by aaron on Thursday, May 01, 2008

The Most Important Skill

About a week ago, the following question was asked by one of our designers: “What is the one skill that can make the most positive impacts in your profession?” If you leave out the obvious answers, such as invisibility or flight, the question is not so easy to answer. A great designer must master several skills in order to be truly effective. After realizing that I didn’t have a good answer, I decided to explore the question a bit further.

What are Skills?

Skills are really only one part of the picture. There are also things that you must know, and there are things that you must be. Skills are actionable, they are the things that you can do. Knowing lots of stuff is not a skill, and simply being a “nice person” is not a skill (there are things that you do in order to know lots of stuff, and things you can do to be a nicer person). Things that you know and your personal attributes are important factors. You can’t have skill in anything if you don’t know how to do it, or if you do not have the attributes required to execute a particular skill.

What Does a Designer Need to Do?

Great designers must perform many different tasks throughout the course a design project. Great designers need to be generalists. They need to have the right attributes, broad knowledge, and good skills in all the areas that they might be required to work. In general, the work that designers are expected to do falls into one of the following three categories.

  1. Understanding
  2. Identifying
  3. Crafting

For each of these sections, I’ve identified what needs to be done, and which skills a designer must execute in order to be effective.

Understanding

The designer must be able to understand or discover the problems and/or opportunities that they are asked to address.

This can be done by:

  1. Listening to those who will be affected, and to those who best understand.
  2. Empathizing with those whose needs you are trying to meet.
  3. Analyzing the data and facts associated with the issue.
  4. If there are no facts, no data, and nobody to listen to, the designer must creatively find ways to build facts and identify the stakeholders.

Identifying

The designer must be able to identify and must also be able to demonstrate realistic ways to address the problem or engage the opportunity.

This can be done by:

Crafting

This can be done by:

  1. Executing the chosen solution in the proper and most perfect way possible according to the available budget and time constraints.
  2. Coordinating and directing the work of others who might be assisting you in the final production.
  3. Evaluating the production work according to the highest standards of your craft.
  4. Presenting the final production ready work with simplicity and clarity.
  5. Educate others about decisions leading to the final design.

What are the Skills?

The above outline is by no means a comprehensive list. Perhaps it is even too simple, but it does provide a basic outline of some of the general things that a designer must do. From this outline, we can extract the following list of skills (the things a designer must do) in order to understand, identify, and craft excellent solutions.

The designer must:

In the case of web site or interaction design, there are few specific skills which come in very handy:

Which skill is most important?

Of all the skills above, I don’t know that you could identify one as being more important than another. The most important skill might be whichever skill you are currently the weakest at, or it might be the skill where you have the most potential or opportunity to excel.

There is one other skill which has not been listed, which is perhaps more important than any other. This sometimes forgotten skill is required before any of the above can ever be obtained. The one skill that I would identify as the most important, and the one that can make the most positive impact on your profession, is that of mastering your capacity and ability to learn.

If you have comments about this article, please send them to john.dilworth [at] gmail.com or discuss them here

posted by john on Wednesday, Apr 30, 2008

“Noise”—in design and in life

I came here to write an homage to administrative professionals—those often-forgotten treasures that do all the behind-the-scenes things to make our work lives tolerable. I have several that support me, and our design group has an exceptional talent in Debra Xavier.

As I caught up on the recent posts, what I write morphs a bit… Emmy talking about vision, Jason realizing that often the universe won’t recognize design, my own frustrations with keeping consistent vision and a sense of humor about the challenges of our project…

ALL of this leads me to believe that our universe is “noisy”...lots of input, lots of distractions, lots of pressures… and I would say that noise drives me to need to ask: “what really matters today?”

I would submit that design is precisely what allows us to adjust to vision changes [literal and otherwise]. Even if no one else on the particular project agrees with me completely, design matters.

For me, one of those vision-related tasks today became thanking our awesome Debra for all she does. Software comes and goes, but people are the real permanent resource; the relationships and the work we do together will last much longer than our web pages!

Today I will also do what I can to educate our business partner about the reasons behind our design decisions, even when they would like us to do something else. I hope to be both persuasive and respectful as I listen to how they see the world.

and I will look forward to hearing more about how Emmy sees the world, since I’m a lot MORE myopic than she ever was!!!

posted by bea on Wednesday, Apr 23, 2008

Does design matter?

Two interesting things happened to me today. First, one of our internal clients asked me to take a design we’ve crafted for more than six months and keep everything except the primary color of the design. That small detail, the one color we chose first and with which we made probably 1000 decisions. Could you just change it real quick? (and it’s not to a different hue, it’s to an embarrassingly opposite side of the spectrum, and quite possibly a color only dogs can hear.)

Second, after rejecting two job applications without portfolio URLs in their resumes, I received two links from the recruiter that would have crashed Firefox if Firefox had that yet-to-be-released Will It Burn My Eyes Extension.

But that’s just it. Firefox doesn’t care how well-designed your site is, and neither do probably 99% of people who consume it. Recruiters wouldn’t know good design if it smacked them in the face. Clients, directors, vice presidents—are they any different?

If not, then why do we bother? If great design isn’t appreciated, then what?

posted by jason on Tuesday, Apr 22, 2008

How to conduct a homemade vision test on your website

Over the last six months, my eyes have gone through an interesting transformation. In October, I went under the laser and with Lasiks, changed my eyesight to 20/15. Prior to the surgery, I had several tests on my eyes, including a “super” dilation. I’m not sure of the medical term, but it meant my eyes stayed dilated for 48 hours, I had a big headache, and really cool farsightedness (hyperopia). I could completely relate to my parents and their trombone reading style. Anything closer than my out stretched hand was completely out of focus.

Before surgery, I had 20/60 vision. Not bad, but I couldn’t read an alarm clock in the dark without squinting. I’ve been near-sighted most of my life and for most of my computer work, I could work without glasses. I also preferred smaller fonts and tiny details.

During my 48 hours of super dilation, being a bit of a computer addict, I kept working. I noticed an interesting effect with my eye sight and the computer screen. The text on most sites was hard to read, so I increased the browser text size. On most sites, this was enough to make it legible. There were a few sites that were almost impossible to read, no matter how large I made the fonts. These were pages that had a dark background and light text. The words danced on the pages and had a halo around them. I confirmed this situation with my eye doctor who has “real” farsightedness. I had never realized how difficult it was to read white text on a black or dark background. It was enough to make me angry because of dizziness I felt after looking at the text.

That experience was six months ago, and today, I went in for a follow up appointment. I received the lucky experience of receiving the dreaded eye drops and the uncontrolled dilation of my eyes. I decided to use the situation to my advantage and perform a vision test on websites.

To confirm my initial thoughts and to add a few:

If you’d like to perform this test on your own, and you’ve never suffered from hyperopia or age-distinguishing presbyopia, I suggest you ask your doctor on your next eye exam for dilation drops and do some web surfing shortly after. This useful test has real world application in web design, as most of the population over 40 has some form of farsightedness, or other eye disorders such as macular degeneration. In making our sites truly accessible, visual markup is as important to consider as our html markup.

~ For my next article, I plan on writing about the effects of Lasik surgery: being intolerable of LCD TVs less than 1080p, and any type of monitor except for a glossy Mac Cinema Display.

posted by emmy on Monday, Apr 21, 2008

Plussing

Back in high school, when the rest of the world was busy playing football, basketball, or something else socially rewarding, I was in the marching band. I don’t regret my decision to join the band. In fact, it has taught me a few lessons that I find useful even today. One such lesson occurred to me yesterday as our design team was discussing the 2008 Web App Summit. One of the highlights of the conference was Jason Fried’s presentation, “The Little Things Matter: Building Web Apps with Laser-Like Attention to Detail”. He spoke about taking something great and making it even better. Walt Disney referred to this concept as “plussing”, a concept that allegedly started with the Jungle Cruise ride. “Walt Disney coined the term plussing as a way of making an idea even better. By telling his workers to plus it, even when they think they nailed it, gave Disney that extra edge when it came to quality animation back in the day. Pixar is a staunch believer in plussing their work. And it shows.” – ward-o-matic.

So the marching band story: In marching band, I was in the drum line. We had an amazing drum captain and were lucky enough to have a band director who had a masters in percussion performance (there is, I learned, a proper technique for playing the triangle, no fooling). The drum captain was extremely disciplined and had that same attention to detail that Jason was talking about. They both worked us hard making sure we were tight as a drum line: that we knew our parts and were together on our double-stroke rolls. We went on to place in every competition we entered and win a good number of them. However, before all this, in one of our first marching competitions, one of the bands before us had what I thought was a killer drum line. They all donned matching Chuck Taylors and had some killer stick tricks. In my heart, I wanted one day to be able to beat that drum line. As it turned out, our one day to beat that drum line was that same day. We very much beat that drum line. We didn’t have tricks as cool or outfits as flashy as they, however, we were much tighter and had paid attention to the details that matter in making a good drum line.

So when you hear people like Jason Fried, Walt Disney and John Laseter talking about plussing, the most important thing to realize is that they focus first on the details that matter. Only after that does it make sense to attempt to make improvements. So when I as an interaction designer ask myself what are the details that matter, I usually answer myself that they involve supporting the work flow of my users. Nobody is going to care whether you’ve timed your expand/collapse effect right if the application as a whole isn’t meeting their basic needs. How do you meet your user’s basic needs? The answer to that question is forthcoming in another article. But here’s a teaser: it involves talking to them.

posted by sam on Wednesday, Apr 16, 2008

More on Lulu and the Information Revolution

My son was too excited to wait any longer, so we uploaded the new cover for his book on lulu.com this morning. After a few changes to meet upload requirements, here’s what I learned—not just about self-publishing, but about what it means for him, and maybe others caught up in the information revolution.

Lesson 1: Read the Instructions. First. It did take some tweaking to get the images the right resolution and size. I think that when I get a printed copy I might have some pixelation on the cover art because I didn’t start out at a high enough resolution. So… read the requirements for cover art before you start. (My son is still giddy, pixelation or no.)

Lesson 2: Keep your source files and experiments. Luckily this one didn’t bite me. I had all me psd files from the experimentation I had done. So when my son asked for changes (adding the lens effect from one of the comps to a different comp), I didn’t have to go back and figure it out.

Lesson 3: Customers don’t always say what they want. I’ve talked about this at length before. My son said he didn’t want the profile to be recognizably… him. But the one he picked has a pretty distinctive “Matthew” outline, though the face is dark. I think there’s a corner of him that very much wants people he knows to recognize his silhouette… but he doesn’t want to tell me that. Or maybe he doesn’t even realize it himself. I run into this kind of discrepancy all the time at work.

Lesson 4: Lulu is really cool. OK, so it’s just an opinion, not a lesson. But as I went through the wizards, I couldn’t help getting excited about what this opportunity represents. From the days from before Gutenberg, when only the very wealthy could ever afford to purchase books, let alone publish them; through the printing revolution where the masses could now afford to buy books (but not publish themselves); to the information revolution, where now you can not only publish online via blogs and websites, but also publish and distribute your own professionally printed material at relatively inexpensive prices. Societal implications aside, it has done wonders for my son’s self-confidence and view of his future. His blogging has a similar effect; he feels he is a contributor to the conversation of life, not just a bystander with nothing to say.

Here is what my son’s Lulu site looks like, with the latest tweaks my son requested to the cover:

How cool is that?

posted by ted on Saturday, Apr 12, 2008

The User-Needs Gap

When occasion permits, which isn’t often, I allow myself to study Bryan Lawson’s excellent book, How Designers Think. I’ve read parts before, but I’m now attempting to read it cover to cover, and about the only way I can do that is to carry it to work and back just about every day.

At lunch last week, I happened to have the book in hand. Coincidentally I flipped ahead to the chapter “A model of design problems,” which is an examination of “generators” (or groups of people) involved in the design process and the constraints they collectively and individually face.

Lawson’s description of the Users group, and particularly his analysis of the gap that exists between this group and the Designers and Clients groups, so completely and perfectly articulates a point I’ve argued repeatedly—that servicing user needs strictly through the voice a client or other mediator presents challenges in understanding and resolving true user needs.

Lawson’s background is in architectural design, but he intended the text to apply to all disciplines within design. As such, there are clearly parallels to user experience design.

Below is an extended excerpt, and above is the diagram referenced in the text:

A great deal of design today is commissioned by clients who are not themselves the users. Public architecture such as hospitals, schools or housing is usually designed by architects who have relatively little contact with the users of their buildings. Industrial design and graphic design are directed at a mass market and are usually commissioned by commercial clients. The traditional image of the designer establishing a personal relationship with a client/user is grossly misleading…. Frequently communication between designers and their users is both indirect and, as John Page has argued, filtered by organisational politics….

In local authorities, for example, both the politicians and administrators may attempt to establish themselves as the communication channel between the designers and the users outside in order to force through policy or maintain a powerful position in the system. On balance such organisational barriers, whatever advantages they give to the client body in terms of increased control over the designer, serve only to make the designer’s task of understanding the problem more difficult. Even if there are not barriers there are what Zeisel (1984) has called ‘gaps’. He referred to ‘paying clients’ and ‘user clients’. He showed that while there might often be good communications between designers and paying clients, both have a gap in their communications with user clients (Fig. 6.1)....

As many young designers must have found on leaving design schools, it is one thing to design for yourself but quite another to design for a real client with personal and institutional prejudices and biases. When that client is not even the prospective user of the design, the problem becomes even more remote. This increasing remoteness of designers from those for whom they design has created the need for user requirement studies. Almost in desperation designers have turned to social and human scientists from ergonomists through architectural psychologists to urban sociologists to tell them what their users actually need. By and large this liaison between design and social science has not been as practically useful as was first hoped. Social science remains largely descriptive while design is necessarily prescriptive, so the psychologists and sociologists have gone on researching and the designers designing, and they are yet to re-educate each other into more genuinely collaborative roles. Meanwhile the communication between the creators and users of environments often remains uncomfortably remote.

I sure hope Lawson addresses this conundrum later in the book, because I’m left wondering what can be done to eliminate this gap—aside from the obvious of just speaking directly with users, which, as Lawson stated, isn’t as easy as it seems given organizational politics. But at least for now I now have a well-articulated text I can refer to the next time this discussion pops up.

posted by cameron on Wednesday, Apr 02, 2008