Tag Archives: usability studies

Thoughts on UX Research Documentation

What kind of research doc­u­men­ta­tion is most use­ful for agile teams? What I have seen to work best has been light­weight doc­u­men­ta­tion. This would be using a wiki to record issues, focus­ing on debriefs, cir­cu­lat­ing tran­scripts, and get­ting every­one to observe tests. How­ever, I find that there is a great deal of pres­sure in the UX Com­mu­nity to track all of our find­ings in a database.

Here is what I think:

  • With lim­ited resources, it’s not prac­ti­cal. I think track­ing usabil­ity issues in a data­base is a great idea in the­ory, but in prac­tice I haven’t seen it work out so well. We man­aged a “usabil­ity find­ings data­base” in a pre­vi­ous job, but it was unfor­tu­nately never used… Researchers spent a great deal of time main­tain­ing the data­base, but design­ers never ref­er­enced it. Researchers would even walk through the data­base with design­ers, but design­ers would always say watch­ing a fresh new study was so much more insightful.
  • It doesn’t align with lean/ux prin­ci­ples. Agile devel­op­ment val­ues work­ing soft­ware over doc­u­men­ta­tion. I think this means it is more valu­able to *see* some­one using your design. It’s becom­ing eas­ier and eas­ier to test work­ing soft­ware, pro­to­types, etc. (using unmod­er­ated test­ing, live-intercept recruit­ment meth­ods, etc.) Instead of doc­u­men­ta­tion, we should be focused on debriefs, dis­cus­sions, and get­ting every­one exposed to users
  • Old usabil­ity issues get out dated — fast. I don’t think we should base today’s design deci­sions on data we col­lected a year ago — the web is chang­ing so fast, as well as our prod­ucts.  We should be putting our focus on ‘expo­sure hours’ get­ting design­ers exposed to users more, which has a direct, proven impact on mak­ing prod­ucts bet­ter and bet­ter. Some of the issues I found even a month ago, in an iPhone study, are no longer valid, since we’ve made updates to the products…

Here’s the real truth: the only doc­u­men­ta­tion that is nec­es­sary is in the form of *user sto­ries* on prod­uct back­logs. Period.

What has been your expe­ri­ence track­ing usabil­ity issues? Check back at a later date for fur­ther thoughts on UX Documentation.

Mobile testing: filmed in front of a live *stakeholder* audience

One of the best ways to build tech­nol­ogy that truly fits into people’s lives is to observe peo­ple using your tech­nol­ogy.  At my job, I fre­quently set up usabil­ity tests, so that we can observe peo­ple using the inter­faces we have designed.  It has become eas­ier and eas­ier to run these stud­ies, thanks to tools like GoToMeet­ing, or Morae, how­ever, one of the most chal­leng­ing tests to set up are tests on mobile devices.  You start out with many of the nor­mal tasks to con­duct web site usabil­ity tests: email cam­paign­ing, sched­ul­ing par­tic­i­pants, coor­di­nat­ing con­fer­ence rooms, tech­ni­cal set up… but then you have the addi­tional chal­lenges of set­ting up mul­ti­ple web­cam feeds, try­ing to stream live video into the next room, host­ing a remote obser­va­tion room, and keep­ing your eye on stake­holder ques­tions while mod­er­at­ing the test with the participant.

We know how pow­er­ful and inspir­ing it is for stake­hold­ers and devel­op­ers to watch ses­sions live, while you are con­duct­ing the tests with par­tic­i­pants.  But watch­ing mobile test­ing live? While in the field? My sister-in-law inspired me to believe this is pos­si­ble because she once live streamed her­self run­ning the Oki­nawah Marathon in Japan. It was almost like being there with her…the kind of expe­ri­ence you want your devel­op­ment teams to have, so they can under­stand the con­text your users are in…

So how do you run a mobile usabil­ity test in front of a live stu­dio audi­ence? Here are a few tips I picked up from watch­ing a lot of 30 Rock (NBC’s Com­edy Series, cre­ated by Tina Fey, about putting on a late night talk show).  The fol­low­ing are a few thoughts you can use to emu­late “Liz Lemon” traits:

1. Speak your mind.
When things are get­ting tough, go to your boss and be vocal about it. They are never going to know what you are strug­gling with unless you TELL THEM. Just tell them the whole story, and they will help you find a solu­tion… or at least tell you not to worry about it.

2. Keep track of the details.
Keep lists of to dos. Make check­lists for repeat tasks. Dou­ble check your work. Test. test. test. Rehearse like crazy. Nail your open­ing script. Be on time. Do every­thing in your power to cover the details. You might start to feel hope­less, if you are cov­er­ing all your bases, but not scor­ing any runs… if you know what I mean. But try not to worry about that. Just try not to drop any balls.

3. Stay focused on your work.
Many peo­ple will try to tell you how to run your test. This can be dis­tract­ing if you are not stay­ing focused on the test you crafted. They are great at offer­ing their opin­ion on the par­tic­i­pants you’ve brought in, the sce­nar­ios you wrote, and giv­ing their sug­ges­tions of what you should have done dif­fer­ently. Every­one has an opin­ion, and while it shows that they care about the research, they are almost always wrong. For exam­ple, peo­ple who com­plain about the peo­ple you recruited wouldn’t know the first step in find­ing the right peo­ple… most of them wouldn’t even know how  to describe who the “right” peo­ple are! Just stay focused on you… you need all the self con­fi­dence you can muster up for this “show” to go off well.

