You are viewing interimlover

UX FAQ

Feb. 16th, 2009 | 04:31 pm
music: Lindstrøm - Where You Go I Go Too | Powered by Last.fm

In the last few weeks, I've been asked questions about the field of user experience design by both friends and a few strangers. Instead of writing my responses out over n' over, I figured a blog post might come in handy. Below is my own personal take on the basics of UX in FAQ form:

1. What is "user experience" (aka "UX")?

In a broad sense, this field examines both improving existing products and the creation of new ones that solve some sort of human problem or fulfill a desire. More often than not, this mainly involves the design of web sites, web applications, and client software (programs that run on a computing device vs the web).

This narrow definition reflects the field as its practiced in techy areas like Seattle and Silicon Valley, but on a greater scale, "UX" means a whole lot more.

If you really boil it down, anyone who prepares anything for someone else to consume is a UX designer... so by this definition, we are all UX designers. Telling someone a story: that's UX... DJs stringing together songs in a pleasurable way: that's UX... the sushi chef who prepares an omakase style diner: definitely UX.... filmmaking = UX. No matter what the particular example, these all share the common thread of understanding an audience and satisfying some kind of desire (to be informed, entertained, etc).

2. Where do "user experience designers" work?

Going by the definition above, someone with this printed on their business card can follow any of the following routes:

A. working for a big corporation like Apple, Google, IBM, Oracle, Amazon, etc
B. working for a startup or small company like Twitter
C. working as a freelancer that goes from project to project with various clients (like my friend Sally)
D. working for a design firm that also has multiple clients (Adaptive Path & ZAAZ are popular ones)

A person in this role will spend their time thinking about how to make a given experience easier to understand and generally more appealing, hopefully even pleasurable!

3. How do I know if UX is something I'd want to do for a living? (aka, "you might be a UX designer if...")

A good litmus test is to look at how you live your daily life. Are you constantly looking for ways to improve the environment around you? Are you the type that gets enjoyment from optimizing your closet? Do you look for ways to make your daily routines more efficient? When you run into the inevitable bad user experience, do you only complain about it or do solutions to improve the frustration come to you naturally? The answer to these questions should give you a sense for whether UX is something you'd enjoy and be good at.

4. How does UX differ from graphic design?

One of the most common misconceptions about the field is that it's the same thing as graphic design. I understand the confusion as the two are very related. To put it as plainly as possible... one could have really crappy graphic desgn skills yet still be a great UX designer. Having art skills is certainly helpful, but it's not a requirement. Some of the best UX work is illustrated by stick figure diagrams and white board drawings covered in post-it notes. In fact, focusing too much on the visual details can often hinder a UX designer depending on the needs of the project (more on this later in the post). While graphic design is certainly a part of good UX, it's a subset which resides along side things like information architecture and usability.

5. So I get it, UX does not equal making pretty graphics... what skills are needed then?

-- Domain knowledge (behind the scenes)

Many people in the tech UX world have degrees in computer science, even though they may not write a single line of code. Why is this useful? On several levels, but most importantly, without a fair bit of knowledge about the constraints of the thing being designed for, the designer will either:

A. design something that's completely impossible to implement (aka "too wild")
B. will miss out on possible design solutions because they didn't know what all was possible (aka "too conservative")

The other component of domain knowledge is the ability to discuss the specifics of a design with the programmers who'll be implementing it. Having a shared language and understanding of the basics under the hood helps tremendously in getting ideas into the real world.

-- Domain knowledge (frontend facing)

The section above talks about knowledge of the underlying systems that make UI's work... this part is more about what the user actually sees and interacts with. The more a UX designer is exposed to different kinds of UI and experiences, the greater their capacity to come up with solutions. There's obviously a law of diminishing returns here, but my point is that if you're designing one particular kind of experience, it's good to look at experiences outside of that particular niche (e.g. web designers looking at video games for inspiration) as a way to broaden the potential solutions to a problem.

-- Empathy & understanding "audience"

Perhaps the most important trait of a good UX designer is the ability to empathize with others. If you're unable to see the world through the eyes of someone else, the only person you'll be able to solve problems for will be yourself (and those who are just like you). One of the mantras of UX is "you are not the user" and it's important to be reminded of this regularly.

