<?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 Danna Wulf on Medium]]></title>
        <description><![CDATA[Stories by Danna Wulf on Medium]]></description>
        <link>https://medium.com/@dannarenee?source=rss-1004f744b864------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MWJLkZH9RSxdxWzqTKbC5A.png</url>
            <title>Stories by Danna Wulf on Medium</title>
            <link>https://medium.com/@dannarenee?source=rss-1004f744b864------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:10:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dannarenee/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 we began a conversation with our users]]></title>
            <link>https://medium.com/insider-inc-engineering/how-we-began-a-conversation-with-our-users-268b0eb36a2?source=rss-1004f744b864------2</link>
            <guid isPermaLink="false">https://medium.com/p/268b0eb36a2</guid>
            <category><![CDATA[user-feedback]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Danna Wulf]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 13:57:38 GMT</pubDate>
            <atom:updated>2021-11-01T15:34:23.432Z</atom:updated>
            <content:encoded><![CDATA[<h4>Co-written with Ingrid Lederman</h4><p>User feedback is critical to crafting good UX. At Insider, the User Experience and Design (UXD) team works with product leads and engineers to continually improve the user experience for our large, global audience.</p><p>A key part of our process is incorporating feedback from our users, something which began in a relatively small way, but which has evolved into a full-fledged, stakeholder-backed, integral part of our design approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b6pJnlPUWH2z1_y6LTWtmw.png" /></figure><h3><strong>Getting crafty: starting from zero</strong></h3><p>We ran our first <a href="https://www.gv.com/sprint/">design sprint</a> in the fall of 2018. It was both an exciting and intimidating process. The process typically requires prototyping ideas and testing them with real users. But a few things stood in the way towards implementing this process: we didn’t have a budget for a research team or dedicated platform to engage with our users.</p><p>But we had to start somewhere. We began soliciting colleagues’ friends and family members by a simple company-wide Slack request. We were searching for those who we knew enjoyed Insider and would be amenable to providing feedback on improving their experience of our brand. Soon, we were able to video interview some of our most passionate Insider readers via Google Meet.</p><p>This specific set of users were highly invested in our product and excited to share their experiences. The passion with which they shared their experiences only increased the motivation we had to continue these types of conversations.</p><p>Going forward, we knew we needed to eliminate potential biases in test groups by expanding the group of participants beyond just friends and family.</p><p><strong>Lesson: </strong>Just start! Identify what’s holding you back, whether it’s how best to communicate with users, some financial barrier, or bandwidth issues. Be resourceful and use what you do have available. You’ll find that perceived hurdles aren’t as insurmountable as you may think.</p><h3><strong>Proving value: How we got more resources</strong></h3><p>As our belief in the importance of user feedback grew, we wanted to get buy-in from key stakeholders at the company to continue our efforts.</p><p>During our first design sprint, we tested three concepts to find the most successful paths for article recirculation. Qualitative feedback from user interviews allowed us to confidently pick a solution from among these three options, which resonated most with users.</p><p>We then presented this newly chosen approach to colleagues and stakeholders. Making the case for the solution was made easier as we were able to refer to video clips and quotes from conversations with users that helped us make our decision.</p><p>Ultimately, continually showing a clear connection between user insights, and how they improved our decision-making, enabled us to get more support for more thorough user feedback tools. (<a href="https://www.usertesting.com/">UserTesting.com</a> was our platform of choice.)</p><p><strong>Lesson:</strong> Show the value of user testing to your organization. Present your feedback-driven insights regularly. (As for UserTesting.com, a popular platform for engaging with customers in real-time, your organization can likely set up a free trial with the company.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z2XadoZ1cu-txapckEPixw.png" /></figure><h3><strong>Habit: Integrating user feedback into our routine</strong></h3><p>In Q1 of 2020, we began experimenting with how we could improve homepage engagement. We aimed to prototype, test, and validate many of the exciting ideas we had been filing away.</p><p>After a few design sprints, we found that our approach to user validation was becoming too time consuming for a small team like ours. We were spending a lot of time crafting unique scripts for each concept, and sifting through lengthy verbal feedback from users, which stalled the process of iterating towards a better user experience. We needed to find a more effective and efficient way to run user tests within our two-week sprint cycles.</p><p>At the same time, we hired our first UXD intern, who brought a strong foundation of user research to the team. With a fresh perspective, more support, and a focus on efficiency, we created a user testing template for scripts (check out our template <a href="https://docs.google.com/document/d/1AdT66124-mmfRfLrrFszGl6O9EA-Q0mFZwg2BYgxoTk/edit?usp=sharing">here</a>), allowing us to automate part of the process. We soon were on a roll; with consolidated resources and re-usable documentation, we were able to make rapid concept validation a staple of our experimental process.</p><p><strong>Lesson: </strong>Make user feedback part of your routine. It will enable quick innovation and validation for new concepts. Make sure the routine is attainable within your bandwidth and timeline — and be ready to constantly adjust to your needs!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qobAjtrc6BzHwa48WoQ4ag.png" /></figure><h3><strong>Communication: cross-team collaboration and sharing value</strong></h3><p>As user testing started playing a bigger role across multiple teams, we recognized the need for more communication channels that could encourage transparency and knowledge sharing between individuals and teams getting user feedback across our organization.</p><p>In mid-April 2020, we formalized a user testing team to champion the process by putting bi-weekly meetings on the calendar, creating a new Slack channel, and an email alias. These channels enabled regular communication, more collaboration, and were helpful steps towards evangelizing the value of user testing.</p><p><strong>Lesson</strong>: Formalize a task force, open up communication channels, and shed more light on user insights regularly through presentations and knowledge sharing sessions across your organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD1iTtMgVFoFhYqZ7uxsJw.png" /></figure><h3><strong>Application: insights leading to innovation</strong></h3><p>As we talked to more users, we began to better understand their needs on a more holistic level. We saw clear trends in user behavior, which gave us more opportunities to innovate and scale existing features.</p><p>In March 2020, in the<strong> </strong>time of the pandemic, uncertain facts, and ever-changing narratives, we began to identify three needs in user behavior surrounding news consumption of the coronavirus: urgency, convenience, and accessible information. These also resonated with users when it came to other big, upcoming news topics such as the 2020 election.</p><p>We built variations of existing features that addressed the three needs we identified.</p><p>While on the surface, these news stories were completely different from one another, we demonstrated how we could leverage our existing tools and relevant user insights to build new and timely features for the election, and to monitor the markets and other big events on the horizon.</p><p><strong>Advice:</strong> Identify user behaviors that you are seeing over time and discern patterns and themes from the data. Look for opportunities to scale, innovate, and leverage existing features to fulfill the needs of different users<em>. </em>Ask yourself: <em>How can we apply this knowledge elsewhere? Will these insights be helpful for an upcoming feature build?</em></p><h3><strong>Scaling: both a retrospective and look forward</strong></h3><p>User testing is now integral to our workflow, and we’re inspiring others outside of product and design to also do more user testing. Engineers and stakeholders have shown enthusiasm in the process and have recognized its role in validating design decisions.</p><p>Looking back to the beginning, we can reflect on what it takes to make user testing a natural part of our process. The effort required work and commitment, but it was worth it because it has made our product better.</p><p>We are still refining how we gather user feedback, and still have some questions about our workflow that we’d like to resolve, including: should we have a dedicated user researcher role or have the design and product team continue to “own” the process? What other tools could help improve our work?</p><h4><strong>We’d love to hear from you!</strong></h4><p>What are <em>your </em>experiences with user feedback? How have you incorporated it into your workflow? What challenges have you faced and how did you overcome them? What are you still working through? How does your user feedback process differ from ours? Please add your comments below and let’s keep this conversation going!</p><p>Special thanks to the product managers, engineers, and fellow designers who have supported this journey.</p><p><strong>Come work with us, we’re hiring a </strong><a href="https://www.linkedin.com/jobs/view/2638607901/?capColoOverride=true"><strong>UX/UI Designer</strong></a><strong> to join the team!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=268b0eb36a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insider-inc-engineering/how-we-began-a-conversation-with-our-users-268b0eb36a2">How we began a conversation with our users</a> was originally published in <a href="https://medium.com/insider-inc-engineering">Inside Business Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>