4. Shake off the mis­takes.
You can’t get held up with the mis­takes you make. You might for­get to record the audio prop­erly, or ask that extra ques­tion your stake­hold­ers asked you to put into the script last minute. Your com­puter might go to sleep, leav­ing your observers with noth­ing but a blank screen.  Just shake it off… take a deep breath, and ground your­self. Focus on what the par­tic­i­pant is say­ing, and fol­low their lead.

5. Don’t sweat the stress induced fore­head acne.
Your adren­a­line will kick in once you get doing dur­ing your tests. Then, all of a sud­den you will lightly brush your hand across your fore­head to dis­cover a sore lit­tle bump, freshly arisen, out of nowhere. Even if you swear to be calm, and not sweat the small stuff the week you are test­ing, your adren­a­line will kick in, pro­duc­ing stress hor­mones that cre­ate break outs on your face. Don’t pick at it, just let it run its course.  Your body needs to heal.

Just remem­ber, run­ning a usabil­ity test in front of a live stake­holder audi­ence may be stress­ful, but it is reward­ing. Watch 30 Rock, and pick up some tips.

Seven Tips for Presenting Usability Issues to Stakeholders

In a pre­vi­ous life, I was a Library and Infor­ma­tion Sci­ence mas­ters stu­dent, and part-time ref­er­ence desk librar­ian. I worked in the Bio­med­ical library, con­nect­ing med­ical stu­dents and pro­fes­sion­als to jour­nals, arti­cles, research, stud­ies, books, knowledge…I attended med­ical library con­fer­ences and stud­ied how to help med­ical pro­fes­sion­als with “evidence-based prac­tice.” As a
result, I became adept at help­ing peo­ple find evi­dence to base their prac­tice on in med­ical research lit­er­a­ture. That skill has cer­tainly served me well as a user expe­ri­ence researcher as I work closely with design­ers and stake­hold­ers, and now unsur­pris­ingly, find­ing and deliv­er­ing evi­dence to inform design deci­sions is my absolute favorite part of this won­der­ful job.

I’m in the thick of user research on my cur­rent project, and along the way I’ve been remind­ing myself of all sorts of best prac­tices I learned from the bril­liant Joan Kaplowitz, an Infor­ma­tion Lit­er­acy Librar­ian.  Using her advice, I do every­thing I can to make sure the peo­ple con­sum­ing the infor­ma­tion I present, are get­ting what they need and inform­ing the design ques­tions they have.

My hope is what works well for me, using Joan’s prin­ci­ples, will help you too when you have to com­mu­ni­cate your results to a team of stakeholders.

1. Engage your stakeholders

“Active learn­ing is bet­ter than pas­sive recep­tion for reten­tion and trans­fer of learn­ing.” Joan Kaplowitz

In my expe­ri­ence, the best way to engage stake­hold­ers, and have them actively learn usabil­ity issues is to involve them in the research.  Hav­ing them come to observe usabil­ity test ses­sions and con­tribute their obser­va­tions to an affin­ity dia­gram is a very effec­tive way for them to retain the feed­back they hear, and see trends across users.  One strat­egy I learned from attend­ing the Nile­sen Nor­man Group Usabil­ity Boot­camp in 2007 was from Kara Per­nice: have your observers take notes on post-its (quotes, obser­va­tions, one issue per post-it), and then change color post-its for dif­fer­ent par­tic­i­pants. Then you can start to group issues together with stake­hold­ers, and see usabil­ity trends across users (col­ors). Your dia­gram of groups then can turn into your report, tran­scrib­ing your wall of insights into a pre­sen­ta­tion slide deck or any other format.

2. Keep it light­weight

“Less is more. It is bet­ter to teach a few things well than to over­whelm learn­ers with so much infor­ma­tion that they become frus­trated, anx­ious, and unable to retain any­thing from the instruc­tion.” Joan Kaplowitz

The best way to describe this prin­ci­ple as it applies to report­ing usabil­ity find­ings was best artic­u­lated by Todd Wilkens from Adap­tive Path: “The effec­tive­ness of your research report is inversely pro­por­tional to the thick­ness of it’s bind­ing.”  You will be so much more effec­tive in mak­ing change hap­pen, and get­ting peo­ple to take action on your find­ings, if you don’t over­whelm them with new infor­ma­tion. Your goal is to inspire your stake­hold­ers to address the usabil­ity issues, and have design­ers solve the usabil­ity prob­lems.  Then, val­i­date those changes were suc­cess­ful with another round of testing!

3. Get them talking

“The instructor’s voice should be the one heard least dur­ing teach­ing.” Joan Kaplowitz