So if UX designers don't design for themselves, they have to figure out who then it is that they're designing for. Sometimes the answer to this is obvious (e.g. cancer patients aged 60-80 who speak English and live in America), but more often, it's quite ambiguous (e.g. all users of the internet). For the latter, this is where things like market and usability research really come in handy. There are a myriad of resources out there to help the UX designer understand the audience better, but nothing is a replacement for someone who inherantly knows lots of different kinds of people and who can use their imagination to picture how others would react to a particular experience.

Having general knowledge about basic limitations of human memory, vision, and other cognitive abilities also helps in this regard.

-- Communication skills

This goes for written, verbal, and visual communication skills. All of these modalities are just tools in the toolkit to get one's ideas across. Also worth mentioning... even though designers rarely write marketing or help copy, tech writing classes can be helpful as they improve one's ability to communicate crisply and concisely which is imperative in tech UX interfaces.

-- Collaborating with others

While many programmers have good social skills, this isn't a requirement in their particular field (writing great code is), but in UX, it's essential. A designer can have the greatest ideas and designs, but if they're unable to involve the rest of the team, nothing they come up with will see the light of day. This reminds me of a particularly thorny part of UX... unlike coding which requires highly specialized knowledge that no one else can provide, everyone can have input on user experience (which can be a blessing and a curse). Because of this, it's important for a designer to gain the team's respect and confidence with their expertise and designs, but not at the expense of shutting out the ideas of others.

-- Vision

Being a good UX designer requires the ability to see into the future and envision a world that is better than today (however small the scale may be). It's easy to copy from tried n' true products, but if the designer's goal is to actually improve on stuff that's already out there, this requires imagination and the ability to understand the big picture that encapsulates any particular user experience.

-- Patience

Great UX doesn't come to life over night. There are few eureka moments and arbitrary constraints can often shape a UX in ways the designer never intended. There are definitely compromises and trade-offs to be made, which lead to time consuming iteration. While most UX designers would prefer to get the best experience out there at the cost of doing something sooner, it's important to also remember that shipping something that's not 100% baked can be useful as a way to get the feedback that will eventually lead to a great product.

6. How do I get into the field and make it into a career?

Well, it depends. Let's revisit the job types from question 2:

-- Big companies

A degree in some variant of Human-Computer Interaction is extremely helpful (if not mandatory in some cases). If not available, computer science, graphic design, and industrial design can also work.
There are exceptions here, but for the most part, big companies use the degree as a weed out tool since they get so many resumes and consider school a decent gauge for vetting candidates. Next in line is relevant work experience and portfolio.

-- Small companies & freelance

It's all about the portfolio. No one really cares which program you came out of, it's more about what you've done and what you can do for the client. If this is where a designer wants to wind up, improving one's portfolio and pulling all the pieces together into a clean, easy to understand website is key.

7. What does a typical UX designer's average day look like?

