<?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 Lacey Lawrence on Medium]]></title>
        <description><![CDATA[Stories by Lacey Lawrence on Medium]]></description>
        <link>https://medium.com/@laceyirvin?source=rss-f095682e1802------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Dc-iUATuiOWSbjRfM64TFQ.jpeg</url>
            <title>Stories by Lacey Lawrence on Medium</title>
            <link>https://medium.com/@laceyirvin?source=rss-f095682e1802------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:22:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@laceyirvin/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[How to Avoid feeling Overwhelm During User Research]]></title>
            <link>https://laceyirvin.medium.com/how-to-avoid-feeling-overwhelm-during-user-research-869f78d42c68?source=rss-f095682e1802------2</link>
            <guid isPermaLink="false">https://medium.com/p/869f78d42c68</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[overwhelmed-at-work]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[feelings]]></category>
            <dc:creator><![CDATA[Lacey Lawrence]]></dc:creator>
            <pubDate>Wed, 22 Apr 2020 15:56:26 GMT</pubDate>
            <atom:updated>2021-10-10T02:10:03.856Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*noxz4KEqUbjwcTG7SD8-mg.gif" /></figure><h3>How to Avoid Feeling Overwhelm During User Research</h3><p>As someone with mid level research experience I know all too well the feeling of overwhelm and anxiety triggered from starting a new research project. Here are some tips to help keep calm and move on during the beginning of the research phases.</p><h4><strong>Do Preliminary Research</strong></h4><p>Get a sense of the overall space before diving into the “heavy” research. I typically spend 2 hours or so with few constraints set. If the client has an existing product, I search software reviews and forums for existing customer opinions, tools, and environment. This is a way for me to get familiar and comfortable so that my mind feels less overwhelmed in the kickoff meetings where we set the research focus.</p><h4><strong>Set a focus even if the client does not</strong></h4><p>It’s the first day of the engagement and the first thing out of the clients mouth is: We’re eager to learn about our product’s users! Or we’re just looking to improve the experience. There’s no way a company would hire you without knowing exactly what they want, right? User experience is an umbrella term encompassing disciplines from research, testing, design, accessibility and more. Not all clients think about user experience or user research in the same way. Our job is to set the stage so that we find insights and present actionable recommendations that benefit the business and users. You can avoid aimless research by asking product teams and stakeholders to expand on exactly what they’re eager to learn about their products users. A product owner may say “We want to know if the app is confusing or if it’s easy to use?” And the CFO may say, “I want to know if the users care because if they don’t, why spend the money?” Might not seem like much but it’s a starting point to knowing what to ask, what to test and how to measure the data.</p><p>Here are a few more questions to keep in mind in the beginning to help frame the focus</p><ul><li>Can you give me 3 tasks in particular you suspect to be confusing in order of priority and tell me why?</li><li>Has there ever been user testing within the last 5 years?</li><li>Are you currently collecting user analytics?</li><li>Do you know if the app is ADA compliant?</li></ul><h4><strong>Pick and stick to your tools</strong></h4><p>This is important because the right tools can make or break the workflow and there are a ton to choose from. I’m used to diving in and learning new tools for designing and prototyping but my research workflow is fixed. I use Evernote to keep all docs, interviews, questionnaires, product manuals and more in one notebook. Evernote allows you to store large PDF’s, add images in notes and create a tagging system for clearer organization. , I use Miro for journey maps, empathy maps and collecting insights from interviews. Miro is my favorite collaborative tool to brainstorm and organize thoughts and the ever expanding board is great for making sense of all of it. The board contains anything from hypothesis to details we want to test further. It helps us to prioritize and ensure nothing falls through the cracks.</p><h4><strong>Research with the final presentation in mind</strong></h4><p>Large companies often have multiple departments for conducting, creating and presenting the final research but I’ve yet to experience this phenomenon. Decks or presentations are a valuable asset when presenting research if you plan for a structured story so decide which images and resources to add and consult with your visual designers. As a researcher that often creates the deck, I recommend thinking about themes or calling out quotes you want to highlight as you uncover insights and add it as you go. Start a folder of stock images, graphics or the companies brand assets to add a personal touch.</p><p>Here is an example of a slide outline for a beginning research engagement.</p><ul><li><strong>Title Slide</strong></li><li>Overview</li><li>Intro Paragraph</li><li>Action Bullets (What We’ve Done)</li><li><strong>Research method Results</strong></li><li>Chart/Graph w/ Data</li><li>Highlight “interesting” data points</li><li>Pictures or clips from session recordings</li><li><strong>What We’ve Learned</strong></li><li>Theme</li><li>Supporting bullets to support theme</li><li>Patterns, behaviors or results from analytics / testing</li><li>A quote from user or stakeholder to support the current theme</li><li><strong>Summary / Recap slide</strong></li><li>Recap all themes</li><li><strong>Recommendations</strong></li><li><strong>Next Steps</strong></li></ul><p>I hope this helps ease any concerns for other mid level researchers that may have felt overwhelmed by the process. Remember, you know you best so trust your gut and stay driven by the goal of uncovering useful human insights to improve the experience and I promise, you’ll be good.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=869f78d42c68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Problem Cost Our Client Millions In Lost Revenue, We Solved It In 4 Weeks.]]></title>
            <link>https://laceyirvin.medium.com/case-study-this-problem-cost-our-client-millions-in-lost-revenue-we-solved-it-in-4-weeks-2413a268776?source=rss-f095682e1802------2</link>
            <guid isPermaLink="false">https://medium.com/p/2413a268776</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Lacey Lawrence]]></dc:creator>
            <pubDate>Wed, 31 Aug 2016 18:40:41 GMT</pubDate>
            <atom:updated>2017-02-25T05:30:00.011Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Theres a reason why technology and politics are not for the weak. The endless problems one encounters working in these fields can drive a person to madness. Good design however can solve any problem, no matter how big or messy. I joined the product team at the political technology startup Circa Victor in May 2016.We had 4 weeks to concept, design and launch Redline, an enterprise solution for multi-media corporations that are tired of losing money.</blockquote><h3>The Problem</h3><p>The client (A well known Multi-Media Corporation) approached us with a problem.</p><ol><li>Political committees <em>spend money</em> faster than they can raise it, making it difficult to pay their bills.</li></ol><p>2. Broadcasting companies<em> lose millions</em> each year when political committees cant pay for booked airtime.</p><p>3. Selling media services without knowing which committees can afford is risky.</p><h4><em>Product strategy</em></h4><p><em>Identify The Problem: A </em>Multi media corporation hates loosing money when a political committee defaults and cant pay, this makes targeting new customers increasingly risky.</p><p><em>Service To Solve It: </em>Circa Victor is here to design a product that prevents revenue loss through awareness. The product will inform the media corporation on which committee’s are safe to target based on the likelihood of default.</p><p><em>How to Achieve It: </em>The product<em> </em>will determine the chance of default by tracking the committee’s expenditures, donations and cash on hand data. We will assign each committee with a healthy, risky or safe label based on defined data parameters.</p><h3>The Process</h3><p>According to the data, most of the defaults occurred when there was a spike in spending. We invited the clients analytics team to meet with our data scientists. The data team worked to refine the burn rate model by identifying the rate of money coming in to the rate of money going out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-1Ztr2-YS-uu3dc_1WLx7A.png" /></figure><p><em>Default Event- A</em>ny occurrence of a campaign canceling a buy after the cancel-by date, defaulting or announcing intention to default.</p><p><em>Burn rate</em> — the ratio of a campaign’s spending to its assets.</p><p>Our data scientist worked closely with the client and created a predictive algorithm of when a campaign will miss its payments. With expenditure and donation data from early as January 1, 2010, we created simulated default-events around expenditure surging periods.</p><p>The results were 87% accurate, this confirmed our assumptions about the default events. The next step was to figure out the design for the data.</p><h4>Designing The Interface</h4><p>How does a human easily digest this information without feeling overwhelmed or out of the loop? We played around with geocoding and choropleth maps; using location to refine results and heat maps to relay risk. Unfortunately, the maps required more work for the engineers and we only had 4 weeks so we kept going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zbVt0BbRY7sKYRe62ml1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xUe2Gt0AD1CmAxWMXEhmcw.png" /><figcaption>The maps were labor intensive and not ideal for such a short deadline. Names and figures blurred per confidentiality agreement</figcaption></figure><p>We continued our design research: evaluating heuristics, exploring data visualization and graphing solutions towards a clean deliberate interface with interactive graphs and tables.</p><h4>Design, Test, Revise</h4><p>Designing with data allowed us to pinpoint problems faster and explore potential edge cases and their exceptions. Instead of coming up with simulated scenarios or false names in a prototype, the interface was designed with live data.</p><p>We designed the original risk concept with progressive and regressive bars but the flow was not as seamless as we hoped. We faced an inevitable user quandary with the risk visual: the bars say bad but the numbers look good.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7y13dtPz_IEWWVafVvpXmw.png" /><figcaption>Risk chart Before</figcaption></figure><p>We reworked the visual concept and went with a static front and center label. I imagine all elements of UX design as a sentence. Can the user look at your design and form a complete sentence based on the order of visual elements?</p><p>This sentence says: The first committee is risky with a 97% chance of defaulting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IQH_JYgCCU1qpolyaE3rJQ.png" /><figcaption>Names and figures were changed per confidentiality agreement.</figcaption></figure><p>Redline rates the health of a committee by analyzing the current activity and recent trends. We designed a visual story about the committee’s annual spending activity and divided it based on the span of a campaign cycle.</p><p>4W = A month — a minimum span of time to view a trend<br>3M = A single fiscal quarter <br>6M = Two fiscal quarters<br>1Y = Almost the entire campaign cycle</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n2mxMvaRJNDiNbQL-VbpoQ.png" /><figcaption>Names and figures were changed per confidentiality agreement.</figcaption></figure><p>The user can hover over any day within a 90 day date range and discover the committees exact amount of cash on hand.</p><p>Spending data was categorized for broken down into percentages. Clicking on a committee triggers a detailed spending report in a pop up modal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kgpCDh5quHTan0EGn0L35Q.png" /><figcaption>Names and figures were changed due to confidentiality agreement. A detailed modal contains breakdown of committee spending.</figcaption></figure><h3>The Final Product</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FXBGCc3wnWyYvOzHK-x2YA.png" /></figure><p>Broadcasters and Media Corporations use Redline to target new customers, assess financial risk, and ultimately save hundreds of millions of dollars in lost revenue.</p><h4>Future Applications</h4><p>Thanks to the success of the product and the hard work from the engineers, Circa Victor developed an API with Redline data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hqLJx5Xs0sUnnHyUoYpXfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2l4I7dLSZI-XFbLSE9J2hw.png" /><figcaption>Names and figures were changed to per confidentiality agreement.</figcaption></figure><h4>My Experience Working For A Startup.</h4><h4>Quote</h4><blockquote>Everything you do in a startup makes a difference. No longer are you surrounded by a safety blanket world where you’re a small cog in a large machine. In a startup, everything you do will contribute to the ultimate success or failure of the business. -Adam Arbolino, Tech Crunch</blockquote><p>I was really nervous when I got this job because I didn&#39;t know what to expect. I don&#39;t consider myself an expert in politics and big data was intimidating to me. I felt comfortable doing user experience so I pushed my UX agenda from day one but I didn’t get far. The chief product officer made it clear that him and I would be involved in every aspect, not just user experience. We worked in an agile scrum environment with a weekly rundown on Tuesday and product recaps on Fridays. I was tasked with designing sales deck presentations for the growth team and made revisions based on feedback after sales meetings. I learned to love the capabilities of data and embraced the limitations and turning points in the design process. I led bug review meetings with engineer and used Github to track progress.</p><p>Most importantly, I worked in the same room with the three founders of the company. Not only did I have a front row seat when things went wrong but I was an audience participant that helped get the show back on track. I can&#39;t thank Circa Victor enough for giving me this opportunity and I&#39;m so excited to see what they do next!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2413a268776" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>