This will be a brief post, but it's been awhile since I've posted and I wanted to put something up, even if it was mostly an "aside."
THE PROBLEM
I listen to a lot of music and have several thousands of songs in my iTunes library. The problem with having so much music is that it can be hard to organize it and listen to songs I know I like while maintaining variety. If I only pick the songs I know I love, I end up just listening to a smaller and smaller subsection of the total library as it grows, leaving tons of songs sitting idly, unlistened. Yes, this is pretty mundane, but it is a problem I wanted to solve.
THE SOLUTION
One of the great aspects of iTunes is its "Smart Playlist" ability, where you can automatically generate playlists based on a number of factors. To re-introduce songs I hadn't heard in awhile, I created a playlist called "Listen Again." At first, I just set one parameter:
-Songs that I have listened to at least 10 times (showing that I liked them at some point) but haven't listened to in more than 2 months (showing I have forgotten about them).
This started off great, I started hearing songs again that I really enjoyed! But then another issue came up...
THE PROBLEM, PART 2
Some of these songs hadn't been listened to in 2+ months for a reason -- I didn't really like them all that much, or was already sick of them. As I continued to listen to the playlist, when I skipped those songs, they remained in the list, while the songs I liked automatically got booted off the list since they had now been played in the past 2 months. The result is that as time went by, the list became increasingly populated by songs I didn't want to listen to.
THE SOLUTION, PART 2
Well, lo and behold, there is another parameter I can use in iTunes to fix this!
-Songs that have been skipped at least once in the past month (removes songs I don't like, but allows them to return to the list in a month's time in case my taste changes by then).
Fantastic! The songs I skipped immediately got booted off the list. There are still two remaining problems, however...
THE PROBLEM, PARTS 3 & 4
I hadn't considered this until the playlist started cooking, but -- a lot of these songs haven't been played in 2+ months because they are Christmas-related songs! Whoops! There is no easy fix for this -- unless I go back and tag all those songs as belonging to the "Christmas" genre, and exclude that genre from the mix (which I may go and do later).
And then there's the biggest problem, really -- what to do with those songs that this playlist has allowed me to rediscover and enjoy? By virtue of being played, they are now immediately off the playlist! Is there another smart playlist I can create to capture them? This one I don't know how to answer. There may be a way to create a hybrid of songs that appeared on this and also were recently played, but I haven't figured it out yet.
Interestingly, iTunes offers several default smart playlists (recently added, most played, etc.) -- it'd be interesting to see if they expanded their default lists to include some similar concepts. Perhaps sparing users the work I just went through. They have made efforts with their Genius tool to expand your listening (which can also lead to expanding your buying), but I bet there's more that can be done.
Showing posts with label lessons learned. Show all posts
Showing posts with label lessons learned. Show all posts
Monday, April 19, 2010
Friday, December 25, 2009
2k50: An Experimental Project

