small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

Still can’t get a UX job? Give up.

large_featuredImage

medium_featuredImage

small_featuredImage

thumbnail_featuredImage

Sticking to UI/UX trends is a losing strategy

<p>Published on <a href="http://ift.tt/2tEii0O">| Prototyping: From UX to Front End &mdash; Medium</a> Stefan Wolpers </p>
<h3>TL;DR — Lean User Tests (Part 5)</h3>
<p>The fifth part of the Lean User Tests series deals with how to interview the participants and what the course of the conversation most likely will be.</p>
<p>How are your preparations progressing? If anything is impeding you from reaching this goal, please do not hesitate to contact me by commenting this post, and I will gladly help you.</p>
<p><a href="http://ift.tt/2typ9J1"><img alt="" src="http://ift.tt/2tE8SCj"></a></p>
<h3>Successful Interview Practices for Lean User Tests</h3>
<p>The interviewer should let the interviewee talk — meaning, he or she should entice the participant to articulate their thoughts. By all means, it should be avoided to suggest answers or ideas. Suggesting those would lead to false positives, as the interviewee might be tempted to say what he/she thinks the interviewer would like to hear. However, this is not the purpose of the interviews.</p>
<h3>Best Practices on how to Run Interviews for Lean User Tests</h3>
<h4>Interviews: What to practice during lean user tests</h4>
<ul>
<li><strong>Don‘t interrogate</strong>: It’s supposed to be a conversation, and the interviewer is the listener. Encourage the interviewees to tell you stories, particularly about things you cannot observe.</li>
<li><strong>Encourage loud thinking</strong>: You need to get your interviewee to share their thoughts during them solving their tasks. A lot of people are not very good at this, as they are not used to speaking out loud what they are thinking.</li>
<li><strong>Ask naïve questions</strong>: It is therefore always good to ask the interviewees why they are doing things in a specific way while they solve a task. And don’t worry if your questions sound naïve to the observers — you can avoid making assumptions this way that the interviewees cannot know about. It will also make the respondents feel like the experts during the conversation.</li>
<li><strong>Stay neutral</strong>: You should not try to influence anything, but stay neutral. You should never tell the interviewee what to do. That they will have to figure out themselves.</li>
<li><strong>Show, don’t tell</strong>: While we like to listen to stories when they cover things we cannot observe, we also like to be shown things we can note, for example, have the interviewee walk you through all the steps of a process.</li>
</ul>
<h4>Interviews: What to avoid during lean user tests</h4>
<ul>
<li><strong>Leading questions</strong>: “If we provide this feature, would you use it?” — That’s a classic and an entirely useless question. Instead, always wait for the interviewee to come up with that. If they don’t do so, the feature apparently does not have priority for them.</li>
<li><strong>Asking for solutions</strong>: As interviewers, we are interested in the problems of the interviewees, so we can help solve them. Discussing solutions with them instead is most of the time not helpful as respondents lack the insight knowledge.</li>
<li><strong>Don’t solve the respondent’s problem</strong>: It happens regularly in interviews: The interviewee cannot solve a task. Observing the struggle, some interviewers feel the need to help the interviewee to accomplish the task. Wrong idea. By helping them, you probably miss important details why they are struggling in the first place, which might affect your ability to come up with a solution in a negative way.</li>
</ul>
<h4>Some questions for an easy start of lean user tests</h4>
<p>A good way to ease into an interview would, for example, be the following questions:</p>
<ul>
<li>What are you doing professionally?</li>
<li>How often do you use the Internet?</li>
<li>Are you buying things on the Internet?</li>
<li>Have you ever bought anything from XYZ.com?</li>
<li>What are you (usually) buying from XYZ.com?</li>
</ul>
<h3>Conclusions</h3>
<ul>
<li>Some interviewees like to show off a little and tend to drift off. These are mostly interview partners working in sales or field services. These should be reminded — softly but firm — to get back to the interview at hand.</li>
<li>Any disturbances are — especially during 30 minutes interviews — rather annoying and disruptive because there simply is not enough time. Hence the strict policy on checking emails etc.</li>
<li>Interviewees liked to talk about good and also bad experiences with XYZ.com. Some like to use the interview as some form of escalation to customer service. We didn’t usually check before the interview if there had been differences of opinions between the interviewee and XYZ.com. It is advised to keep that in mind when asking questions about bad experiences.</li>
</ul>
<h4>Please hit the “heart button” 💚 below, if you found this post useful–it would mean a lot to me!</h4>
<p><strong><em>If you prefer a notification by email, please </em></strong><a href="http://ift.tt/2hoWLQv"><strong><em>sign-up for my weekly newsletter</em></strong></a><strong><em> and join 9,655 peers…</em></strong></p>
<h3>Lean User Tests: The Course of Interviews</h3>
<h4>The Structure of the Interviews</h4>
<p>The interviews are made up of repeating phases — regardless of the test subject:</p>
<ul>
<li><strong>Greeting and an introduction of everyone present (5 minutes)</strong>: In this phase, the participants will have time to take off their coats (takes longer in winter and when it is raining outside) and allows for a general greeting and settling in. After that everybody should just briefly introduce herself.</li>
<li><strong>Signing the test agreement (5 minutes)</strong>: Here the test agreement should be explained and then be signed. Most interviewees will take this very relaxed, but some may read the entire document from start to finish. This is a good time to let someone in the group (the recording person or an observer) fetch the coffee and other beverages for the interviewee. So far, nobody has ever refused to sign the agreement. Should this occur, the interview needs to be canceled.</li>
<li><strong>Handing over the gift certificate with the voucher (1 minute)</strong>: By handing over the compensation early, the situation is immediately more relaxed, and it creates trust, as practically all interviewees anticipate to receive the payment after the interview. Giving the voucher early may also please those of the interviewees, whose interest is mainly receiving the compensation. It helps to eliminate “false positives,” as it no longer matters if their answers are the ones the interviewer may want hear — because they received their compensation already.</li>
<li><strong>List with tasks (2–3 minutes)</strong>: If certain processes have to be tested with a detailed set of tasks, it makes sense to present a list of these tasks to the interviewee. This summary should be explained before beginning the interview so that the respondent is fully informed and knows what to do.</li>
<li><strong>The actual interview</strong>: Lost time can hardly ever be recovered during tightly packed interview slots. Therefore the interviewer is also the timekeeper and has to make sure that no time is wasted or lost. The net interview time is as follows: For a 30 minutes interview it is 12–15 minutes, and for a 60 minutes interview it is 30–35 minutes.</li>
<li><strong>Summary and finish (5 minutes)</strong>: At the end of the interview, the interviewer will summarize the most prominent findings. (Also as a feedback for the recording person.) You should all thank the participant for his or her time and effort and say goodbye. During the winter the part of getting dressed may take a little longer. It should be avoided to make the interviewee feel like she is ushered out, just because the next interviewee is already waiting outside.</li>
<li><strong>Preparation for the next interview (5–10 minutes)</strong>: This part is also important. You will have to delete information from the previous interview session, e.g. cookies, stop the screen recorder and save the file, collect the recorded protocols, getting the paperwork for the next participant like the test agreement, voucher, and task list ready, as well as clean the table.</li>
</ul>
<h4>The interviewees of Lean User Tests</h4>
<p>These are the most significant findings concerning interviewees from hundreds of interviews:</p>
<ul>
<li><strong>Early-show</strong>: They like to turn up earlier to their appointment than planned. In this case, you might as well start with the interview earlier. An excellent team of interviewers might even be capable of holding two interviews at the same time.</li>
<li><strong>Late-show</strong>: They are late. For 30 minutes interviews, this is putting quite some stress on the schedule, unless the following interview can be pushed out a little or you can have two interviews parallel with a second interviewer and recording person.</li>
<li><strong>No-show</strong>: They just don’t show up at and don’t cancel. (Status: “No-show” in the Google doc.) This is very unfortunate. I usually don’t waste any more time in trying to find out the reasons, and apparently, this kind of behavior will not be rewarded with a voucher.</li>
<li><strong>Last minute cancelation</strong>: They cancel minutes before the interview so that the replacement interviewee cannot be activated. We usually inform the replacement interviewees around 12.30pm, and that often works out well. If we, however, only learn about the cancellation by 3 pm, the chances of the replacement interviewee being able to jump in are rather slim — but it’s always worth a try.</li>
<li><strong>And you are?</strong> They show up despite having been declined via email. (Status: “Declined by us, 2nd winner” in the Google doc.) In this case, you either interview both or you send the second winner away. (In any case, we were generous and awarded the compensation for showing up.)</li>
<li><strong>Limbo</strong>: They are not available on their telephone during the morning hours, despite the prior agreement. This puts you into the position, where you don’t know, if this may be a no-show or if they simply forgot about the phone call and will turn up to the interview on time. In this case, I normally don’t activate the replacement interviewees.</li>
<li><strong>Kids &amp; dogs</strong>: They do not come alone, but bring children (mostly babies) or friends, relatives, and partners (spouses). We even had dogs in the interviews. In the end, these companions didn’t have any influence on the success of the interviews.</li>
</ul>
<h4>Conclusions</h4>
<ul>
<li>It is important to call every interviewee around 12 pm, to remind them of the interview in the afternoon. Some interviewees will forget their appointment. Any calls before 12 pm are not very successful. If someone is not available, a message should be left on the voicemail inbox, and I recommend sending a text message also.</li>
<li>The way to the interview room should be sign posted. These signs should be printed and put up. (Don’t forget to take scissors and tape if these are hard to come by at the venue.) This is particularly important in off-site venues that are not labeled with your company’s logo. Also, the reception of that off-site venue has to be informed so that they can assist the interviewees.</li>
<li>You should not offer any food the respondents. This will drag the interview out and makes it less successful. However, a post-interview-muffin is fine.</li>
<li>Observers should be allowed to ask relevant questions, but the interviewer should always have the lead over the interview. If the observer would like to ask questions, they should be cleared before the interview if possible. If this weren’t the case, the interviewer would have to intervene.</li>
<li>Last, but not least: During the interviews, nobody should be allowed to use any laptops, smartphones or tablets. Everybody shall listen to the interview and take notes, but emails, messages or texts should be checked elsewhere. It would be considered disrespectful towards the interviewee.</li>
</ul>
<h3>Follow-up and Debriefing of Lean User Tests</h3>
<h4>The Follow-up</h4>
<p>For the follow-up, the notes of the recording participants will be summarized into a form for each single interview. For this purpose, standard templates in the form of bullet point lists have proven to be successful, because they enable a quick orientation over the core statements.</p>
<p>This structure contains, for example:</p>
<ul>
<li>The name of the interviewee</li>
<li>Age</li>
<li>Gender</li>
<li>Motivation for taking part in the user test</li>
<li>Client history</li>
<li>A quote that summarizes this interviewee’s experience with the application</li>
<li>A description of how the application was used.</li>
</ul>
<h4>Conclusion</h4>
<p>Every recording person has their system as to how they record their notes. I recommend the use of handwriting on paper, as this doesn’t interfere as much as the typing on a computer might with the interview, and it also captures the information faster.</p>
<p>Also, it is useful to aggregate a series of interviews on a particular topic once more — think of it as an executive summary — and highlight the most significant findings, since recommendations on next steps can be derived directly from them. Use this executive summary as a teaser to distribute your findings to a larger audience within your organization.</p>
<p>Last, but not least will the follow-up also include the notes of the observers of other departments. Each of them should have identified the three most important issues for each interviewee, regardless of other interviewees reporting the same issues.</p>
<h4>The Debriefing</h4>
<p>The debriefing for the observers comes after the user test, and the interview protocols will be created in due time.</p>
<p>The meeting for the debriefing should not take longer than 30–45 minutes. The debriefing meeting will not only reflect the general findings of the tests, but it should also lead to and answer the question: “What can be done or should be fixed for the next user test?”</p>
<p>The protocols should be made available to all prospective participants before the next user test and should become a part of the agenda of the upcoming briefing meeting as a requirement for participation.</p>
<h3>What Did You Learn Today?</h3>
<p>This part of the “Lean User Testing” series covered the “action” of a user test: How to interview your interviewees, what you can expect from them and the proper closing of the user session with a follow-up and debriefing.</p>
<p>How many interviewees have you signed-up? Are some interview slots still available?</p>
<p>See you in part 6, when we talk about what to do with the findings and whether crowd testing might be an alternative.</p>
<h3>Related Posts</h3>
<p><a href="http://ift.tt/2tEhAjR">Part 3: Lean User Tests — Inviting Interviewees</a></p>
<p><a href="http://ift.tt/2slbtx5">Lean User Tests — Equipment and Location (Part 4 of 7)</a></p>
<p><a href="http://ift.tt/1NOpBSm">Four Lessons Learned From Making Customer Value Your Priority</a></p>
<p><strong><em>Please hit the “heart button” </em></strong><em>💚 </em><strong><em>below, if you found this post useful–it would mean a lot to me!</em></strong></p>
<p><strong><em>Do you want to read more like this? Well:</em></strong></p>
<ul>
<li>📰 <strong><em>Join 9,655 peers and </em></strong><a href="http://ift.tt/2hoWLQv"><strong><em>sign-up for this weekly newsletter</em></strong></a></li>
<li>🐦 <strong><em>Follow me on </em></strong><a href="https://twitter.com/stefanw"><strong><em>Twitter</em></strong></a><strong><em> and subscribe to my blog </em></strong><a href="http://ift.tt/1OEfX8K"><strong><em>Age of Product</em></strong></a></li>
<li>💬 <strong><em>Alternatively, join 1,250-plus peers of the new </em></strong><a href="http://ift.tt/2hoQGUk"><strong><em>Slack team “Hands-on Agile” for free</em></strong></a><strong><em>…</em></strong></li>
</ul>
<p><a href="http://ift.tt/2typ9J1">‘Lean User Tests, Part 5 of 7’ was first published in Age of Product</a>.</p>
<p><img src="http://ift.tt/2slpYAS" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="http://ift.tt/2tEp72l">Lean User Tests, Part 5 of 7</a> was originally published in <a href="http://ift.tt/2cAqCpx">prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Lean User Tests, Part 5 of 7

Lean User Tests, Part 5 of 7

TL;DR — Lean User Tests (Part 5)

Top Stories