<?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 Rasa Jonkute on Medium]]></title>
        <description><![CDATA[Stories by Rasa Jonkute on Medium]]></description>
        <link>https://medium.com/@rasajonkute?source=rss-7f3627418b57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1HPJnV-uvKXhYbRlDbqLzA@2x.jpeg</url>
            <title>Stories by Rasa Jonkute on Medium</title>
            <link>https://medium.com/@rasajonkute?source=rss-7f3627418b57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:14:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rasajonkute/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 improve collaboration between Design and Data teams]]></title>
            <link>https://medium.com/design-bootcamp/case-study-design-and-data-collaboration-f397f17b2daf?source=rss-7f3627418b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/f397f17b2daf</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Rasa Jonkute]]></dc:creator>
            <pubDate>Fri, 08 Mar 2024 13:44:16 GMT</pubDate>
            <atom:updated>2024-07-28T14:31:25.614Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design x data: the ultimate collaboration playbook</h3><h4><em>When envisioning collaboration between data and design teams, people often use symbols like the brain and heart for distinction. However, this simplification tells us nothing about the magic that occurs when two disciplines work together to create experiences that deeply resonate with users.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77NIsPYUywHJx1zjGVGDIg.png" /></figure><p>Not sure what that looks like? Below is a list of recommendations based on what I’ve learned by partnering with the data team throughout the design process of building Review Insights for consumers at Trustpilot.</p><h4>1 - Collaborate with other disciplines to see the big picture</h4><p>To understand why design and data need to work together, consider the story of “The Blind Men and an Elephant.” In this parable, each blind man interprets the elephant differently based on the part they touch. One feels the trunk and thinks it’s like a snake, another feels the ear and thinks it’s like a fan, and so on. None of them alone can fully comprehend what an elephant truly is. Likewise, in product development, we encounter complex problems that we approach from our respective areas of expertise. By collaborating, design and data can build a more comprehensive understanding of complex problems and find better solutions.</p><h4>2 - Mix your research methods for better triangulation</h4><p>Triangulation is the practice of using multiple sources of data, or multiple approaches to analyzing data, to enhance the credibility of a research study. Every designer should employ various research methods, combining qualitative and quantitative insights, even without a data partner. Considering new and complex problems teams encounter, collaboration between design and data allows them to utilize unique knowledge and methods to discover deeper insights and solutions than they would uncover alone.</p><p>Spotify beautifully introduced the concept of <a href="https://spotify.design/article/simultaneous-triangulation-mixing-user-research-and-data-science-methods">Simultaneous Triangulation</a>, where both teams: (i) Clearly define research objectives to facilitate collaboration, (ii) Identify complementary methods in different quadrants to balance strengths and weaknesses, and (iii) Implement methods concurrently for comprehensive insights. This approach helps reduce the risk of unexplained discrepancies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gairb3Torhoc6zYgUNQIvg.png" /><figcaption>UX research method matrix</figcaption></figure><h4>3 - Involve the Data team from the beginning to align and explore common goals</h4><p>Nobody wants to be pulled into a project at the last minute. Ensure that you involve your data partners early in the process. Can they assist in defining the problem? Does their roadmap potentially intersect with your plans?</p><p>At the start of our project, we had a data model for showing popular mentions on company profiles, but we knew that users didn’t find it useful. We wanted to discuss the data team’s perspective and determine if we could work together on improving it. What we discovered was that the team was already developing something for businesses, which could also be applied to our project. We aligned our goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OJtb_VsWPGXMMN6SjYxQZw.png" /><figcaption>5 whys root-cause analysis</figcaption></figure><p>My product team wanted to improve the current solution by building Review Insights, a feature that would add sentiment to popular mentions. To define the problem, we asked numerous “Why?” questions and leveraged existing knowledge about users. We knew that when people evaluate a company, they usually look at its profile. They care about the TrustScore, how many reviews there are, and the star rating. They also want to see if there are any common problems, especially in negative reviews. To do this, they filter out 1-star reviews and read them carefully, which can be tedious work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3RXYSxMlPrrAmZzFhHOwTg.png" /><figcaption>Previous design of filters containing popular mentions</figcaption></figure><h4>4 - Collaborate with the data team to gather evidence of a problem’s existence</h4><p>We already had qualitative insights about issues related to the reading experience on Trustpilot. However, having data partners provided us with quantitative insights on the topic, increasing our confidence that the problem existed. Based on the data points we had, we built the following story map and scoped our project to focus on improving these pain points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDyrqlQbGPJuceW-yZEgoA.png" /></figure><h4>5 - Ideate and collaborate on design concepts as a team</h4><p>People who build models often have fantastic ideas for visualizing concepts! Add developers and UX writers to the mix, and you can discuss the feasibility of the ideas you’ve generated in the same meeting. We brainstormed multiple ideas, which we then consolidated into the following concepts based on feasibility and what we wanted to explore further as a team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qOAyyThqG0gCdkUcsqfVQ.png" /></figure><h4>6 - Challenge the content you include in your designs — is the data realistic enough to get the most out of your testing?</h4><p>Using Lorem Ipsum in designs is convenient, but you’re missing out on the opportunity to learn some important design nuances. For testing the design concept we proceeded with, we used real data to populate our prototypes. This approach gave us insights into how the model works and whether topics make sense to users. Should we only highlight the most popular topics? Or do people care about a mix of positives and negatives?</p><h4>7 - Keep everyone in the loop during the test</h4><p>Find a way to involve your stakeholders in testing to advocate for good design and explain why it’s crucial to put it in front of users. I conducted a debrief with my product and data team. After the debrief, we decided what we wanted to improve — the confusion around numbers and graphs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CL7puiYchU-ZmaT0iG9rCA.png" /></figure><p>The second iteration performed significantly better. We gained the confidence needed to release the first version of Review Insights on the Trustpilot mobile app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bE7UznbGpDtodZ1LQZloMg.png" /></figure><h4>8 - Check in if are you making the impact you want to make, and iterate accordingly</h4><p>Throughout the first 7 weeks, an average of 3.8% of weekly CPP viewers clicked on a topic tile. This is 7.2 times higher than the interaction with the previous implementation of Popular mentions. Additionally, 47% have clicked “See reviews” to read further into reviews on a particular topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eqA0A833zfU4NMHv" /><figcaption>Discussing the impact</figcaption></figure><h4>Start small and improve with every project!</h4><p>When kicking off your next project, try some of the recommendations from the list above to get the most out of collaboration between design and data teams. Notice the change in your process of building delightful user experiences!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f397f17b2daf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-design-and-data-collaboration-f397f17b2daf">How to improve collaboration between Design and Data teams</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From research to decision: how to use the campfire principle to engage your team]]></title>
            <link>https://tech.trustpilot.com/from-research-to-decision-how-to-use-the-campfire-principle-to-engage-your-team-71bb4012126a?source=rss-7f3627418b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/71bb4012126a</guid>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[synthesis]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[facilitation]]></category>
            <dc:creator><![CDATA[Rasa Jonkute]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 08:44:11 GMT</pubDate>
            <atom:updated>2020-01-21T11:46:42.030Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2i3JDpxYIBk8ezHX" /></figure><h3>Building a shared understanding is a challenge</h3><p>Making even small decisions as a product team can be challenging when everyone has their own individual understanding of a problem. Because of that, a big part of my work as a designer is to help build shared understanding by facilitating, rather than just executing design. In a perfect world, I’d invite the whole team to observe all interviews or usability sessions for every round of research we do. But this kind of <a href="https://library.gv.com/ux-watch-parties-543d22b1478d">UX Watch Party</a> quickly takes up the time of up to ten people. It’s hard to synchronize something as time-consuming as that with all the other activities that happen during a sprint.</p><p>The workshop this article dives into is one I designed and executed in my team with great success. It allowed us to share learnings, build shared understanding quickly, and decide on the next problem to focus on.</p><h3>Time to gather around the campfire</h3><h4>Everyone has a voice and a story to tell</h4><p>Enriching research findings with (user) stories helps to bring research participants and their needs to life. It allows us to champion their experiences and bring their voice into the design process. But even a perfect research report isn’t enough to keep the team engaged, as it’s only one-way communication.</p><p>This is where a campfire is different. It acts as an informal gathering where everyone participates. As <a href="https://gamestorming.com/?s=campfire">Dave Gray</a> writes, “Campfire leverages our natural storytelling tendencies by giving players a format and space in which to share stories.” Instead of a designer talking, the whole group brings their authentic perspective, and with it their diversity and sense of ownership.</p><h4>Share understanding to share stories</h4><p>Using simple card models and drawings while telling stories helps to deconstruct stories and confirm everyone understand them the same way. Having visuals can inspire and encourage your team members to build even further on top of your model. You can then reorganize bits and pieces together. The result? A shared understanding that includes everyone’s contribution. Next is the visual voting and ranking of issues. This helps the team to identify and focus on the next problem to work on.</p><p>The documents we created helped us recall details and decisions that emerge during effective collaboration. Jeff Patton compares the simplified visual model you create as a result to vacation photos.</p><h3>How we play</h3><h4>Start by including more storytellers</h4><p>Don’t do your user interviews all by yourself! Make sure that your other team members have their own stories to tell during the workshop. I always invite the Product Manager and at least one developer along to my interviews so they can hear customers’ stories first-hand. Instruct them how they should take <a href="https://www.nngroup.com/articles/group-notetaking/">notes</a>, and share insights afterwards.</p><p>I’ll use the example of the learnings I shared with my team during the upgrade experience project for Trustpilot’s customers.</p><h4>Time to play the game</h4><p><strong>Assign. </strong>The goal is to hear (user) stories from different people, not only from the designer leading the research. If you have more people in the room than stories to share, split them into groups based on the interviews they’ve observed. For my project, I conducted five interviews and then had a workshop with ten people in the room which resulted in five working groups.</p><p><strong>Think (10 mins).</strong> Each group has a story (or an interview) they need to present to the whole group. Give everyone some time to go through their notes to refresh their memory. I also hand out transcripts with the main insights from specific interviews as a cheat sheet.</p><p><strong>Write (10mins).</strong> Ask groups to write down a sequence of the story on sticky notes. These golden nuggets of information help others understand, remember and built on top of your story later. Multiple-color sticky notes help to label and recognize interviews. For my project, colors helped us to identify companies on different subscription plans: Lite, Pro or Enterprise.</p><p><strong>Say and place (5 min each).</strong> It’s showtime! Every group tells an authentic story as they place sticky notes on the whiteboard. You can draw a line on the whiteboard to indicate a timeline that has a beginning and an end. For my project, the beginning was “Signing up” and the end was “Buying a subscription”. After 5 presentations we had 5 parallel lines on the board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8nhNEndEKhJmf05rd116g.png" /></figure><p><strong>Organize (15min).</strong> After everyone has presented their stories, it’s time to start working on unifying the story/journey as a team. Try to arrange (approx.) your sticky notes across the timeline so that things happening at the same time are stacked one below the other. Name the big steps. For my project, we ended up with these: 1) Signs up for Trustpilot; 2) Reaches the limits of a Free plan; 3) Searches for information on paid plans; 4) Contacts Sales; 5) Buys a subscription.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qjeEGP_f8iAv0pwpuWAH0Q.png" /></figure><p><strong>Focus</strong> <strong>(15min)</strong>. With this model in front of you, you can now identify the pain points and positives of this journey. The next important step is defining what you learned and where you go next. My team assumed that adding the ability for users to upgrade their plans themselves would eliminate the need to contact Sales, and thus improve their whole buying process. But after mapping the user journey we realized the biggest problem was that none of the customers could actually choose a plan themselves. The content lacked specific answers, suggestions, and transparency around pricing, so people still needed to contact Sales. A shared artifact sparked a discussion around where we should focus as a team, and we switched from optimizing the checkout flow to improving content in the sprints that followed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NSJUrgoTzQd_RPyIGFh8JQ.png" /></figure><h3>Steer the product in the right direction</h3><p>Life is too short to designing things that don’t change anything. The campfire method works because it brings your research to life, it helps your team build a shared understanding quickly, and it enables you to decide on the next thing to focus on in order to steer the product in the right direction.</p><blockquote>“It was fun, and I learned so much in so little time.” A developer from my team.</blockquote><blockquote>“We knew we had problems with content, but it was hard to grasp how big it was and prioritize it. This workshop helped us update our plans for the next sprints.” Product Manager.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71bb4012126a" width="1" height="1" alt=""><hr><p><a href="https://tech.trustpilot.com/from-research-to-decision-how-to-use-the-campfire-principle-to-engage-your-team-71bb4012126a">From research to decision: how to use the campfire principle to engage your team</a> was originally published in <a href="https://tech.trustpilot.com/">Trustpilot Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being responsive - from a checklist to a BINGO card]]></title>
            <link>https://tech.trustpilot.com/being-responsive-from-a-checklist-to-a-bingo-card-d8715f96ef12?source=rss-7f3627418b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8715f96ef12</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Rasa Jonkute]]></dc:creator>
            <pubDate>Tue, 02 Jul 2019 07:43:04 GMT</pubDate>
            <atom:updated>2019-07-19T13:30:50.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GliekUbESPGDi4g5l2L9NQ.png" /></figure><h3>Responsive design is only somewhat responsive</h3><p>When we talk about <a href="https://en.wikipedia.org/wiki/Responsive_web_design">responsive design</a>, we have a spectrum of devices in mind: screen size, platform, and orientation. We design for specific breakpoints so that content responds according to the device’s width, allowing us to provide users with the best possible layout. To track our progress, we use a checklist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_xKcOikBVjQqtTNgV_okiw.png" /></figure><p>But is <em>the device</em> the only variable we should be designing around? <a href="https://insanelab.com/blog/web-design/age-responsive-web-design/">Age-responsive design</a> suggests to also adapt the design to the users’ needs, preferences, and possible limitations based on age. For example, video content and bright colors are recommended for children, while text-based information and muted shades are recommended for elderly people. Although age-responsive design is barely practiced, the underlying message is important:<strong> users are as diverse as the devices they use.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVq-PKLcEwFmdeh2HSfsmg.png" /></figure><h3>[Insert important user differences]-responsive design</h3><p>I recently designed a user management feature for Trustpilot’s business app. The purpose of the feature was to help business users manage who has access to their company’s Trustpilot business account, and what level of access they have based on their roles/responsibilities.</p><p>For our first iteration, we built a table with an overview of the existing business users and a CTA inviting the user to add more teammates. Clicking on the button would open a modal with a form asking the user to provide the new teammate’s email, role, and a domain list representing the different markets or shops of the company.</p><p>Then we tested our prototype on users:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sOGewMVrLNwMlg2cVHTPFQ.gif" /></figure><p>“That number of domains doesn’t tell me much,” one user pointed out. He was looking for the list of markets or shops instead of domains. While a dropdown seemed fine to cover the extreme cases of companies owning hundreds of domains, data indicated most of Trustpilot’s customers only have one domain. With a better understanding of our diverse user base, we turned to the concept of age-responsive design as inspiration and tailored the experience for different users instead of designing a generic solution for all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YCvLczfP83aVkhdhJxlwWw.gif" /></figure><p>Just like the spectrum of age, Trustpilot’s business users are different in ways that are significant for how we should design solutions for them, e.g., the number of domains they own. With this in mind, we were able to see if the design was inconvenient anywhere, and we could make tweaks accordingly. We ended up with 2 <strong>breakpoints</strong>:</p><ol><li>Select all domains at once (if the user has more than one domain).</li><li>A search functionality (if the user has a long list of domains to choose from).</li></ol><h3>Hello BINGO format</h3><p>By indicating different design solutions via <strong>breakpoints</strong> we empowered ourselves to design a great experience for our diverse user base. And by adding an axis for devices, we moved from a checklist to a matrix:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LebJWzqicGa6-korljUASQ.png" /></figure><h4>User axis</h4><p>Fields 1 through 3 represent breakpoints, or design variations, from the perspective of users. Each type of user has their own desktop version — small business users, medium business users, and enterprise/agency users (with many domains).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lK2HUQQwM5UWSjW3QT0yew.gif" /></figure><h4>Device axis</h4><p>Each vertical column represents a traditional way of thinking about the responsive design. Here’s an example of moving through different resolutions from the perspective of a small company:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEPmMBLx72lzApdnUcDAuQ.gif" /></figure><h3>BINGO format beyond design phase</h3><p>Once the designer is finished designing, we’re never really done contributing to the final result. Developers come with questions, and sometimes ad-hoc tweaks are inevitable simply because we forget to think through important user differences. Fortunately, BINGO format helps during the development phase as well! It provides a more structured way to identify design variations and reduces the number of questions or problems later. This way, your team can deliver the best experience for your users faster.</p><h3>Ready to complete the card?</h3><p>Use this framework to empower your team and you so you can approach responsive design in a more structured and holistic way. Create a superior design that quickly meets the needs of your diverse user base.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8715f96ef12" width="1" height="1" alt=""><hr><p><a href="https://tech.trustpilot.com/being-responsive-from-a-checklist-to-a-bingo-card-d8715f96ef12">Being responsive - from a checklist to a BINGO card</a> was originally published in <a href="https://tech.trustpilot.com/">Trustpilot Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>