I've been working on a personal side project called "2k50: The 50 Best Songs of the Decade," which just went up a few days ago. I spent weeks compiling my 50 favorite songs of 2000-2009, and am now posting 5 more every day until December 30 (50-26 are up as of this writing). This project also served as an opportunity to further explore Wordpress as a site management solution. It worked wonderfully, and has given me a lot of insight into how to build sites that clients can update themselves even if they don't know how to code. Furthermore, I even learned a new thing or two about CSS layouts. This may not mean much to those who don't know coding, but I was able to design the site using solely text and CSS-scripted boxes of color -- this is a great technique in general as it not only makes pages load faster, but improves searchability.
Check it out: 2k50: The 50 Best Songs of the Decade
Tuesday, November 24, 2009
Removing ego from design
One of the most difficult aspects of any web design project is reconciling the goals of the designer with the goals of the audience. (And by "designer," I am including everyone involved in the design process, including the client, the design agency, etc.) This is so difficult because the goals of the designer include so many facets -- the client wants to get more money coming in, the agency wants to please the client to get more work in the future, the creative director wants to wow other creative types with his/her vision and maybe win an award, etc. And amidst all of that as well are political power plays, internal arguments, and some "selective hearing" when it comes to research and statistics that don't support their individual goals. (I speak of no particular agency or experience here -- these are accumulated observations.)
The whole rigmarole can be a bit exhausting and it is very easy to get caught up in the "designer" side of things. It all seems quite serious - to step back and think about the fact that people can get into shouting matches over a single word on a website (I've seen it happen) - I don't know, it seems like the perspective is off. People take these battles very personally, and fight for things because they want them, or because it means something to them, and it's easy to forget that all that really matters is whether or not somebody going to your website is going to have a good experience.
This is why I've found it so valuable, in my own work, to start viewing the work I do as completely separate from who I am. Much of what I design is based on research - knowing what works and what doesn't - but there is not enough research in the world to make every decision foolproof. If something was a subjective call, or I designed based on a hunch, and someone takes issue, I'll explain my viewpoint but recognize that if I don't have an empirical study to back it up, it's really just an opinion.
In addition, when working in a group environment, letting go of ego can make the brainstorming and overall creative process a lot more open. An idea prefaced with "this may be stupid, but..." could end up being the best idea of the day, while one that someone thinks is surefire could be quickly tossed out as the details are thought out further. When ego is involved, the initial "stupid" idea might never be brought up for fear of a negative reaction, while the "surefire" idea might be fought for tooth-and-nail to the detriment of better options. Letting go of ego - where you perceive comments about your idea as a comments about you - switches the emphasis to the ideas, not the people.
This ends up being quite liberating in the long run, because not only does it make it easier to edit and adapt your design as more learnings come in, it also makes you focus more on what will best serve the end user. And in the end, that's really the truest measure of a successful design.
In addition, when working in a group environment, letting go of ego can make the brainstorming and overall creative process a lot more open. An idea prefaced with "this may be stupid, but..." could end up being the best idea of the day, while one that someone thinks is surefire could be quickly tossed out as the details are thought out further. When ego is involved, the initial "stupid" idea might never be brought up for fear of a negative reaction, while the "surefire" idea might be fought for tooth-and-nail to the detriment of better options. Letting go of ego - where you perceive comments about your idea as a comments about you - switches the emphasis to the ideas, not the people.
This ends up being quite liberating in the long run, because not only does it make it easier to edit and adapt your design as more learnings come in, it also makes you focus more on what will best serve the end user. And in the end, that's really the truest measure of a successful design.
Labels:
brainstorming,
collaboration,
design,
lessons learned,
process,
project management
Tuesday, March 10, 2009
Trust and faith in design
It's a cliche to make fun of older generations and their discomfort with technology, but that stereotypical technophobia is really just an extreme version of something all of us probably feel at some point or another: a lack of trust and faith in the system we are using.
What does this button do?
I remember having someone ask me, "What do I do to submit the form? Do I press the submit button?" The answer, to most of us, is "yes, duh." But what if the question is less clear? Navigational terms don't match what you thought you'd find. Something you thought was a free trial asks for your credit card and doesn't explain why. A link that seemed obvious takes you to a completely unexpected page or site. In each case, the design is playing fast and loose with the user's trust and faith, and as a result, is probably failing the user's needs.
Anticipate the next step
Good design anticipates what the user will want. On your homepage, offer links to the things your visitors most likely will want. Look at the search terms people use to find things on your site, and make sure your navigational terms match them. Whenever you ask a user for information, explain why you want it and how it will be used.
Explain yourself
One place that I frequently see abused is the "contact us" page -- many sites will ask for name, address, phone number, email, sometimes even fax number and company, and in worst-case scenarios, they'll even tack on some "survey" type questions -- even if all you wanted to do was maybe email them to ask about the release date of an upcoming product. In that scenario, literally the only piece of information the company actually needs is your email address. So why ask for the moon? Is it because your designer just used a "contact us" template and didn't really think about what that means for the user? Is it because you are adding me to a database you are going to sell to third parties? And even if all you do ask for is my email address, will you start sending me unwanted email newsletters without asking? Tell the user up front, and let them make the informed decision. (Even better, in this scenario, you could save the user and yourself time by having just clearly listed the product release date on your site in the first place.)
Expect questions, and provide answers
One thing I try to do when starting any project is just write down a list of questions I think a user/visitor may have, based on the type of site/product and the customer base. I try not to get overly specific but the questions should not just be the broad ones either -- for example, on a shoe site, I wouldn't write out questions about a particular pair of shoes, but I might write out questions about broader types of shoes, or questions that might apply to any individual pair of shoes.
Prioritize and group logically
From there, I try to group the questions logically, and see if they align to particular terms. If possible, prioritize the questions as well, and make it easier to find the answers to those more essential questions. This is also where some statistical data can come in handy -- search terms used, frequency of visits to particular areas of a site, volume of support emails/calls about particular topics. Maybe half the visitors to your site are just trying to find your address, and already know all about your product/service. You could have a beautiful, highly usable presentation of your product line, but if that address is hard to find, you are failing half your audience from the start.
I've found that structuring a website around this is a good way to meet user's needs, and a lot of this work can inform other decisions down the line, and make it easier to work in changes/new ideas -- just follow a mini-version of these steps (asking questions, grouping them, working out logical answers) and see if your architecture already accommodates these changes or if you need to restructure.
By anticipating everything the user will want, and providing easy answers to key questions and presenting them at logical points, you build that trust and faith. You're more likely to have a happy customer, and you reduce anxiety.
What does this button do?
I remember having someone ask me, "What do I do to submit the form? Do I press the submit button?" The answer, to most of us, is "yes, duh." But what if the question is less clear? Navigational terms don't match what you thought you'd find. Something you thought was a free trial asks for your credit card and doesn't explain why. A link that seemed obvious takes you to a completely unexpected page or site. In each case, the design is playing fast and loose with the user's trust and faith, and as a result, is probably failing the user's needs.
Anticipate the next step
Good design anticipates what the user will want. On your homepage, offer links to the things your visitors most likely will want. Look at the search terms people use to find things on your site, and make sure your navigational terms match them. Whenever you ask a user for information, explain why you want it and how it will be used.
Explain yourself
One place that I frequently see abused is the "contact us" page -- many sites will ask for name, address, phone number, email, sometimes even fax number and company, and in worst-case scenarios, they'll even tack on some "survey" type questions -- even if all you wanted to do was maybe email them to ask about the release date of an upcoming product. In that scenario, literally the only piece of information the company actually needs is your email address. So why ask for the moon? Is it because your designer just used a "contact us" template and didn't really think about what that means for the user? Is it because you are adding me to a database you are going to sell to third parties? And even if all you do ask for is my email address, will you start sending me unwanted email newsletters without asking? Tell the user up front, and let them make the informed decision. (Even better, in this scenario, you could save the user and yourself time by having just clearly listed the product release date on your site in the first place.)
Expect questions, and provide answers
One thing I try to do when starting any project is just write down a list of questions I think a user/visitor may have, based on the type of site/product and the customer base. I try not to get overly specific but the questions should not just be the broad ones either -- for example, on a shoe site, I wouldn't write out questions about a particular pair of shoes, but I might write out questions about broader types of shoes, or questions that might apply to any individual pair of shoes.
Prioritize and group logically
From there, I try to group the questions logically, and see if they align to particular terms. If possible, prioritize the questions as well, and make it easier to find the answers to those more essential questions. This is also where some statistical data can come in handy -- search terms used, frequency of visits to particular areas of a site, volume of support emails/calls about particular topics. Maybe half the visitors to your site are just trying to find your address, and already know all about your product/service. You could have a beautiful, highly usable presentation of your product line, but if that address is hard to find, you are failing half your audience from the start.
I've found that structuring a website around this is a good way to meet user's needs, and a lot of this work can inform other decisions down the line, and make it easier to work in changes/new ideas -- just follow a mini-version of these steps (asking questions, grouping them, working out logical answers) and see if your architecture already accommodates these changes or if you need to restructure.
By anticipating everything the user will want, and providing easy answers to key questions and presenting them at logical points, you build that trust and faith. You're more likely to have a happy customer, and you reduce anxiety.
Labels:
design,
IA,
lessons learned,
organization,
process,
usability
Thursday, February 5, 2009
Beware the permanent brainstorm
There is a particular type of person out there who is very creative, who loves to come up with new ideas, who gets excited about a new concept they think could be really successful or beneficial. These people are vital -- without them, many (if not all) of the big ideas that have changed our lives would never have happened.
But there is one flaw that often comes hand-in-hand with this level of creativity and brainstorming. For every Steve Jobs (Apple), Bill Gates (Microsoft), and Mark Zuckerberg (Facebook), there is that friend you have who is convinced that adding zipper pockets to suspenders is the next big thing. Or maybe that was last week, and now they're pitching tiny umbrellas for cellphones. In any case, their mind seems to always be working, but never carrying through the thoughts to something that is not only a great idea, but one that they can (and do) actually implement. I call this the danger of the "permanent brainstorm."
Those examples are extreme, but I believe there can be a real danger to focusing so much on the brainstorming and "ideating" portion of a project that you never get off the ground and develop something real.
For a more grounded example, consider a project where a company wants to come up with a new marketing website. All they know at first is that they want to target a new audience that they don't currently speak to. The brainstorming phase begins, and the team narrows it down to one particular concept.
This could go two ways -- the team could further focus in, delineate their ideas, and develop them into a site and get it live.
Or they could just keep brainstorming. What if we broaden it to include this other audience as well? What if we focus more on the interactive games? What if we switch from an edgy/rough look to a clean/modern look? And then after trying all those alternatives, they keep spinning around to other ideas. A hot new competitor site shows up halfway through the project, and they want to take some of the competitor's ideas and re-think the original goal.
You get the picture. The ideas keep coming, the project keeps changing, people second-guess their original ideas and the whole thing continues to mutate and shift even as it's supposed to be nearing its completion. The budget has swelled, the timeline has been shot, and corners are being cut that could make the difference between something great and simple and something overly ambitious and complicated.
Of course, this is not to say that brainstorming is bad - as I mentioned before, it's the brainstormers who come up with all the big new ideas. The key is knowing when to shift away from generating more ideas and shift toward refining and implementing your original idea. It can be scary sometimes to do this, but it's all about putting a stake in the ground and saying "this phase is done, we need to move on to the next phase, or else we're going to get stuck."
That can be a hard thing to do. Nobody likes the idea of setting something in stone when they are anything less than 100% sure of it -- and rarely is any new idea a 100% bet. But this is where handy metaphors and sayings run short -- unless you are engraving tombstones, you're not literally setting things in stone. You can make changes later on if need be -- it's just important to respect that those changes should be based on fully reasoned thinking, not whims, or a dream you had last night, or what your 5 year old said when he saw a mock-up of the project.
Be excited. Think wildly. But recognize that as part of any project, brainstorming is just step one. It takes a lot of work to turn a good idea into a good product, and you'll never get to a successful end if you never leave step one.
But there is one flaw that often comes hand-in-hand with this level of creativity and brainstorming. For every Steve Jobs (Apple), Bill Gates (Microsoft), and Mark Zuckerberg (Facebook), there is that friend you have who is convinced that adding zipper pockets to suspenders is the next big thing. Or maybe that was last week, and now they're pitching tiny umbrellas for cellphones. In any case, their mind seems to always be working, but never carrying through the thoughts to something that is not only a great idea, but one that they can (and do) actually implement. I call this the danger of the "permanent brainstorm."
Those examples are extreme, but I believe there can be a real danger to focusing so much on the brainstorming and "ideating" portion of a project that you never get off the ground and develop something real.
For a more grounded example, consider a project where a company wants to come up with a new marketing website. All they know at first is that they want to target a new audience that they don't currently speak to. The brainstorming phase begins, and the team narrows it down to one particular concept.
This could go two ways -- the team could further focus in, delineate their ideas, and develop them into a site and get it live.
Or they could just keep brainstorming. What if we broaden it to include this other audience as well? What if we focus more on the interactive games? What if we switch from an edgy/rough look to a clean/modern look? And then after trying all those alternatives, they keep spinning around to other ideas. A hot new competitor site shows up halfway through the project, and they want to take some of the competitor's ideas and re-think the original goal.
You get the picture. The ideas keep coming, the project keeps changing, people second-guess their original ideas and the whole thing continues to mutate and shift even as it's supposed to be nearing its completion. The budget has swelled, the timeline has been shot, and corners are being cut that could make the difference between something great and simple and something overly ambitious and complicated.
Of course, this is not to say that brainstorming is bad - as I mentioned before, it's the brainstormers who come up with all the big new ideas. The key is knowing when to shift away from generating more ideas and shift toward refining and implementing your original idea. It can be scary sometimes to do this, but it's all about putting a stake in the ground and saying "this phase is done, we need to move on to the next phase, or else we're going to get stuck."
That can be a hard thing to do. Nobody likes the idea of setting something in stone when they are anything less than 100% sure of it -- and rarely is any new idea a 100% bet. But this is where handy metaphors and sayings run short -- unless you are engraving tombstones, you're not literally setting things in stone. You can make changes later on if need be -- it's just important to respect that those changes should be based on fully reasoned thinking, not whims, or a dream you had last night, or what your 5 year old said when he saw a mock-up of the project.
Be excited. Think wildly. But recognize that as part of any project, brainstorming is just step one. It takes a lot of work to turn a good idea into a good product, and you'll never get to a successful end if you never leave step one.
Labels:
brainstorming,
lessons learned,
process,
project management
Monday, February 2, 2009
michaelhisten.com 3.0

It wasn't that long ago that I did a redesign of my portfolio website, www.michaelhisten.com. It was not a very dramatic change, it mostly focused on enhancing the content and involved adding my beloved color switcher. But as I started writing more in this blog, I realized I wasn't listening to a lot of my own advice when it came to my own site.
I was concerned about a few things -- one, the level of simplicity of the old site was so extreme that I was worried people would assume that's all I could do. To make up for that, I've ditched the "no graphics" concept and used some imagery and gradients, including using the font FD Helwoodica, an all-lowercase distressed take on my favorite font, Helvetica.
But perhaps my biggest issue with my site was that I was falling victim to that perennial trap -- thinking my content was more interesting than it was. Some site statistics bore this out, but basically, people didn't bother reading much of any of the content pages and just went straight for the portfolio section. To top it off, my portfolio examples did not have thumbnail imagery to give you a preview until you clicked on the name of a project. This, combined with some research into how other designers out there are presenting their profiles, led me to embrace the idea of a one-page website.
Yup, just one page, there's nothing more than what you see when you land there. Of course, clicking thumbnails gives you larger views (much larger than before -- more than twice as large, in fact) of each project, but now all those projects are front and center. I think the end result is that people will get a quick glimpse of what I can do, and they can then read a little bit in the area at the bottom of the page, and then I encourage them to contact me for more. If they want to read more about me and my design philosophy, the blog is right here. All in all, I'm very happy with the update.
Oh, and that color switcher is still there -- I still love the idea of giving visitors a little interactivity!
Labels:
applied design,
design,
lessons learned,
my work
Wednesday, January 21, 2009
"In a perfect world..."
Most design agencies are structured into silos, with people specialized in different aspects of the design and management. I wrote about some of the problems this can create in an earlier post, but there's another aspect to specialization: we expect people in later stages of the process to be able to fully realize the ideas we have as designers earlier on in the process.
I have seen too many times an idea get implemented either without the interaction/design fully realized, or just plain implemented wrong. The results are almost always disappointing, and sometimes that seemingly small difference between well-polished and rough-around-the-edges is the difference between easy and frustrating. A poorly-implemented great idea is often worse than a well-implemented mediocre idea.
This is a tough situation to deal with, because often you won't know if the idea fails in implementation until it has actually been implemented, and at that point it may be too late to try an alternate approach. And even if you know it is risky, sometimes it is worth the risk. My best suggestions?
Make a sample version/functional prototype
Try to create a mini version of your big idea. Problems may rear their head that you didn't expect, while things you expected to be difficult may work out smoothly after all. In either case, it should tell you if it is worth exploring further or abandoning.
Do it yourself
You can't always do this in a large agency (in fact, you probably rarely can), but one of the benefits of working small or being an all-in-one freelancer is that you know fully the skills and knowledge of every one at every step -- because it might be you in every role. You may not know every single aspect of how to create something in advance, but it's important that you at least know how to learn everything needed, and that you can do it within the scope of your project.
Have a well-thought-out Plan B
Sometimes your Plan B may just be an earlier brainstorm that wasn't fully realized, but just as you should design for user failure, you should design for designer failure too. Unexpected obstacles are common, and the more ready you are with an alternate approach, the more likely your end result will be successful. Trying to patch up a sinking ship that has been battered and bruised may be a mistake -- sometimes you just need to scratch that ship and build another one. If you've got the blueprints for the second ship available already, you'll have a head start.
I've half-joked before that I want to become a "reality consultant" -- someone who can look at all the big ideas and plans and offer some cold hard reality about what is or isn't achievable, what will be simple or difficult, and ultimately where energy should be spent to really ensure something good in the end. But until that is a real job, we can all be our own reality consultants and be ready to adapt if our "perfect world" vision doesn't come to fruition.
I have seen too many times an idea get implemented either without the interaction/design fully realized, or just plain implemented wrong. The results are almost always disappointing, and sometimes that seemingly small difference between well-polished and rough-around-the-edges is the difference between easy and frustrating. A poorly-implemented great idea is often worse than a well-implemented mediocre idea.
This is a tough situation to deal with, because often you won't know if the idea fails in implementation until it has actually been implemented, and at that point it may be too late to try an alternate approach. And even if you know it is risky, sometimes it is worth the risk. My best suggestions?
Make a sample version/functional prototype
Try to create a mini version of your big idea. Problems may rear their head that you didn't expect, while things you expected to be difficult may work out smoothly after all. In either case, it should tell you if it is worth exploring further or abandoning.
Do it yourself
You can't always do this in a large agency (in fact, you probably rarely can), but one of the benefits of working small or being an all-in-one freelancer is that you know fully the skills and knowledge of every one at every step -- because it might be you in every role. You may not know every single aspect of how to create something in advance, but it's important that you at least know how to learn everything needed, and that you can do it within the scope of your project.
Have a well-thought-out Plan B
Sometimes your Plan B may just be an earlier brainstorm that wasn't fully realized, but just as you should design for user failure, you should design for designer failure too. Unexpected obstacles are common, and the more ready you are with an alternate approach, the more likely your end result will be successful. Trying to patch up a sinking ship that has been battered and bruised may be a mistake -- sometimes you just need to scratch that ship and build another one. If you've got the blueprints for the second ship available already, you'll have a head start.
I've half-joked before that I want to become a "reality consultant" -- someone who can look at all the big ideas and plans and offer some cold hard reality about what is or isn't achievable, what will be simple or difficult, and ultimately where energy should be spent to really ensure something good in the end. But until that is a real job, we can all be our own reality consultants and be ready to adapt if our "perfect world" vision doesn't come to fruition.
Monday, October 20, 2008
Cut cut cut!
For many people who have websites, this is a sad but almost undoubtedly true fact: No one wants to read what you have to say.
First, let me give a caveat - if you have a blog or some opinion-based or news-based site, chances are people that visit your site do actually want to read what you have to say. But, most sites do not fall into that category. Also, this is not to say that visitors won't read anything at all -- but all most visitors want to do is find a specific piece of information very quickly and move on. Nobody sets out looking for self-hyping or vague filler, and any amount of that present on your site is an obstacle to their goal.
What I've said in previous posts about being self-aware or maintaining objectivity applies strongly here -- do you read websites? When you search for something and find a relevant hit, do you explore a site, patiently sit through a flash intro, and read paragraphs of marketing copy? The answer is probably no. So why would you expect your visitors to do that?
I've seen cases where I get the distinct impression a client is afraid that not having a lot of pages and a lot of text will send a message to the visitor that there is a lack of substance there. This couldn't be further from the truth. A trim, efficient, streamlined site that is light on fluff but clear and direct on content will send a message that you know what you're talking about, you know what the visitor wants, and you don't waste time and energy on the superfluous. Probably the only commodity more valuable than money is time, and no one wants their time wasted.
So I'm going to listen to my own advice and keep this short. Some simple rules:
First, let me give a caveat - if you have a blog or some opinion-based or news-based site, chances are people that visit your site do actually want to read what you have to say. But, most sites do not fall into that category. Also, this is not to say that visitors won't read anything at all -- but all most visitors want to do is find a specific piece of information very quickly and move on. Nobody sets out looking for self-hyping or vague filler, and any amount of that present on your site is an obstacle to their goal.
What I've said in previous posts about being self-aware or maintaining objectivity applies strongly here -- do you read websites? When you search for something and find a relevant hit, do you explore a site, patiently sit through a flash intro, and read paragraphs of marketing copy? The answer is probably no. So why would you expect your visitors to do that?
I've seen cases where I get the distinct impression a client is afraid that not having a lot of pages and a lot of text will send a message to the visitor that there is a lack of substance there. This couldn't be further from the truth. A trim, efficient, streamlined site that is light on fluff but clear and direct on content will send a message that you know what you're talking about, you know what the visitor wants, and you don't waste time and energy on the superfluous. Probably the only commodity more valuable than money is time, and no one wants their time wasted.
So I'm going to listen to my own advice and keep this short. Some simple rules:
- Be ruthless and be willing to edit - because your visitors are ruthless with the "back" button and will ditch your page in seconds if they don't see what they want right away.
- Every piece of content you write needs to deliver vital information that the visitor wants to read, otherwise you need to get rid of it.
- Be willing to delete entire pages if their content is unnecessary or so light it could easily be combined with other pages.
- Don't be long-winded; write concisely.
- And perhaps underpinning all of this: don't be emotionally attached to any of your content, or you'll cheat yourself out of making the best site for your visitors.
Labels:
IA,
lessons learned,
rules for design,
usability
Friday, September 5, 2008
How much can you know?
Confession time: I don't know everything. I know, you're shocked. But seriously, I was talking with a couple friends who are in web design, shooting the shit about various techniques and CSS and JavaScript (you know you're a nerd when...), and at one point I blurted out, "sometimes I feel like I don't know nearly as much as I should and I'm just making it up as I go along." My friend, who has had a few years more experience than I have, didn't miss a beat: "You just described everyone in our industry."
That was comforting, and probably true, as there are so many different things any individual could know in the field of web design that it's pretty much impossible to expect anyone to know it all. I'd argue that the greatest advancements in design have come from people who were making it up as they went along.
It seems to me that a good designer -- or perhaps more specifically a coder/developer -- doesn't necessarily need to know how to do every idea or assignment that comes their way. They just need to know how to LEARN how to do it.
I'll give an example of a recent project I did. There were a number of techniques I wanted to do, yet didn't know specifically how to do them off the top of my head. Among them: tabbed content within a page (rather than clicking to a new page for every tab), an automatic rotating image slideshow, a form that calculated various fees and totals in real time as you select different options, and a method to display content only if it exists on the server and how to present an alternative if it doesn't -- these are all things I had never done before, but knew I could figure them out, and I managed all of them successfully. Admittedly these are smaller features, and allowed me to learn in chunks rather than being presented with something as complex as "build us an online stock trading system." I felt confident tackling them because I at least knew enough about the various languages and techniques involved to know that they were all achievable, and as I worked on them, I learned more about other underlying concepts that will help me with the next new idea/design.
I think too many people, when given a challenge they don't already know how to complete, simply give up and think it's outside of their abilities. This is rarely true. There are still coding languages and techniques that seem so complex to me that I can't help but feel intimidated -- but breaking them down, and remembering that everyone who is now an "expert" was once in my shoes as well, has made me realize that knowing "how to know" is a skill that lets you do just about anything.
That was comforting, and probably true, as there are so many different things any individual could know in the field of web design that it's pretty much impossible to expect anyone to know it all. I'd argue that the greatest advancements in design have come from people who were making it up as they went along.
It seems to me that a good designer -- or perhaps more specifically a coder/developer -- doesn't necessarily need to know how to do every idea or assignment that comes their way. They just need to know how to LEARN how to do it.
I'll give an example of a recent project I did. There were a number of techniques I wanted to do, yet didn't know specifically how to do them off the top of my head. Among them: tabbed content within a page (rather than clicking to a new page for every tab), an automatic rotating image slideshow, a form that calculated various fees and totals in real time as you select different options, and a method to display content only if it exists on the server and how to present an alternative if it doesn't -- these are all things I had never done before, but knew I could figure them out, and I managed all of them successfully. Admittedly these are smaller features, and allowed me to learn in chunks rather than being presented with something as complex as "build us an online stock trading system." I felt confident tackling them because I at least knew enough about the various languages and techniques involved to know that they were all achievable, and as I worked on them, I learned more about other underlying concepts that will help me with the next new idea/design.
I think too many people, when given a challenge they don't already know how to complete, simply give up and think it's outside of their abilities. This is rarely true. There are still coding languages and techniques that seem so complex to me that I can't help but feel intimidated -- but breaking them down, and remembering that everyone who is now an "expert" was once in my shoes as well, has made me realize that knowing "how to know" is a skill that lets you do just about anything.
Monday, August 25, 2008
Learning to be self-aware
Jumping off of a concept from my last post about common sense usability, one of the most important things a good designer (particularly in the usability field) needs to be is self-aware. In general, people are extremely un-self-aware. Concepts of time are often way off (anecdotally, I remember my mother, in 2007, referring to Princess Diana's death as having been "a couple years ago," when in fact it had been ten years), and we tend to conflate memories into events that either didn't happen or occurred in separate times and places.
This is particularly an issue when working on web design. Very few people stop to ask of themselves the kinds of questions that are absolutely vital for good design. Where does my eye go first? This can help you organize the layout via information hierarchy. Am I moving my mouse to follow my eye? This may suggest good places to have hover states. Do I quickly click from page to page until I find what I want or do I scan a page fully before making my first click? This could inform your approach to site navigation. How many seconds does it REALLY take for me before I get annoyed at not finding what I want? This may determine whether a long-loading Flash module or graphics-heavy page is worth the sacrifice in loading time it may cost.
As important as it is to do proper testing and remember that, as the designer, you are rarely the intended audience, and you certainly know far more about the site than the average visitor will, you can still glean a lot of information just by carefully noting your own reactions -- even reactions to sites that have nothing to do with the one you are working on.
This is also helpful for someone who is not in design, but may need to work with a designer on a project. Are you working at a small organization that needs a better website? You'll be better able to get a top-notch end product if you are able to articulate clearly what your needs are, and you'll be better able to stand up for good usability practices if you end up working with a designer who has a great eye but perhaps a poor sense of usability. Think about your own site. Are there places you (or your visitors) frequently go to on your site that are buried? Is valuable home page real estate being devoted to unsupported or barely visited portions of your site? What aspects of your own site or your competitors' sites frustrate you and what do you find pleasing?
Asking these questions and being aware of your emotional state (by which I mean, happy, annoyed, indifferent, etc.) while browsing can help you pinpoint the design aspects that work and those that don't. So next time you find yourself frustrated by a website, stop for a second and think about what exactly is bothering you, and maybe even write it down. Similarly, next time you enter a site and find the information you want right away, think about what they did right -- this is often just as important or more important than finding the negatives, and frequently we don't even notice when something is done right.
But even when trying these exercises, keep in mind that there will undoubtedly be things you are doing that you are not realizing. It may sharpen your instincts, but for any larger scale project, you'll still need to take that critical look and apply it to other users to truly find underlying patterns and problems.
This is particularly an issue when working on web design. Very few people stop to ask of themselves the kinds of questions that are absolutely vital for good design. Where does my eye go first? This can help you organize the layout via information hierarchy. Am I moving my mouse to follow my eye? This may suggest good places to have hover states. Do I quickly click from page to page until I find what I want or do I scan a page fully before making my first click? This could inform your approach to site navigation. How many seconds does it REALLY take for me before I get annoyed at not finding what I want? This may determine whether a long-loading Flash module or graphics-heavy page is worth the sacrifice in loading time it may cost.
As important as it is to do proper testing and remember that, as the designer, you are rarely the intended audience, and you certainly know far more about the site than the average visitor will, you can still glean a lot of information just by carefully noting your own reactions -- even reactions to sites that have nothing to do with the one you are working on.
This is also helpful for someone who is not in design, but may need to work with a designer on a project. Are you working at a small organization that needs a better website? You'll be better able to get a top-notch end product if you are able to articulate clearly what your needs are, and you'll be better able to stand up for good usability practices if you end up working with a designer who has a great eye but perhaps a poor sense of usability. Think about your own site. Are there places you (or your visitors) frequently go to on your site that are buried? Is valuable home page real estate being devoted to unsupported or barely visited portions of your site? What aspects of your own site or your competitors' sites frustrate you and what do you find pleasing?
Asking these questions and being aware of your emotional state (by which I mean, happy, annoyed, indifferent, etc.) while browsing can help you pinpoint the design aspects that work and those that don't. So next time you find yourself frustrated by a website, stop for a second and think about what exactly is bothering you, and maybe even write it down. Similarly, next time you enter a site and find the information you want right away, think about what they did right -- this is often just as important or more important than finding the negatives, and frequently we don't even notice when something is done right.
But even when trying these exercises, keep in mind that there will undoubtedly be things you are doing that you are not realizing. It may sharpen your instincts, but for any larger scale project, you'll still need to take that critical look and apply it to other users to truly find underlying patterns and problems.
Tuesday, July 15, 2008
The Hurdle of Visuals
You've worked your heart out on a project, coming up with a great site structure, smart placement of content on each page, and a solid outer shell of basic fonts and colors, and you present the work to your client. What's the first thing you hear? "I don't like the photos." Many of us have been there before. After all your hard work, the only thing the client can see are the images (which usually they have provided and you have no control over). How do you get people to look at the right things?
One of the biggest challenges facing anyone in the field of information architecture/interaction design/usability (etc.) is the careful line of visual fidelity. Human beings are naturally extremely visual people. Look at the stats for most product sites, and you'll probably find that the most visited portions are photo galleries and other high-visual/low-text areas.
Unfortunately, strictly speaking, much of the work in this field is not particularly visual. Yes, a good information architect lays out where things lay on the page, but in many (most?) situations they are not the ones creating the graphics files, choosing colors and fonts, writing copy, taking (and choosing) photographs, etc. One of my favorite sayings comes from the field of film, and basically states, "a good editor has done his job when nobody notices his work." The point being, a bad editing job is going to be obvious and annoying, but a good editing job is going to be completely overlooked as the viewer is immersed in the film itself rather than the editing. The same goes for many user experiences. People notice when it's frustrating, but a seamless, intuitive experience lets the user focus on the content, not the process.
I bring this topic up now because I am wrestling with the best way to present work, both at an internal wireframe level and at a client-facing presentation level. I remember a project at my last job where five members of my team were independently presenting wireframes to a client -- the idea was to treat it almost like a pitch meeting as if we were different firms rather than just members of the same team. It was a fun challenge as we all got along well, but the differences in our approaches were stark. Some of us made ultra-simple wireframes, just black and white boxes with Arial text. Others added a layer of polish with gradients, nicer fonts, and drop-shadows. Some used photographs, others used representative "silhouette" images, some just used placeholder boxes. Before our client presentation, our boss looked across our examples and decided we shouldn't be biasing the client toward or against any design based on the fidelity of the wireframes. Let the IA speak for itself.
This posed a problem for me -- my design was very sparse, and was intended to highlight the imagery of the product itself by minimizing navigation and text. Removing images meant that there were large areas of blank space now in my presentation. Would the client be able to "project" the imagery in their own mind and see how it looked? Would she end up preferring a presentation that was heavy on text and navigation because there was no imagery competing for visual attention?
It's a tricky question. My boss could have suggested the opposite -- everyone HAD to add photos and gloss up their wireframes. But then would the client focus on images chosen rather than the IA? How do you make a client look at the right things? And on that note, how do you get your co-workers to even look at the right things when presenting internally?
The answer all depends largely on who your audience is. You could have a super-savvy client who can envision the finished product just from a wireframe, or you could have a client who sees a wireframe and dismisses the work entirely because it doesn't look like the polished, finished sites they're used to seeing. And on an internal level, particularly in firms where different people work on different aspects of sites -- such as an IA building wireframes and a designer creating the actual visuals -- you can find yourself stepping on toes. Does a high-fidelity wireframe make the designer feel like you're dictating their job? Conversely, does a low-fidelity wireframe make you look sloppy? Can you make something that projects a polished, dynamic end product while still respecting that technically, the visual polish is someone else's job?
In general, I think I tend to over-design wireframes and under-design comps. Most of my wireframing is in an agency environment, where it helps to have nice fonts and clean lines, but inserting sample imagery and venturing into the land of colors and graphics are going too far. Meanwhile, as a freelance designer, clients often can't see the finished product if they don't have imagery in place as well, although I think it's best to use different imagery from what they might see on their live site today, just to underscore that the imagery may change frequently but the structure and visual design will be constant.
One of the biggest challenges facing anyone in the field of information architecture/interaction design/usability (etc.) is the careful line of visual fidelity. Human beings are naturally extremely visual people. Look at the stats for most product sites, and you'll probably find that the most visited portions are photo galleries and other high-visual/low-text areas.
Unfortunately, strictly speaking, much of the work in this field is not particularly visual. Yes, a good information architect lays out where things lay on the page, but in many (most?) situations they are not the ones creating the graphics files, choosing colors and fonts, writing copy, taking (and choosing) photographs, etc. One of my favorite sayings comes from the field of film, and basically states, "a good editor has done his job when nobody notices his work." The point being, a bad editing job is going to be obvious and annoying, but a good editing job is going to be completely overlooked as the viewer is immersed in the film itself rather than the editing. The same goes for many user experiences. People notice when it's frustrating, but a seamless, intuitive experience lets the user focus on the content, not the process.
I bring this topic up now because I am wrestling with the best way to present work, both at an internal wireframe level and at a client-facing presentation level. I remember a project at my last job where five members of my team were independently presenting wireframes to a client -- the idea was to treat it almost like a pitch meeting as if we were different firms rather than just members of the same team. It was a fun challenge as we all got along well, but the differences in our approaches were stark. Some of us made ultra-simple wireframes, just black and white boxes with Arial text. Others added a layer of polish with gradients, nicer fonts, and drop-shadows. Some used photographs, others used representative "silhouette" images, some just used placeholder boxes. Before our client presentation, our boss looked across our examples and decided we shouldn't be biasing the client toward or against any design based on the fidelity of the wireframes. Let the IA speak for itself.
This posed a problem for me -- my design was very sparse, and was intended to highlight the imagery of the product itself by minimizing navigation and text. Removing images meant that there were large areas of blank space now in my presentation. Would the client be able to "project" the imagery in their own mind and see how it looked? Would she end up preferring a presentation that was heavy on text and navigation because there was no imagery competing for visual attention?
It's a tricky question. My boss could have suggested the opposite -- everyone HAD to add photos and gloss up their wireframes. But then would the client focus on images chosen rather than the IA? How do you make a client look at the right things? And on that note, how do you get your co-workers to even look at the right things when presenting internally?
The answer all depends largely on who your audience is. You could have a super-savvy client who can envision the finished product just from a wireframe, or you could have a client who sees a wireframe and dismisses the work entirely because it doesn't look like the polished, finished sites they're used to seeing. And on an internal level, particularly in firms where different people work on different aspects of sites -- such as an IA building wireframes and a designer creating the actual visuals -- you can find yourself stepping on toes. Does a high-fidelity wireframe make the designer feel like you're dictating their job? Conversely, does a low-fidelity wireframe make you look sloppy? Can you make something that projects a polished, dynamic end product while still respecting that technically, the visual polish is someone else's job?
In general, I think I tend to over-design wireframes and under-design comps. Most of my wireframing is in an agency environment, where it helps to have nice fonts and clean lines, but inserting sample imagery and venturing into the land of colors and graphics are going too far. Meanwhile, as a freelance designer, clients often can't see the finished product if they don't have imagery in place as well, although I think it's best to use different imagery from what they might see on their live site today, just to underscore that the imagery may change frequently but the structure and visual design will be constant.
Tuesday, July 1, 2008
A Beginning
This is not the first time I've attempted to start a blog. I had one going for about 4 entries several months ago, where I was trying to present usability and design advice in a Jakob Nielsen-esque "this is how you should do things." But I realized rather quickly that limiting myself to usability design (and then requiring myself to write in a prescriptive manner) was far too restrictive.
So I'm letting myself branch out a bit. I want to focus on talking about design, but not limit myself. I tend to let my mind wander on to vaguely philosophical topics and I don't want to stop myself from talking about those things if I think others may find it interesting. And, more importantly, I don't want to write from a "do things this way" point of view because, while I have skill and experience, I don't know everything, and I don't think it's particularly responsible of me to claim that my ways of thinking will work for others.
I'm also letting myself (temporarily) disregard the visual design of this blog. I spent some time customizing templates the last time I tried to make a blog and, in retrospect, I realize I was valuing style over content. Maybe that's the first lesson I learn as a blogger: a good-looking nothing is still nothing.
So I'm letting myself branch out a bit. I want to focus on talking about design, but not limit myself. I tend to let my mind wander on to vaguely philosophical topics and I don't want to stop myself from talking about those things if I think others may find it interesting. And, more importantly, I don't want to write from a "do things this way" point of view because, while I have skill and experience, I don't know everything, and I don't think it's particularly responsible of me to claim that my ways of thinking will work for others.
I'm also letting myself (temporarily) disregard the visual design of this blog. I spent some time customizing templates the last time I tried to make a blog and, in retrospect, I realize I was valuing style over content. Maybe that's the first lesson I learn as a blogger: a good-looking nothing is still nothing.
Subscribe to:
Posts (Atom)