<?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 Aubri Denevan on Medium]]></title>
        <description><![CDATA[Stories by Aubri Denevan on Medium]]></description>
        <link>https://medium.com/@aubri.denevan?source=rss-3eb4790b7106------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bgZVbIQ1CXJvZ4s2LNQliw.jpeg</url>
            <title>Stories by Aubri Denevan on Medium</title>
            <link>https://medium.com/@aubri.denevan?source=rss-3eb4790b7106------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:31:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aubri.denevan/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[A day in the life of a Sr. UX Researcher]]></title>
            <link>https://medium.com/alaskaair-guestdigitaldesign/a-day-in-the-life-of-a-sr-ux-researcher-c6de34b4d441?source=rss-3eb4790b7106------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6de34b4d441</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[airlines]]></category>
            <category><![CDATA[aviation]]></category>
            <dc:creator><![CDATA[Aubri Denevan]]></dc:creator>
            <pubDate>Mon, 07 Dec 2020 23:17:06 GMT</pubDate>
            <atom:updated>2020-12-08T00:02:00.116Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KF2pXm80ytPd8rlH0aSlOA.png" /></figure><p>Are you considering a career in UX research? Are you new to UX research and curious about how other researchers work at different companies? Or have you met someone recently who’s a UX researcher, but don’t know what that means?</p><p>I often get asked what my typical day consists of as a UX researcher at Alaska Airlines. I think the assumption of most — especially aspiring researchers new to the field — is that I spend all my time conducting evaluative usability studies. While that was true when I was a junior researcher, my role has expanded and changed quite a bit as I’ve moved into a senior role with the company.</p><p>When I was first starting out as a researcher, I was consistently running weekly usability tests. And if you are a junior researcher or just starting out in the field, running a lot of usability tests is an excellent foundation to have for future UX research work. But after a while, at least for me, it got to be very redundant and I wanted my work to have a bigger impact on the overall product strategy.</p><p>After a couple of years, I was able to make the move from solely conducting evaluative research into the foundational and strategic work I’m currently working on.</p><p>So, what do my days look like now?</p><p><strong>8:00 AM — Analyzing survey data</strong></p><p>I do a lot of context switching throughout the day, so I make sure I have set aside an hour or two first thing in the morning of dedicated time to complete any heavier analysis tasks while my mind is fresh. <br> <br>This morning, I set time aside to finish the analysis of results from two surveys fielded over the past couple of weeks. I ran these surveys to triangulate and quantify insights identified from several qualitative in-depth interview studies I completed the previous month. I also incorporated the survey results with the qualitative insights in a final report deck for an upcoming research readout in the week.</p><p><strong>9:00 AM — Student check-in on their final presentation</strong></p><p>Next, I sat in on a dry run presentation of a University of Washington’s HCDE program student group we’ve been working with to provide feedback on how they are presenting their research findings. At Alaska, we work with a lot of student groups throughout the year. It’s a great way to give back to the UX community and have fresh eyes to bring new perspectives to our ongoing research and design efforts.</p><p><strong>10:00 AM — UserTesting.com diary study collaboration check-in</strong></p><p>Over the summer, the team at UserTesting.com approached us with an opportunity to partner with their research team on a new diary study functionality they were testing out on their platform.</p><p>I met with the team at UserTesting.com to discuss the study’s progress, brainstorm ways to overcome a couple of minor challenges that had come up, and strategize on how we (both Alaska and UserTesting.com) plan to use the insights uncovered during the study. <em>Our teams co-presented this work on a UserTesting.com webinar in November 2020.</em></p><p><strong>11:00 AM — Skip level chat</strong></p><p>Normally, I talk with our UX Director a lot about very project-specific topics. But once a quarter, I’m able to sit down with her and have a skip level 1:1 chat on broader topics. I took today’s opportunity to ask some harder questions about the changes we’ve made during COVID-19 and the direction she envisions our team going once the pandemic is over.</p><p><strong>11:30 AM — Hackathon planning</strong></p><p>After my one-on-one meeting, another researcher and I met with several product and engineering leads from different areas in the company to help plan an upcoming internal hackathon.</p><p>Our part as researchers on the planning committee is to not only provide research resources to teams during the hackathon, but this time bring a number of identified customer pain points for participating teams to focus on solving and creating innovative concepts during the event. The pain points we identified for the hackathon are outside of work already prioritized in 2020 and early 2021. This allows teams to dig into new and exciting problems outside of their regular, day-to-day sprint work.</p><blockquote>TIP: Often there are user pain points uncovered during foundational studies that don’t get prioritized into sprint work. A hackathon is a great space for teams to work on those issues and create innovative solutions quickly that demonstrate the need for future sprint work.</blockquote><p><strong>12:00 PM — Lunch!</strong></p><p>With everything going on throughout the day, lunch is an important time for me to step away from the computer — especially when working from home during the pandemic. I usually eat my lunch outside (when it’s not raining) and play with my dogs in our backyard. Today was no different.</p><p><strong>1:00 PM — Strategic research workshops prep</strong></p><p>I just completed a 2-month strategic research study with another researcher on the team. As a part of the next steps, I had a 2-hour working session with another researcher to finalize the structure, activities, and remaining logistical tasks for three upcoming research workshops we have planned with product teams and stakeholders throughout the company. Each workshop focused on a different aspect of the research and ask participants to help tee up well-defined problems and opportunity statements for product teams to then take and ideate on when they were ready to begin working on them next year.</p><p><strong>3:00 PM — Presenting at the Monthly Business Review</strong></p><p>Every month, I analyze the user feedback we collect via a site intercept survey on our website and create a top 10 list of e-commerce related issues to share with our product teams. After presenting to leadership earlier in the month, I also walk through the list at the e-commerce monthly business review meeting. While I only present for about 5 minutes in the 30-minute meeting, it plays a vital part in bringing the “why” behind any issues flagged by looking at the site’s analytics trends the Business Intelligence team presents on first.</p><p><strong>3:30 PM — UX Research team check-in</strong></p><p>With all of us on the research team working on different efforts, it’s important to check in with each other a couple of times a week. We are a highly collaborative team and value the opportunity to share findings and insights each of us uncovers. All our work in e-commerce is very interconnected so these check-ins allow us to leverage each other’s work to make our own work stronger and more holistic.</p><p><strong>4:15 PM — Wrapping up for the day</strong></p><p>I like to use the end of the day to make sure I haven’t missed any emails or instant message chats throughout the day. I also do a quick check to see what my day looks like tomorrow — and prepare as needed.</p><p><strong>5:15 PM — Time to sign off for the night</strong></p><p>After I turn my computer off for the night, I still monitor my email and instant messages just in case something comes up.</p><p>— — — — —</p><p>Hopefully, that answered some of your questions about what UX researchers do on a regular basis. Although every day is truly different, this is a “day in the life” snapshot that demonstrates the breadth of projects I work on at Alaska Airlines and highlights the balance of time I spend conducting research and influencing product decisions with key findings and insights throughout the company.</p><p>Still have questions about the UX research field? Leave them in the comments section below — I’m always looking for future article ideas!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6de34b4d441" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alaskaair-guestdigitaldesign/a-day-in-the-life-of-a-sr-ux-researcher-c6de34b4d441">A day in the life of a Sr. UX Researcher</a> was originally published in <a href="https://medium.com/alaskaair-guestdigitaldesign">Alaska Airlines Design &amp; Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>