The best pre­sen­ta­tions I’ve ever given have been because I met with stake­hold­ers ahead of time to get a sense of what they learned from watch­ing usabil­ity ses­sions. Get design­ers to tell you what they learned, because it doesn’t mat­ter so much what is in your head, as it does what is in theirs. Before giv­ing your final pre­sen­ta­tion to the larger group of stake­hold­ers, talk with your key stake­hold­ers, and have them tell you what they learned, observed, and took away from the ses­sions.  Review the take­aways you intend to present, and invite them to add to it. Your final pre­sen­ta­tion will be far more effec­tive at inspir­ing change to happen.

4. Grab them in the first 5 minutes

“You win or lose your audi­ence in the first five min­utes. Talk to your learn­ers as they enter the room. Pro­vide them with some­thing to do and/or think about as peo­ple are arriv­ing. Engage them from the start.” Joan Kaplowitz

Some­times the begin­ning of the find­ings pre­sen­ta­tion is the most chal­leng­ing, because all your great insights are com­ing later in your slide deck.  How­ever, the begin­ning of a pre­sen­ta­tion ALWAYS sets the stage for the mes­sage you are giv­ing. Get to the pre­sen­ta­tion room early, and build rap­port with each per­son who comes through the door.  Great them with a hello, and say their name (peo­ple love to hear their own name).  The goal before the pre­sen­ta­tion starts is to get “audi­ence mem­bers” on your side, because in my expe­ri­ence, these are the folks that that are most likely to help fend of heck­lers in your defense! Also, you want a strong intro­duc­tion.  You def­i­nitely don’t want to stum­ble through your first 2 min­utes of speak­ing.  Here is a basic intro­duc­tion that I use often — but the more cre­ative you can be the better!

Great, let’s go ahead and get started. Today we are going to talk about_____________. We have about 45 min­utes for the dis­cus­sion, and I’ll leave some time at the end for ques­tions, but if you have any ques­tions along the way, please feel free to ask. First I want to ask… who had a chance to observe the ses­sions?  Great, well if there is any­thing you would like to add that you remem­ber observ­ing, please feel free…”

5. Demon­strate each key issue

This advice I learned on the ground floor at the UCLA Bio­med­ical Library ref­er­ence desk.  Stu­dents, nurses, patients, etc. would come to the desk ask­ing how to use the library data­bases.  The most effec­tive way for them to learn how to use the data­bases wasn’t just telling them, but actu­ally demon­strat­ing it to them. In fact, it was best if you could hand the key­board to them, and have them drive them­selves.  In an usabil­ity find­ings pre­se­n­a­tion, you really want to re-create the issues that par­tic­i­pants had dur­ing the ses­sion.  Stake­hold­ers tend to be quite visual, and greatly ben­e­fit if you show them what you mean.  Take full screen shots, and sim­u­late the expe­ri­ence of using the tech­nol­ogy using basic ani­ma­tions such as fad­ing in.  This seems to be the best way to re-tell the story, and have your find­ings really sink in with stakeholders.

6. Keep track of your effectiveness

“Always include a way to assess your out­comes. Oth­er­wise you will have no idea if your learn­ers have attained them.” Joan Kaplowitz

In the world of UX Research, the best way to assess your out­comes is to keep track of which issues are on the plan to get­ting fixed, and which ones have not been fixed. You can keep track of these in an Excel spread­sheet on your own, but the best is to have your issues make it to the prod­uct roadmap.  You want to see your usabil­ity issues turn into “user sto­ries” if you are work­ing with Agile teams, or pos­si­bly the roadmap, bug fixes, or “change requests” if you are work­ing in a water­fall envi­ron­ment. How­ever your orga­ni­za­tion keeps track of changes that need to be made to the sys­tem, do what you can to make sure usabil­ity issues are rep­re­sented there.

7. Take a multi-format approach

“Use hand­outs, web pages, and pre and post activ­i­ties to extend your con­tact time with your learn­ers. Offer ways for learn­ers to keep the con­ver­sa­tion going after instruc­tion is com­pleted — through email, blogs etc.” Joan Kaplowitz

A Pow­er­Point pre­sen­ta­tion is a great way to walk through usabil­ity find­ings.  How­ever, you don’t want to only deliver a slide deck. In addi­tion to your pre­sen­ta­tion, you will want to give a “hand out” to your key stake­hold­ers, the peo­ple who need a “check list” of things to address.  Don’t rely on them tak­ing their own notes dur­ing the pre­sen­ta­tion, give them a list that they can eas­ily make notes to.  You don’t need to pass this out to every­one, just to your 1 or 2 key stake­hold­ers. Also, I’ve seen a fol­low up email work really well, with a link to your pre­sen­ta­tion, to the record­ing of the dis­cus­sion, and a cou­ple bul­lets that sum­ma­rize the key take­aways.  Invit­ing users to con­tinue the con­ver­sa­tion using wiki pages is a great way to keep them engaged, and con­tinue with next steps.

So there you have it. This is my very best advice on how to present usabil­ity find­ings so that it inspires your stake­hold­ers to take action. Many of the infor­ma­tion lit­er­acy prin­ci­ples listed here apply to bas­ing design deci­sions on evi­dence.   How do you com­mu­ni­cate your usabil­ity issues?