We can be in a fair amount of meetings to discuss the ins and outs of various design decisions, but most of our time is spent doing any of the following (depending on what phase of a project we're in):

-- Whiteboarding/brainstorming

This is where I like to spend most of my time (although in practice this rarely happens). In this phase, we're just having fun with ideas. The cost to sketch something out is super cheap, so there's a lot of freedom to play around and collaborate on tough experience problems.

download flow

-- Wireframing

At this stage, a UX designer is taking their sketches and turning them into a digital format that consists solely of lines, boxes, arrows, and text labels. We call this "low-fidelity" and it keeps the team focused on a particular solution's "main idea" vs which colors and graphics are used.</i>



-- Prototyping (aka "mocks")

Here, we're taking an idea and prototyping it so that it looks real. Prototypes can be static (a series of images) or dynamic (typically done as Flash animations or animated gifs). Unfortunately, to get buy-in from execs and other stakeholders, UX designers spend the majority of their time here on ideas that aren't quite ready since wireframes take longer to explain and understand. This dichotemy between high and low-fi prototyping is a never-ending debate in the field which I won't go into in this post. You can read more about it here.



-- Email / specs

Much like everyone else in tech, UX'ers spend a lot of time writing and reading emails, but much of the emails written are used to describe some aspect of an experience in conjunction with any combination of the items above. Depending on the company's culture, these descriptions can go directly into emails, as seperate docs (called "specs"), or into bug tracking systems.

more on UX deliverables here and here.

8. What is the difference between user experience design and usability?

Usability researchers spend their time uncovering UX issues and do things like lab studies, surveys, ethnography, etc. Designers spend their time more on the other side of the equation coming up with solutions to UX problems. They both need each other and work towards a common purpose, but the skill sets and deliverables involved are different.

9. How else can I get my foot in the door?

If finding a UX role is proving difficult, look for entry level product or project management jobs. There are more of them and can help you get your foot in the door (and usually involve some component of spec writing and design). You'd gain some UX experience in a role like this and could then shoot for more UX-specific roles later on. These kinds of positions often require CS degrees, so if you don't have that, then just do stuff on your own... find open source projects that have crummy UIs and make them better. Work on the design of your own site/blog. Write blog posts about UX... in particular things you see that have room for improvement (and how you'd specifically improve them). Find local businesses that have crappy sites and offer up your services... non-profits are usually dying for this kind of help. The possibilities are only limited by your imagination! :)

Above all, I recommend "doing UX work" as much as possible and then the job will come along as a byproduct of that. Reading books and UX blogs is a good thing too, but designers looking for work should make sure they're spending more time designing than reading. Another way to get traction is to find others who are like-minded and collaborate with them on a project (particularly great if the partner's skill set is complimentary like someone with strong web development skills).

10. What are some resources I can check out to learn more?

There are countless books on the subject, two of the most referenced are About Face & Don't Make Me Think.

More on general UX stuff here:

http://www.montparnas.com/articles/what-is-user-experience-design/
http://en.wikipedia.org/wiki/User_experience

and these are collections of UX related links that came in handy to me over the years...

http://delicious.com/interimlover/ux
http://delicious.com/interimlover/uxp
http://delicious.com/interimlover/ui
http://delicious.com/interimlover/webdesign
http://delicious.com/interimlover/portfolio

If there are other UX related questions anyone has, fire away in the comments! I know many of you work in UX, so if you have anything to add, I'd love to hear your feedback too.
Tags:

Link | Leave a comment {7} | Share

25 things (facebook meme)

Feb. 2nd, 2009 | 12:43 am
music: Ryuichi Sakamoto - Railroad Man - Piano Version | Powered by Last.fm

Xposting to El Jay...Collapse )
Tags:

Link | Leave a comment {9} | Share

*sniff*

Feb. 1st, 2009 | 12:24 pm




Man, I miss having Bill around. Hope you got that Hendrix harp concert after all.
Tags:

Link | Leave a comment {3} | Share

info overload, a response

Jan. 23rd, 2009 | 11:27 pm
music: Jugoe - Devil Woman | Powered by Last.fm

A student in the program I came out of at UW sent me a well thought out paper on the topic of information overload. Here's an excerpt from my response to him:
The topic of information overload isn't easy to explore. The problem is different from person to person and varies wildly by culture. I've been thinking about it for years and "a struggle" is the best way I can describe it.

I think it boils down to the age old battle between the Buddhist idea of letting go of desire vs the very Western idea of continual progress (and striving to be the "best"). The internet provides us with the ability to become knowledgeable on a wide variety of subjects in a way that would take much longer to achieve via traditional print media. But as Postman points out, the Faustian bargain here is that we rarely go deep into any one subject... we're a mile wide and an inch deep as the expression goes.

I think it's still up in the air to see what this will do to society as time moves on. What does a society comprised of super generalists and a handful of specialists look like?

