<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Deirdre on Medium]]></title>
        <description><![CDATA[Stories by Deirdre on Medium]]></description>
        <link>https://medium.com/@deirdre_lyon?source=rss-a071e6479e7b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*m61h2ay12O7oL1QLxqsvPA.jpeg</url>
            <title>Stories by Deirdre on Medium</title>
            <link>https://medium.com/@deirdre_lyon?source=rss-a071e6479e7b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:58:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deirdre_lyon/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Anatomy of a Research Findings Presentation]]></title>
            <link>https://medium.com/toast-ux/the-anatomy-of-a-research-findings-presentation-639e9659b50d?source=rss-a071e6479e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/639e9659b50d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[wearetoasters]]></category>
            <category><![CDATA[research-reports]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Deirdre]]></dc:creator>
            <pubDate>Thu, 30 May 2019 14:59:05 GMT</pubDate>
            <atom:updated>2019-05-30T14:59:05.746Z</atom:updated>
            <content:encoded><![CDATA[<p>This post is about <strong>giving a presentation on qualitative research findings, </strong>including building credibility, storytelling and persuasion. It<strong><em> </em></strong><em>is not about</em><strong><em> </em></strong>writing a report. There are <a href="https://uxdesign.cc/how-to-not-present-your-ux-findings-8c2bce341e00">many</a> <a href="https://www.nngroup.com/articles/actionable-usability-findings/">great</a> <a href="https://uxplanet.org/a-ux-review-framework-anyone-can-use-4218d4821d6c">resources</a> on that already, as well as some <a href="https://uie.fm/shows/spoolcast/erika-hall-cultivating-shared-understanding-from-collaborative-user-research">constructive</a> <a href="https://medium.com/@tsharon/the-atomic-unit-of-a-research-insight-7bf13ec8fabe#.34h11em65">debate</a> about whether or not it’s worth doing; I highly recommend opting for a presentation if you’re choosing between the two, although there are alternatives as well.</p><p>Some of the reasons to choose giving a presentation over writing a report:</p><ul><li>It gives you an opportunity to build your presentation and storytelling experience</li><li>It provides your audience with a clear opportunity for engagement and discussion</li><li>Folks who need an artifact afterwards can dig more deeply into the deck, or other artifacts coming out of the research — they don’t necessarily need a written report (let’s get real, very few stakeholders are actually digging into a written report anyway)</li><li>I find it much easier to create a deck than to write a paper, and I know I’m not alone in that</li></ul><p>If those don’t convince you, check out <a href="https://medium.com/u/f72ac9381707">Kyle Soucy</a>’s excellent presentation on storytelling from this year’s Boston UXPA conference, <a href="https://www.youtube.com/watch?v=kEp6cj5Dlms&amp;feature=youtu.be">Gather Round: How to Share the Stories from UX Research</a>.</p><p>Pretty much everything below is optional; I will often include things or leave them out based on the size of the research project, the level of awareness of the audience or the amount of time I’m committing to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoQp4k2Klx1e9IU-xbvhag.jpeg" /></figure><p><strong>Intro</strong></p><p>This can be as simple as a title slide. I love a clever title, but it’s obviously not necessary; do include your name and the date, though. I didn’t think those were necessary in a Google Drive world, but we use PDFs in our repository, so we need that information in the actual artifact.</p><p>Also, name the file <em>the same thing</em> as the title of the slide. It should include the name of the product, team or product area (if applicable) and the word “research” somewhere so it’s easier to search for later.</p><p><strong>The Why</strong></p><p>This is the business context for the project. If you’re using Tomer Sharon’s <a href="https://www.smashingmagazine.com/2012/01/ux-research-plan-stakeholders-love/">The UX Research Plan that Stakeholders Love</a> (which I suggest you do), you can include the background, the goals and/or research questions here.</p><p>Other information that can be helpful here, especially if you can have a PM present it (it demonstrates collaboration!):</p><ul><li>Quantitative data from analytics, surveys or secondary research</li><li>Sales or support data, especially if it addresses win, loss or churn rates</li><li>Competitive intelligence</li><li>Any kind of projection or prediction, especially if it highlights some assumptions the business is making</li></ul><p>If you’re presenting qualitative findings to a group that includes some quantitative thinkers (and almost all groups of stakeholders do), this is an opportunity to demonstrate that you’ve done your numbers homework too.</p><p><strong>Process</strong></p><p>Including information about process is a double-edged sword. It could build your credibility as a researcher and educate audience members about the amount of effort that goes into research; it could also bore your audience, further the stereotype that UX is process-heavy or open the door to endless questions about sample size and validity.</p><p>Include <em>more process</em> when:</p><ul><li>You can present it confidently; the more confidently you present it, the fewer questions you will get about sample size</li><li>You feel prepared to answer endless questions about sample size or other aspects of the process</li><li>You have an engaged audience thirsty for more details about process (this is rare; if you think you have this, I suggest you think again)</li></ul><p>Include <em>less process </em>when:</p><ul><li>Your audience doesn’t have the patience for it, or already trusts you to handle it</li><li>You think it may encourage your audience to focus on the methodology rather than the findings</li><li>You don’t have a lot of time, or want to use the time you do have to focus on other information</li></ul><p>The elements of process I typically include (if any) are:</p><ul><li>Sample size, plus any details about the sample breakdown I believe my stakeholders will need to feel confident about the findings</li><li>Method, with a brief description of why I chose that method for the project</li><li>The team, including co-researchers — I love to bring stakeholders with me so this list can get a little long!</li></ul><p>You may have noticed I am what some might call “overly concerned” with questions about sample size. I freely admit that they are the bane of my professional existence, which I actually don’t think is a super mature attitude for a researcher to have. I’m working on it.</p><p><strong>Workflow</strong></p><p>This is where you really start to dig into the findings. I usually break this down into high-level findings and then in-depth detail; if you have a M-XL size project with multiple themes, you can treat each theme as its own section and do this for each.</p><p>If there’s a workflow we’re discussing, I usually try to lay this out in the order of the workflow, or the order in which users are making decisions. This gives the audience a loose sense of chronological order that can help them orient themselves, and it gives me a framework that makes my life easier.</p><p><em>High Level</em></p><p>This can take any form that makes sense. You can use a one-sentence statement here to introduce a theme, you can break it down into a job to be done — whatever makes sense in terms of fidelity for the story you’re telling.</p><p>If your research findings contradict assumptions stakeholders, or the business as a whole, have previously made, I like to use a “What We Thought vs. What We Learned” format. You have to frame it carefully or it can come off a little abrasive: I include myself firmly in the camp that made the assumption, and then present the findings with a “wow! Can you believe?!” tone. I know when I’ve done it well when my audience follows the story through that plot twist (although I recommend socializing the twist with your stakeholders beforehand).</p><p><em>In-Depth</em></p><p>I tend to think in workflows, so when I go into detail it’s often an in-depth look at the microdecisions users are making during the interaction I’m studying with the social, emotional and functional factors in play throughout. I’ll visualize this as a timeline, a storyboard or a series of steps, or if I’m lucky I’m collaborating with a designer who steps in here.</p><p>Synthesis often leads to an overview of the path most users take; that’s often what I present here, but if there are other common workflows or workarounds those deserve coverage here too.</p><p>If I’m presenting to leadership or fitting into an otherwise tight agenda, this becomes part of the appendix. If I’m presenting to an audience that’s enthusiastic about research or will be working on any roadmap items resulting from the research, I’ll go into this kind of detail during the presentation.</p><p><strong>Can You Believe!?</strong></p><p>You will probably have some really interesting findings that don’t fit into the framework above, but that you really want to share: great details that humanize your users, or wild workflows you felt lucky to catch even if they were outliers. If there are details that don’t fit but you feel are too powerful not to share, you can include them here.</p><p><strong>Wrapup</strong></p><p>This is the party favor section; you wrap things up in neat little bows so your audience can walk away with something tangible.</p><p><em>Takeaways</em></p><p>These are the sound bytes your audience can use to talk about your research outside of the room and the project. One of my personal metrics of success is hearing research I’ve been a part of discussed when I’m not part of the conversation — this can really help here.</p><p>This should be 3–6 major themes coming out of the research, ideally framed in language familiar to your stakeholders and IDEALLY ideally tied to larger strategic themes important to the business. If you’re using <a href="https://www.slidescarnival.com/">Slides Carnival</a>, most decks have a slide with about 6 small sections of text; this works really well here.</p><p><em>Next Steps</em></p><p>You know you’ve told a great story when your audience asks “How can I be involved?” This is where you tell them. It’s also important to demonstrate that research has impact beyond furthering the organization’s knowledge about its users; concrete next steps here suggest momentum.</p><p>Here are some kinds of next steps I typically include — again, it’s especially helpful if you have a PM, designer or other partner who can co-present:</p><ul><li>Designs based on research findings</li><li>Roadmap items resulting from research</li><li>Business opportunities uncovered by research</li><li>Research findings framed as hypotheses the team is interested in testing</li><li>Design thinking exercises you might use to get the most out of the findings, like ideation</li></ul><p>If your culture is very solution-heavy, there can be <em>a lot </em>of anxiety around presenting findings from a research project that didn’t lead to clear solutions. There are so many reasons this can happen — many of them are permutations of “the problem was more complicated than we thought.” There are several things you can do to socialize this:</p><ul><li>Set expectations with key stakeholders early and often, so no one is surprised</li><li>Frame discussions of the findings around the immense value of what you learned —it’s so much better to be diving deeper into a problem than putting effort into a solution that won’t solve it</li></ul><p>And remember you’re not alone! Human beings <em>love</em> to solution; we’re built for it, and taking a step back to investigate the problem space doesn’t always come naturally to us. That means UXers are change agents no matter the culture they’re working in.</p><p><strong>Questions</strong></p><p>The final slide I present is generally a “Thanks! Questions?” slide with my contact information. I always dedicate about 1/3 of the time I have to questions because I think it’s important for the audience to engage, and have an opportunity to be heard. It also allows me to focus on the story I want to tell rather than trying to predict every question and answer it as part of the presentation.</p><p><strong>Appendix</strong></p><p>As a librarian, I love to cite my sources! And an appendix can be useful for the occasional stakeholder who wants a deep dive, or for new folks who are getting up to speed.</p><p>The kinds of things I usually include in an appendix are:</p><ul><li>Slides I put effort into buy ultimately didn’t make the cut</li><li>Process information, if I didn’t include it up front</li><li>Links to research plans, scripts, prototypes, designs and any other artifacts used in the research</li><li>Relevant secondary research</li></ul><p><strong>A Few Logistics</strong></p><p><em>Touchpoints</em></p><p>If you’re still building credibility with your stakeholders, using existing touchpoints like demos and regular update meetings will help integrate research into the team’s vocabulary and regular cadence. My general rule is that if there’s an open agenda, I can add a findings presentation to it.</p><p>Once you’ve generated some excitement around research, these touchpoints are still valuable but you can also reach for a larger audience and try out things like brown bag sessions or webinars.</p><p><em>Templates</em></p><p>I highly, highly recommend <a href="https://www.slidescarnival.com/">Slides Carnival</a>. The templates are free and easy to use, you can import them right into Google Slides, and they have slide formats that work well for most of the sections I outline below. And if you work in a PowerPoint-heavy culture where folks tend not to think outside the company template, they can really make a splash.</p><p><em>Repository</em></p><p>Presentations like this should live in a research repository. Like a written report, very few folks will actually dive in, so it’s not necessary to put a ton of effort into but it’s an important marker of what research has accomplished and a great place to send new hires.</p><p><strong>Thanks! Questions?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=639e9659b50d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/toast-ux/the-anatomy-of-a-research-findings-presentation-639e9659b50d">The Anatomy of a Research Findings Presentation</a> was originally published in <a href="https://medium.com/toast-ux">Toast UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Queer Eye Taught Me About UX Research]]></title>
            <link>https://medium.com/@deirdre_lyon/what-queer-eye-taught-me-about-ux-research-289b2918c860?source=rss-a071e6479e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/289b2918c860</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Deirdre]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 20:52:25 GMT</pubDate>
            <atom:updated>2018-09-04T20:52:25.598Z</atom:updated>
            <content:encoded><![CDATA[<p>If you haven’t watched the new Queer Eye on Netflix, go. Now.</p><p>OK! Now we can talk. Like many other Netflix viewers, my life has been permanently bettered by the new Fab 5. What would Tan wear? What would Karamo counsel me to do here? And how can I be as much like Jonathan as possible with every single breath?</p><p>One of the most interesting things that has emerged for me, though, is how many lessons I come away with as a UX Researcher.</p><p><strong>Everyone Asks The Tough Questions</strong></p><p>The way the 5 <em>ask</em> fascinates me<em>. </em>They don’t shy away from the intimate, and they don’t just leave it to Karamo, the closest they have to a counselor. Even Antoni, the foodie whose territory seems like it should mostly consist of Instagram-worthy salads, asks pointed on-screen questions about familial relationships.</p><p>The confidence with which they ask is inspiring because it fosters a confidence in answering. The (mostly) straight men don’t shy away, and often answer very frankly. I’ve been inspired to confidently ask questions I used to see as tough — questions about finances, about procrastination, about any number of things I think participants might feel shame about. And like the show, people <em>answer</em>!</p><p>When I started asking confidently, I realized I had been projecting my own shame onto participants and impeding the success of my own sessions. By framing the questions without hesitation, I‘m telling participants there’s nothing to be ashamed of, which leads to more forthcoming and honest answers.</p><p><strong>Be Vulnerable</strong></p><p>The men getting made over aren’t the only ones sharing. My favorite moments are when the Fab 5 share pieces of their own history and deepen their connections. Bobby talking about growing up gay in an evangelical household helps him connect to the Christian father. Karamo sharing his reaction to being pulled over broadens the white cop’s perspective. And … we all cry.</p><p>By sharing with participants, I put them at ease and make a connection that helps me get great, honest, organic data. I’m not exactly sharing deep history or past trauma — for example, I recently talked with a nervous participant about our favorite Trader Joe’s snacks (peanut butter pretzels &amp; frozen Indian food, respectively). Her hands stopped shaking, we started making more eye contact and I could see her getting more comfortable — which eventually helped her give great, self-reflective feedback about the designs in front of us.</p><p><strong>Be the Bobby</strong></p><p>On the show, most of the hour is spent on the guy himself. Hair done, new clothes, a pep talk from Karamo + a cooking lesson and he’s transformed. Meanwhile, Bobby toils in the background toward the <em>big</em> reveal, the part that makes most of the guys (and their families) cry: the house. Unless there’s a proposal (which there sometimes is), this is usually the part of the episode with the most impact.</p><p>I recently worked with the incredible <a href="http://www.gv.com/">GV</a> team on a <a href="http://www.gv.com/sprint/">Design Sprint</a>, culminating in a day of research led by <a href="https://medium.com/@mmargolis">Michael Margolis</a>. While I participated alongside the team in the entire process, Michael was in and out, doing the recruiting, scheduling, scripting and general heavy lifting to make Friday a success. Watching my colleagues follow the sessions — some of them seeing research for the first time — I immediately thought about that moment the audience &amp; the makeoveree see the house for the first time, and how exciting and enlightening that moment is.</p><p>Michael stepped back from the day-to-day activity of the sprint to plan for a part of the work that is just as important as the strategy and decision-making, but requires a different kind of labor to be effective. When it all came together, Michael’s craft had the same impact as Bobby’s taste + talent. Well, okay, no one cried, but they definitely felt like they had a clearer vision for their future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=289b2918c860" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starbucks’ Birthday Drink is my Favorite Brand Touchpoint]]></title>
            <link>https://medium.com/@deirdre_lyon/starbucks-birthday-drink-is-my-favorite-brand-touchpoint-a8b7174a3ed1?source=rss-a071e6479e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8b7174a3ed1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[birthday]]></category>
            <dc:creator><![CDATA[Deirdre]]></dc:creator>
            <pubDate>Thu, 14 Dec 2017 23:18:18 GMT</pubDate>
            <atom:updated>2017-12-14T23:18:18.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzMcPu9DyD-TvdalXi5HlA.jpeg" /></figure><p>I’m a birthday humbug. I like to have a piece of cake with my husband, get some texts from my friends and hear my grandparents sing me happy birthday over the phone — that’s pretty much it. Any bigger deal is just embarrassing.</p><p>But I have a new birthday tradition: a grande peppermint mocha. I have one once a year because, well, sugar and money. But I <em>love </em>them, and Starbucks makes me one happy customer every year when they offer me one as a celebration of my birthday.</p><p>Here’s how it works:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k0_0hHIFf3thKdBzs7HM0A.png" /></figure><p>So it’s not only the mocha and walking into work with a red cup — it’s how <em>easy </em>it is tailor the entire experience to my taste.</p><p>I know Starbucks isn’t for everyone, and I’m sure my blatant consumerism isn’t either. But I am annually delighted by this experience. Also, happy birthday to me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8b7174a3ed1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Communicating the Research Process]]></title>
            <link>https://medium.com/@deirdre_lyon/communicating-the-research-process-b2b850129cd2?source=rss-a071e6479e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2b850129cd2</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Deirdre]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 15:27:51 GMT</pubDate>
            <atom:updated>2017-12-05T15:27:51.839Z</atom:updated>
            <content:encoded><![CDATA[<p>Compared to Slack and Flowdock, email sometimes feels old. Traditional, in a stuffy way. But while communication tools may be shifting towards more immediate, immersive interaction, the dominant medium at my company is still email. The higher you get up the hierarchy, the more true that is. And I bet I’m not alone.</p><p>Which is why I’m finding it worthwhile to teach a junior member of our research team the communication etiquette I’ve spent years unconsciously accumulating. I’m sharing those lessons because I think there are strategies here for all UXers in terms of <strong>getting clarity</strong>, <strong>socializing research</strong> and <strong>making UX work visible </strong>via email.</p><p><strong>The Meeting Followup</strong></p><p>This sounds small, but it’s important in the early stages of a project or with a new set of stakeholders. I send one of these emails every time I discuss anything researchers and stakeholders need to collaborate or agree on. Whether it’s a formal meeting, some light Slacking or a hallway encounter, if there’s an action item or something shared, I put it in writing in a <strong>meeting followup.</strong></p><p>What’s usually included:</p><ul><li>Action items, both mine and stakeholders’</li><li>The specifics of anything agreed on</li><li>URLs or attachments for anything referenced during the interaction (previous findings, NNG articles, Google Material Design resources, etc.)</li></ul><p>Ultimately, these conversations become a more formal research plan; we use Tomer Sharon’s <a href="https://www.smashingmagazine.com/2012/01/ux-research-plan-stakeholders-love/">The UX Research Plan That Stakeholders Love</a> as a framework. <strong>Getting clarity</strong> in these earlier documented conversations helps <strong>build agreement</strong> when asking for <strong>stakeholder signoff</strong> at that later stage.</p><p><strong>The Pre-Session Email</strong></p><p>This strategy works well with stakeholders with extremely busy schedules. I believe in bringing stakeholders into the research process whenever possible, but the higher up a stakeholder is in the organization the harder it is to schedule.</p><p>That’s why I send a <strong>pre-session email </strong>— a polite reminder combined with some context that will help stakeholders feel ready to sit down with a participant.</p><p>What’s usually included:</p><ul><li>Date, time &amp; location, parking information if relevant</li><li>What to bring in terms of notetaking</li><li>Participant’s name and role in the sample (“Second graduate student in the sciences,” “First public library non-user,” etc.)</li><li>Overview of where we are in terms of data gathering (“Second session of five”)</li></ul><p>After making these emails a best practice, I’ve noticed an increase in stakeholders arriving to sessions <strong>on time</strong> and <strong>ready to engage </strong>with participants, as well as <strong>speaking more confidently</strong> about project progress to other areas of the business.</p><p><strong>The Post-Session Email</strong></p><p>Participant sessions build up a lot of energy, especially for stakeholders who are connecting with users for the first time. I love to get coffee with stakeholders and co-researchers after a session to debrief and foster those responses, and a <strong>post-session email </strong>can take those positive connections even further.</p><p>What’s usually included:</p><ul><li>Participant’s role in the sample (this sometimes gets shared, so I omit identifying data)</li><li>A few highlights from the session</li><li>My cleaned-up session notes</li><li>A recording of the session, if available</li><li>A teaser for the next session, especially if there’s an opportunity for stakeholders to attend</li></ul><p>This email gives stakeholders a <strong>tangible product</strong> from the session without having to wait for the full findings report and <strong>keeps the project fresh</strong> in the team’s collective mind. I’ve also found that for stakeholders who attend only one or two sessions, it reduces the tendency to overemphasize those participants’ perspectives.</p><p>Previously I’ve also included observations about developing patterns, especially if we’ve already conducted a few sessions. Stakeholders responded to it, but I found that identifying patters too early in a project led to <strong>confirmation bias</strong> in later sessions so I no longer recommend it.</p><p><strong>The Findings Summary</strong></p><p>While I’m lucky to work at a company of informavores who will devour a report, session notes AND raw data, an executive summary of findings is essential to get themes across at different levels of the organization. I pair the <strong>findings summary </strong>with the report itself and send it to the executive team, expecting that it may be the only part of the report many of them read.</p><p>What’s usually included:</p><ul><li>3–5 bullet points highlighting major themes from the project with key terms in bold and explicit connections to business priorities</li><li>An invitation to a presentation of findings (if there is one)</li><li>The agreed-on deliverables as attachments</li><li>A link to the deliverables’ home on the team repository</li></ul><p>If this summary hits a good balance of being short and touching on business values, it’s likely to be shared and can help <strong>socialize research findings </strong>and <strong>demonstrate alignment</strong> with business needs.</p><p><strong>The Monthly Update</strong></p><p>This gets shared more than any other communication and drives more questions about our work, via email and otherwise.</p><p>What’s usually included:</p><ul><li>Recent highlights with links to relevant artifacts in the team repository</li><li>Upcoming studies, including any opportunities for colleagues to join sessions</li><li>Summaries of UX articles relevant to business priorities</li><li>Any other opportunities to engage with the team</li></ul><p>This communication has been a breakthrough for our team in terms of <strong>socializing research findings</strong> and <strong>making UX work visible </strong>throughout the organization. We’ve had an especially positive response to the summaries of UX industry articles — our knowledge on these points has helped establish us as experts with a responsibility for educating our colleagues.</p><p>It can be a challenge to keep up with a monthly update; first it becomes bimonthly, then quarterly, then slowly fizzles out. Right now, my strategy is to make each team member responsible for a topic they’re enthusiastic about and check in with them regularly. I’ll let you know how it goes!</p><p>Email may seem like an outdated way of communicating research findings internally, especially in a development environment that thrives on timeliness and efficiency. But the email strategies outlined above have helped us <strong>establish good working relationships</strong> with stakeholders, <strong>promote our work </strong>within the organization and highlight the ways we <strong>align with business priorities.</strong></p><p><em>Do you have communication best practices, email or otherwise? Let me know!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2b850129cd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fieldwork makes me nervous]]></title>
            <link>https://medium.com/the-field-study-handbook/fieldwork-makes-me-nervous-6de4493cf718?source=rss-a071e6479e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6de4493cf718</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Deirdre]]></dc:creator>
            <pubDate>Wed, 24 May 2017 16:16:51 GMT</pubDate>
            <atom:updated>2017-05-26T16:57:47.644Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>But it’s worth it.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9TbbQCKLWrDp2S3iHVvVw.png" /><figcaption>This is what I mean when I say I overplan. TripIt for monitoring travel; Google Maps for checking traffic <em>well </em>in advance; ParkWhiz to mitigate parking panic; Toilet Finder to mitigate bathroom panic; Yelp app to make sure wherever I’m going has wifi and I can eat something vegan afterward; Two Dots in case the participant is late and I don’t want to be seen anxiously monitoring the door. And that’s all before I shake the participant’s hand.</figcaption></figure><p>First, there’s traveling to where your participant has identified as the right place for you to see what you want them to show you. I don’t <em>love</em> going new places, so there’s always some overplanning — Google maps, checking traffic days in advance, figuring out parking, making sure there’s a bathroom; the logistics are tough, not even counting recruiting in the first place.</p><p>Then, there’s meeting someone I don’t know. As an introvert, this is already rocky, but fieldwork means travel and travel means not being able to recharge using my own familiar routines. And as a woman, well, this can feel like a risk.</p><p>Then there’s the self-doubt: Will I know the right thing to say? What if I miss something and stakeholders decide the whole project is a bust? What if it’s <em>awkward</em>? Triple all of this if you’re bringing a stakeholder along because going in without a script — without control over what you’re going to get out of it — can feel like a crisis if you haven’t done it before.</p><p><strong>But then you get to this moment: the point where the <em>magic</em> happens.</strong></p><p>You’ve talked a little bit about how each of you got there, maybe you’ve complimented the participant’s shoes, or watch. Then all of a sudden there’s a subtle shift, like you’re moving into high gear. You’ve made a connection, you’re slipping into a groove — the self-doubt falls away because you remember how to ask and how to listen.</p><p>As much as I love this part and how good it feels to remember that I know how to do this, this is actually the part that makes me the <em>most</em> nervous because this is where participants get really honest. You’ve built something between yourself and the participant, and as much as I as an ethical researcher want to believe it only goes one way, I would be lying if I said I wasn’t affected deeply by my participants.</p><p>I’ve had participants tell me about tough childhoods, or about doing things that are definitely illegal. I had a participant talk about moving from Africa to the United States without being able to read or write her own name and the transformation that happened when she got access to education. I once had a participant misinterpret this connection and ask me on a date. Things can get intense.</p><p>And I’m grateful for that intensity, for what participants are willing to share with me that helps me tell the story of their <em>lives</em>, not just the pain points they encounter on a single platform. Turning stakeholders into advocates — that’s what powers a good user experience, and it’s the moments that participants share with me that make that possible.</p><p>I guess what really makes me nervous is that I fall in love with every participant just a little.</p><p>— —</p><p><strong><em>Deirdre Costello </em></strong><em>is the Director of UX Research at EBSCO Information Services. She is a user experience professional passionate about discovering how technologies fit into users’ lives and their pursuit of information.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6de4493cf718" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-field-study-handbook/fieldwork-makes-me-nervous-6de4493cf718">Fieldwork makes me nervous</a> was originally published in <a href="https://medium.com/the-field-study-handbook">The Field Study Handbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>