inicio mail me! sindicaci;ón

Learning how to make UX decisions

I just had a great time recording a Userability Podcast where Jared Spool and Robert Hoekman answer my questions about how UX practitioners can learn to make good decisions about which methods to employ in their work.

[I'll update this with a link once it's published]

My question is an old concern about how new practitioners are being introduced to User Experience Design and Research practices by being fed a multitude of methods and not given much support about how to decide the right circumstances to use them.

It is not sufficient just to know how a certain method works. It is also not sufficient having used that method once or twice. What is it about our experience as practitioners that makes us better or worse decision makers? How do we choose to dedicate time and money to an 8-week long project to produce personas instead of a different approach?

What distinguishes the practitioners that not only choose methods and know how to apply them, but choose the methods that are most effective for a given problem?

A few years ago, Jared himself told me a story about an experiment where two distinct research teams (unaware of each other I believe) were given the exact same research goal and employed the same methodology to achieve it, and came up with different results and findings.

When that sort of thing happens, I wonder: Can we really trust our methods? But more importantly, if we accept that our methods are not really scientific and that we can’t really have a high level of confidence about the results we end up with, how do we choose one over another?

Somehow we just do. But some do better than others. Some do MUCH better than MANY others. If you have the opportunity to work with practitioners with enough experience and knowledge, you see excellent arguments for why to do A versus B for a given set of circumstances. So yes, only experience will help one make better choices, but everyone’s experiences are different. As a way to try to educate new practitioners we coach and mentor by teaching the methods and also giving advice such as “be flexible” and “don’t marry a particular process” and “figure out what kind of problem you are trying to solve first”, which are all excellent advice, but not strategic enough and often not practical enough that it can really help someone make a decision when they are faced with a new challenge.

Jared’s opinion is that our field is still too young and we haven’t yet been able to articulate the criteria we use in that decision-making process. I agree, however, it worries me that many think they are advancing in their practice because they know more, when in fact, they just learned new methods, but don’t really have the skills to assess risks, and benefits, between choosing one over another.

Being a runner gets you to the finish line, knowing which way to run wins the race. I really hope we become better equipped to pass on knowledge about how we make choices and why because, paraphrasing Jared, knowing a lot of recipes a restauranteur does not make.

Connect with people first, content second

Very frequently people ask me how to get started in the UX field, or IA practice or Design. I always try to tailor my answers to their specific needs. Today I got an email from someone at work asking:

“Hi, everyone. If you decided you were interested in IA/UX but you didn’t know much about it…and you wanted to find out more…where would you go? What books would you read? What blogs would you add to your feed reader? What seminars would you attend? What tutorials would you take? What tweeters would you follow?”

Having no context I took 5 minutes are made this recommendation. I am sure I would tweak and change this significantly if I had any other inputs, but this was my 5 minute recommendation and I thought I’d share:

The starter book is Information Architecture: Blueprints for the Web. After that, The Elements of User Experience followed by Don’t Make Me Think. All other books people recommend are wonderful, but not to start with.

Become a member of The Information Architecture Institute and find yourself a mentor; it’s the most valuable investment anyone can make when starting out.

I don’t follow blogs. I let the community curate content for me instead. Following the right people on twitter means they send me all the good blog posts. Also, you come across the relevant blogs via the discussion lists (specially the one you get access to when you join the IA Institute). Connect with people first, content second. It’s helpful to connect to the UX/IA/IxD groups on LinkedIn, Facebook, Slideshare – it will help attract good content to you. You’ll immediately have access to all kinds of people you’ll become interested in connecting with.

Attending seminars: Go to all the free stuff happening locally. In Philly there’s PhillyCHI and Refresh Philly to start with. Online, spend your money wisely and pick the topics that seem more interesting to from UIE Virtual Seminars and Rosenfeld Media Webinar Series. Make sure you keep track of The UX Workshop for free broadcast of local events in other cities.

For community and education, attend the IA Summit. If you are starting out, that’s the first conference to go to. And Interactions. For more focused training, UIE’s User Interface Events and Adaptive Path’s UX Week and UX Intensive.

On Twitter, there are too many interesting people to follow and big names in the field. They don’t necessarily share any relevant information or advice relevant to starting out. These people do: @jmspool, @whitneyhess, @halvorson, @sladner, @mmilan, @austingovella, @leisa, @mediajunkie, @emalone, @stephenanderson, @billder (I share a lot of stuff too: @livlab)

Lastly, start a blog. You learn significantly more by sharing and capturing your own thoughts than countless dollars spent in training.

And if you are going to start on all this after lunch, print this to read during lunch: http://www.jjg.net/ia/recon/

Tune Deaf

Do you use conference calling service for your work? I am sure you do. It’s inescapable; whether you use it for remote team collaboration, sales pitches or anything else, you have experienced the music that comes up when you first call in and is waiting for the leader to join and start the call.

It’s bad. I have used a number of different services and they are all bad. So when my friend Kit Seeborg told me about her new start-up, BumperTunes, I thought, they could definitely help with the lousy quality music these services have to offer!

So, in the spirit of encouragement for Kit & team, who are really focused on the podcasting market rather than conference calling, I just wanted to share what I have to listen to between 5 to 10 times a week (sometimes multiple times in a day):

please-help-my-poor-corporate-ears.wav

Update: If you have other examples, please record and post here! It’s easy. On Windows, just go to Programs > Accessories > Entertainment > Sound Recorder (fire up your lovely conference call tune and hit record)

Next entries »