In my job, I'm constantly thinking about the right balance between putting people in the path of more useful information vs the cost of having more noise to deal with. Twitter is a great example of this dichotomy. I find some really nifty things via Twitter and it's a great tool to keep up with my friends (especially those who I don't see in person often), but there's a hefty tax to pay for this benefit in terms of time and the mental energy it takes to sift through all the tweets I don't care about.

Another factor in all of this is how our tastes change as we get older. A stream of information I may have found interesting in the past may no longer be useful to me anymore, so there's this constant interplay of taking in new streams and unfollowing old ones.

The thing to learn in all of this is just because you can expose yourself to something, it doesn't mean you should. If memory serves, there's a science experiment where they give a mouse unlimited access to tasty food. The mouse can't help himself and eats to the point where it eventually dies. There are documented cases of this in the massive multiplayer game world where gamers die from playing the game for 3-4 days straight without a break. Obviously this addictive drive still exists in humans, to varying degrees of course, but it's there. We get the same kind of dopamine squirt in the brain when we learn something new or from processing a ton of information like taking an inbox of 200 emails down to zero... I've heard people describe such information processing as a "rush." The question I ask myself is "am I a happier, better person from all of this digital interaction?" The jury is still out on that one :)
55
taken from here.

Link | Leave a comment | Share

Rick Steves' Iran

Jan. 20th, 2009 | 01:22 pm

New documentary on Iran debuting this week on PBS...



Looks pretty good from the preview.

Local broadcast times here. (It's on at 10 pm tonight in the bay area).
Tags:

Link | Leave a comment {4} | Share

"To All My Valued Employees"

Jan. 16th, 2009 | 11:19 am

Just received this letter as an email forward from a family member.

Can someone who actually knows something about economics provide a rebuttal? It makes sweeping generalizations about the intentions of business owners and the author's policy descriptions seem sketchy.
Tags:

Link | Leave a comment {20} | Share

Some thoughts after reading "Amusing Ourselves to Death"

Jan. 12th, 2009 | 11:19 pm
music: Anders Ilar - playing with the winds | Powered by Last.fm



One thing I didn't do nearly enough of last year was read. I'm going to work on improving this in '09 and started along that path with this excellent book, circa 1985 by Neil Postman. I was introduced to Postman in grad school by way of his infamous speech, "Informing Oursleves to Death" which is one of the rare texts I find myself going back and reading every few months or so... the same goes for Graham's "What You Can't Say."

Before I say anything more about the book, I wanted to first explain how I read the book.

As a long time iTunes hater, it took me a while to warm up to it after I got an iPhone. Now having used it, I'm well aware of its shortcomings (libraries that span multiple computers & disks) and it's strengths (powerful database features around ratings). Since I now rate all the music I listen to, I'm able to create really enjoyable playists of just my favorite songs.

By rating every single track, this forces me to be a much more engaged and analytical listener. As a music lover with a voracious appetite, disk space comes at a premium, so if a track doesn't cut the mustard, it's deleted. Here's how I use the iTunes 5 star scale for rating songs:

5 = a song I can truly call a "favorite"... has super high replay value and will hopefully stand the test of time.
4 = a pretty good song that I find enjoyable, but it's not moving any mountains for me
3 = the wishy-washiest of ratings... I try to reserve it only for tracks that hold an album together like Board of Canada interstitials.
2 = I'm learning stronly towards deleting it. I'll let these accumulate over time and will go back and listen to them occasionally... very rarely do they ever survive the 2nd pass.
1 = means delete this at some point, it sucks big time.

After using the ratings for awhile, I started thinking about applying this model to all areas of life... clothes, food, people... keep the good stuff and cherish it, toss out the stuff that doesn't matter.

With regards to reading, before, I'd read books without making a mark in them ("books are cherished sacred objects" I thought), but then I remembered that I retain my reading a lot better when I write in the book like when I was studying for exams and writing papers. My technique back then was simple, just underline noteworthy passages and draw a quick star symbol next to things I thought were of particular importance.

The problem with this method was that I'd put too many stars and underlines everywhere, which gave equal weight to too many parts of the text. When I go back to revisit the text, I might as well read the entire thing over again to really figure out the parts I liked most.

I tried applying the iTunes model directly to "Amusing" and quickly discovered it tedious to draw out 5 stars as I was reading. After a bit more thought, I realized I could scale the rating system down to a 3 star method... 1 for good ideas, 2 for great ideas, and 3 for the kinds of ideas I'd want to commit to memory. If an entire page struck me as significant, I'd circle the page number and continue to underline particularly good phrases.



So now having used this system all the way through a book, here's a summary of a few 2-3 star sections:
more...Collapse )
Tags: ,

Link | Leave a comment {16} | Share

A reminder from Dale Carnegie

Jan. 12th, 2009 | 09:30 pm
music: Bassmouse - The Condition Within | Powered by Last.fm

“You can tell people they are wrong by a look or an intonation or a gesture just as eloquently as you can in words—and if you tell them they are wrong, do you make them want to agree with you? Never! For you have struck a direct blow at their intelligence, judgment, pride, and self-respect. That will make them want to strike back. But it will never make them want to change their minds. You may then hurl at them all the logic of a Plato or an Immanuel Kant, but you will not alter their opinions, for you have hurt their feelings.”

Tags:

Link | Leave a comment {5} | Share

Two fictitious male characters I like a lot

Jan. 11th, 2009 | 10:54 pm
music: Lomax - ATM Presents Lomax Mix | Powered by Last.fm

Ricky:

and more recently, Omar:

Link | Leave a comment {9} | Share

my social universe

Jan. 9th, 2009 | 01:52 pm


my social universe, originally uploaded by ario_j.

made with skitch.com & nexus.ludios.net.

View large.

Link | Leave a comment {1} | Share