<?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 Eva Muck on Medium]]></title>
        <description><![CDATA[Stories by Eva Muck on Medium]]></description>
        <link>https://medium.com/@evamux?source=rss-c390c9fdbd32------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JBiOprJuW-j-Mw-vxdWiOw.jpeg</url>
            <title>Stories by Eva Muck on Medium</title>
            <link>https://medium.com/@evamux?source=rss-c390c9fdbd32------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:39:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@evamux/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[Exploring the human-AI relationship]]></title>
            <link>https://medium.com/design-bootcamp/exploring-the-human-ai-relationship-f5dae10a4d16?source=rss-c390c9fdbd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5dae10a4d16</guid>
            <dc:creator><![CDATA[Eva Muck]]></dc:creator>
            <pubDate>Tue, 13 May 2025 09:12:01 GMT</pubDate>
            <atom:updated>2025-05-14T11:45:56.341Z</atom:updated>
            <content:encoded><![CDATA[<h3>Exploring the human-AI relationship: lessons I’ve learned about people and AI</h3><figure><img alt="Human and robot shaking hands" src="https://cdn-images-1.medium.com/max/1024/1*AXFOl-jKm_wlem6SFijtJw.png" /></figure><p>I joined <a href="https://medium.com/u/b3088e3930e6">ColossyanHQ</a>, an AI video platform, a few months ago as the first full-time Senior UX Researcher to support decision-making with strategic research studies. During my first 3 months, I learned some interesting things about how humans perceive AI, and I wanted to share my experience on what patterns I see in people’s behaviour when we talk about AI.</p><h3>The paradox of instant AI content: the effort heuristic</h3><p>One of the first self-contradictions I observed was that most participants I’ve talked with expect AI to generate content immediately but they distrust instant content because they presume it will contain inaccurate information because of its speed. In other words, participants connect inaccuracy with AI’s speed, stating sometimes that “slower AI is better”.</p><p>This is a cognitive bias known as the effort heuristic. People assume that more effort (or time) invested into something means it has higher value or quality, even when the outcome is identical. (<a href="https://www.sciencedirect.com/science/article/abs/pii/S0022103103000659">Kruger et al.</a>)</p><p>This bias can appear in various situations, e.g. when the expected results come from yourself, someone else, or a product.</p><h3>When you expect results from yourself</h3><p>Chopin’s approach to composition was notably iterative. He often revised his works extensively, sometimes producing numerous drafts before settling on a final version. He couldn’t trust an idea until it had survived the furnace of numerous rewrites. Cello Sonata in G Minor, Op. 65, composed between 1845 and 1847, is a prime example. He produced over a hundred pages of sketches for this work before finalizing the composition. Such a rigorous approach often led him to revisit and sometimes revert to initial concepts after exploring numerous alternatives. (<a href="http://chopin.pl/">chopin.pl</a>) (<a href="https://academic.oup.com/book/58192/chapter-abstract/480952257?redirectedFrom=fulltext&amp;login=false">Wilson</a>)</p><h3>When you expect results from someone else</h3><p>I’m using Dan Airely’s example from the book <em>Dollars and Sense</em> which follows a story of a tradesperson who quickly fixes a problem in just a few minutes and the customer balks at the high bill saying something like “But it only took you five minutes!”. Even though the tradesperson not only fixed the problem but saved you precious time, you may have a feeling that their job is worth less than someone else’s who spent hours with that. We might undervalue when a job is done quickly and efficiently even though that speed comes from years of expertise and training. On the contrary, we may overpay for items that appear labor-intensive, even if they don’t provide proportional value. (<a href="https://www.goodreads.com/book/show/34323010-dollars-and-sense">Airely &amp; Kreisler</a>)</p><h3>When you expect results from a (AI) product</h3><p>Users might perceive AI-generated outputs as less valuable just because they’re created instantly — compared to something they might have crafted manually over hours. Users might undervalue AI-generated scripts, layouts, or videos simply because they’re produced too quickly. This could lead to over-editing AI outputs to feel like they worked for it or distrust automation even when it’s accurate. If more than 70% of users override or tweak AI-generated content within a few minutes of its creation, it might indicate that the effort heuristic is at play.</p><h3>Trust starts with control: what users need beyond instant outputs</h3><p>As ChatGPT, Claude, Gemini, and other popular LLMs became the part of everyday-life, their functionalities became the status quo. Participants expect tools to work the same way as the tools they already know. For example, research participants find conversational AI friendly and think that prompting gives them a sense of control. (<a href="https://lawsofux.com/jakobs-law/#:~:text=Users%20spend%20most%20of%20their,other%20sites%20they%20already%20know">Jakob’s law</a>)</p><p>Regarding control, this leads to my next point. People need to feel that they are in control and initial content should be indeed generated instantly with a prompt but there must be an option to <strong>refine </strong>it<strong> manually to feel the content is “theirs” and trustworthy</strong>.</p><p>Even though prompting gives people a sense of control, there are a lot of misunderstandings about the way it works. Every participant I talked with in the past 3 months (39) could mention an event when the tool didn’t get what they were saying and they had to change the wording and reiterate multiple times which led to frustration.</p><p>As there’s no general guide on what an efficient prompt should look like, it’s mostly self-taught, and people learn from their mistakes. At the same time, they have super high expectations of AI, and there’s a<strong> general confusion about what they can </strong>actually<strong> achieve with AI </strong>tools.</p><h3>What worries people about AI — and why it matters</h3><p>You’ve probably heard these concerns before, but I still want to call them out, especially if you build AI products. It’s important to think about the fears and doubts people have because some concerns will not only create negative feelings associated with a product, but will prevent people from using it altogether.</p><p>These fears include:</p><ul><li><strong>Losing uniqueness</strong>: Certain professions, especially those where human touch is key, require unique content to attract customers. These professionals fear that if they use AI, they’ll lose uniqueness and they receive results that other people already received.</li><li><strong>Overreliance on AI</strong>: People worry it might lead to decreased creativity and critical thinking.</li><li><strong>Privacy concerns</strong>: Corporate environments have strict rules for tools handling internal data. Certain professionals will have to go through a lengthy SaaS review process to prove that a tool is compliant with their privacy policy.</li><li><strong>Losing jobs</strong>: While genAI can be mind-blowing for someone, it can be a source of stress for those who fear they or others will lose their jobs due to AI tools’ promise.</li><li><strong>Ethical concerns</strong>: Using AI-generated content can feel like deceiving customers for some people.</li></ul><p>It’s crucial for AI builders to acknowledge and address these cognitive biases and concerns. By prioritizing transparency, user control, and ethical considerations, we can build AI products that are not only effective but also trusted and embraced by users. Ultimately, fostering a balanced understanding of AI as an assistant will be key to its successful integration into various aspects of life and work.</p><p>What do you think?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5dae10a4d16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/exploring-the-human-ai-relationship-f5dae10a4d16">Exploring the human-AI relationship</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[UX research in a zero-knowledge B2B company: balancing insights and ethics]]></title>
            <link>https://medium.com/tresorit-engineering/ux-research-in-a-zero-knowledge-b2b-company-balancing-insights-and-ethics-5dda098b3406?source=rss-c390c9fdbd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dda098b3406</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[zero-knowledge]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[ux-research-process]]></category>
            <dc:creator><![CDATA[Eva Muck]]></dc:creator>
            <pubDate>Fri, 16 Aug 2024 13:04:23 GMT</pubDate>
            <atom:updated>2024-08-16T13:04:23.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2ExtkvEUcYkjO6yfO4kkA.png" /><figcaption>Illustration inspired by Massimo Vignelli’s iconic NY subway design system</figcaption></figure><p>I’ve recently read an article about the <a href="https://www.linkedin.com/pulse/special-challenges-ux-b2b-part-1-access-end-users-tom-wolf-bauer/">Special challenges of UX in B2B</a> that inspired me to share my experience as a UX Researcher in Tresorit, a company that offers B2B products in a zero-knowledge environment.</p><p>Zero-knowledge companies operate on the principle that they should have minimal knowledge of the data their customers store or manage. This approach enhances security and privacy, making these companies attractive to customers with high security needs. However, this same principle creates a significant barrier for our UX research team, whose goal is to gather insights on user behavior, preferences, and challenges.</p><h3>The conflict: insights vs. privacy</h3><h4>When you’d like to know more, but you have zero-knowledge…</h4><p>Tresorit is dedicated to safeguarding product usage data to the extent that internal teams cannot have insights about customers’ files, not even knowing whether it is a document or an image.</p><p>For this reason, understanding how users interact with our products becomes quite challenging. The difficulty arises when we need to ask sensitive questions to understand how users manage their confidential data. Security-conscious users are often, quite understandably, reluctant to share information openly, fearing that any disclosure could compromise their security.</p><p>One common strategy in UX research is the <a href="https://psycnet.apa.org/doiLanding?doi=10.1037%2Fh0023552">foot-in-the-door technique</a>, where researchers begin with small, non-intrusive questions and gradually move to more detailed inquiries. This method can build trust and make participants more willing to share information. However, in zero-knowledge environments, even this technique can fall short. Customers may perceive any request for information as a <strong>potential conflict with the company’s value proposition</strong>, regardless of how gradually it is introduced.</p><p>The ethical dilemma for us on one hand, is that we must remain compliant with strict privacy and security protocols, ensuring that no customer data is compromised. On the other hand, we need detailed insights to inform business decisions and improve our products.</p><p>Remaining compliant means using tools and methodologies that respect customer privacy to the highest degree. This compliance can slow down the research process, as common methods of data collection may be off-limits.</p><p>Furthermore, we might need to rely on indirect data, such as <strong>anonymized usage patterns</strong>, which may not provide the depth of insight required for nuanced understanding and makes it difficult to optimize the product based on usage insights. This can result in putting more emphasis on qualitative research in decision making.</p><p>In the next section, I’ll focus on failed attempts and difficulties that come with the extreme security consciousness, but I don’t want you to feel that it’s a mission impossible. My aim is to raise awareness of the potential obstacles.</p><h4>Completing missing metrics with surveys</h4><p>When you have limited access to usage data, you try your best to find other methods you can cook with. In our case, we tried to gather missing quantitative data with good old surveys that sometimes are effective in our environment, sometimes they’re not.</p><p>Let me tell you the story of a survey that didn’t work out and what we’ve learnt from it.</p><p>We tried to understand how customers collaborate with external clients and partners in Tresorit. Our goal with the survey was to uncover trends within our target group of Tresorit users. After multiple emails, reminders and the involvement of our email marketing team, we only received 15 answers out of 937 contacts.</p><p>In the past, we shared a survey with a similar sample size and received around 200 responses. The difference was the <strong>sensitivity </strong>of questions, the previous survey contained high-level questions, whereas the latter survey included questions about <strong>volatility </strong>and <strong>content management </strong>between our customers and their clients.</p><p>In this case, we had to rely on user interviews solely to have a deeper understanding about external collaboration with Tresorit. Interviews make it possible to build <a href="https://www.nngroup.com/videos/building-rapport/">rapport</a> and provide a comfortable environment for the subjects that helps them to talk more openly, although quantifying qualitative data needs consideration to ensure that the essence of the qualitative data is not lost in the process.</p><h3>Juggling compliance and business needs</h3><p>Having previously worked on a nation-wide banking and finances application, I was familiar with the challenges of maintaining compliance in research processes. However, entering the zero-knowledge B2B environment introduced me to a whole new set of hurdles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FmeZ-QBnMkeMMAPfQ_Mh8A.png" /><figcaption>Illustration inspired by Massimo Vignelli’s iconic NY subway design system</figcaption></figure><h4>Administrative obstacles that may rain on your research plan</h4><p>During the discovery phase of a product concept, we followed the steps of the <a href="https://www.discoverydiscipline.com/en">Discovery discipline</a> by Rémi Guyot &amp; Tristan Charvillat. One of the stages suggested looking for group reactions of the value proposition, so we decided to organize a focus group session to trigger discussions and observe reactions.</p><p>We carefully selected several Tresorit customers with the help of the customer success team for a focus group session but unfortunately, we bumped into administrative obstacles. We’ve found out that the legal documentation, administration and the required coordination with other teams for such an event would have slowed down our ongoing research so much that we had to postpone it.</p><p>The administrative obstacles included a profound legal documentation of signing an extensive NDA with all participants and our internal signatories. In addition, involving employees from different companies would have exposed them to each other’s customer status and business needs, posing a risk to their business strategies. This proved to be cumbersome and ultimately unfeasible.</p><h4>Protect customer data with all your power</h4><p>Making sure that customer data is stored securely sounds like a no-brainer but handling data in a company with extreme data security and privacy focus is another level.</p><p>We maintain a close ongoing collaboration with our legal department to make sure our workflows are compliant. We have established together the following rules on how we must process customer data:</p><ul><li>Personal data (e.g. email, account number, etc.) and direct videos can never be shared on company-wide communication channels, only on a need-to-know basis with an end-to-end encrypted share link.</li><li>Datasets can be accessed by only those who have company authorized access to the relevant tool.</li><li>The data (e.g. interview recordings, usability test recordings) collected by the UXR team must be stored in Tresorit.</li><li>Only the UXR team has FULL access to the data. The access given to any confidential material goes upon request from the UXR team.</li><li>According to our internal data-retention policy, the data retention period is limited to 5 years starting from the Tresorit creation time of each file.</li><li>Once the retention period for a specific dataset expires, the UXR team is responsible for deleting the data.</li></ul><h3>Complex SaaS reviews</h3><p>Not only is the way we work strictly regulated, but the tools we use are also under the microscope of information security. When I started to work at Tresorit, I soon realized that the most commonly used UX tools are not compliant with the company’s principles. Some tools failed our internal SaaS review because of various privacy concerns:</p><ul><li>A tool has been denied because it would have processed Tresorit’s and our customers’ data for its own purposes by feeding the data into AI learning algorithms for use in Marketing and Sales.</li><li>Another reason for rejection was that we’d have to get our customers’ consent for the tool’s activities too, and their activities don’t align well with the values Tresorit stands for.</li><li>When practices regarding who is the data controller and processor are not clear based on the documentation, it’s also a disqualifying factor.</li><li>Last but not least, providing only the bare minimum regarding data security can be also a reason for rejection.<br>- E.g. if the tool only supports email-based 2FA for User Verification, (which is probably because that was the easiest to implement)<br>- or SSO-based login is behind the enterprise-wall.</li></ul><p>I find it important to highlight that Tresorit’s principles <strong>don’t approve of</strong> the usage of <strong>AI</strong> features with <strong>customer data</strong>. From an information security standpoint, feeding customer data into AI models is considered jeopardous, and it’s also questionable from a legal viewpoint. In the midst of AI revolution when most products and services are aimed at developing AI features, the question arises: <em>how can we keep up with the AI trend and maintain or even improve our processes?</em></p><p>Well, this question is for the future and for our information security team, so I’m leaving it open, but as an employee of a company with zero-knowledge policy I’m curious to see how such companies will adapt, stay up-to-date and compliant at the same time. (Is it even possible, I wonder?)</p><h3>Conclusion</h3><p>UX research in zero-knowledge companies is fraught with challenges, but it is not insurmountable. By prioritizing ethical considerations and being innovative in research methodologies, we can still gather valuable insights without compromising user trust. In the end, the goal is to create products that meet users’ needs while maintaining the highest standards of security and privacy. As Carl Jung said: <em>“Protection and security are only valuable if they do not cramp life excessively.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dda098b3406" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tresorit-engineering/ux-research-in-a-zero-knowledge-b2b-company-balancing-insights-and-ethics-5dda098b3406">UX research in a zero-knowledge B2B company: balancing insights and ethics</a> was originally published in <a href="https://medium.com/tresorit-engineering">Tresorit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How generative research about personal finances can help design your bank’s value proposition]]></title>
            <link>https://medium.com/design-bootcamp/how-generative-research-about-personal-finances-can-help-design-your-banks-value-proposition-45f12b37180b?source=rss-c390c9fdbd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/45f12b37180b</guid>
            <category><![CDATA[value-proposition]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[value-proposition-canvas]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[generative-research]]></category>
            <dc:creator><![CDATA[Eva Muck]]></dc:creator>
            <pubDate>Mon, 03 Jan 2022 13:03:41 GMT</pubDate>
            <atom:updated>2022-01-03T13:03:41.056Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Research approach</strong></h3><p>When we think about digital products, the main levels are the users, the product and the business. It means that users interact with a product that gives them value — hopefully. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g7zGyLZOqoqLO6aP4BRMAQ.png" /><figcaption>The levels of research</figcaption></figure><p>Organisations tend to concentrate mostly on the first two components which means the interaction of the user and the product. This is inevitably essential, but this model has two limitations.</p><p>One of them is that we assume that our solution is valid and the iterative correction of its usability will lead to a better product. This is true in case we have a deep knowledge of the original problem. The exploration of the problem is that we don’t consider the product research level.</p><p>The other limitation is that the business side is missing but research can provide valuable insights for the business as well.</p><p>We wanted to take research to the next step in order to achieve to work in the whole spectrum on the user-product-business levels.</p><h4>Job-to-be-done model</h4><p>Why is it crucial to research customers’ needs and way of thinking to create a bank’s value proposition?</p><p>Typically, financial institutes build their hypothesis thinking their solution is correct, e.g. if the customer needs money, they’ll get a personal loan.</p><p>But in the real world the thinking behind a decision is way more complex. It may turn out that a completely different solution is needed.</p><p>This is what fin-tech companies are aware of, they truly understand customer jobs and they create a different solution for their problems than incumbent banks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-W68iDYRzpGoJXgEFWCQ-Q.png" /><figcaption>JTBD solution example</figcaption></figure><p><strong>Example</strong></p><p>JTBD: Gotta pay deposit urgently to rent an apartment.</p><p>Banks’ solution: personal loan which comes with high interest rate, hard to understand banking terms, lots of paperwork.</p><p>Fin-tech solution: <a href="https://fronted.rent/">Fronted</a>, an alternative to large upfront deposits that comes with low interest rate, more manageable platform and comprehensible process.</p><p>Our goal was to better understand what kind of problems people have with money — regardless of banking solutions, and to gain a comprehensive picture of what their goals, difficulties and opportunities are. We needed generative research to get a deep understanding of customers’ real problems.</p><p>What’s worth mentioning regarding this model is that fin-tech companies often answer to one job-to-be-done while banks have to give a solution to tons of them.</p><h3>Phase 1: Baseline research</h3><p>This research was created to support the merge of three traditional Hungarian banks in redefining themselves.</p><p>The goal of the baseline research was to identify the main topics that we should dig deeper in the deep interviews later on to discover the complex picture.</p><p>The baseline included the following steps:</p><ul><li>Collecting the existing qualitative research materials from the three banks on personal finances</li><li>Desk research to review the publicly available findings of personal finances</li><li>Guerilla interviews (40) with friends and family on personal finances with the involvement of the broader team (product owners, designers, developers) to get a direction on recruitment and customer segmentation, furthermore defining further research questions</li></ul><h3>Phase 2: Deep dive on personal finances</h3><p>The goal of this phase was to understand the main goals and motivations of customers around their personal finances.</p><p>We defined the following steps in order to achieve that goal:</p><ul><li>Who we want to speak with: the segments for the recruitment</li><li>What we want to understand: the questions we want to explore=interview script</li><li>Recruitment: screener and selection</li><li>Qualitative deep interviews (55)</li></ul><h3>Phase 3: Synthesis of the learnings and creating research outputs</h3><p>UX Research may result in multiple outputs and it’s often easy to end up with a static report. Our goal was to reach a more extensive engagement throughout the organisation, so the stakeholders and the design team could better empathise with the customers.</p><h4>From Synthesis Monster to Public Insight Center</h4><p>We started to brainstorm and collect overall findings on a Miro board that soon became quite incomprehensible for those who hadn’t participated in the research process. The original purpose of this board was to use it as a notebook or exercise book.</p><p>Once we had a clear picture of the insights, we’ve created an insight center to provide an easy-to-digest and fun format that is accessible for everyone within the company. We also created a written document in parallel in case anyone would like to have a deeper understanding of the insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yl6VxwMN5Z9DacPQErmc_w.png" /><figcaption>Miro board evolution</figcaption></figure><h4>Visibility</h4><p>To make research more visible within the organisation, we‘ve opened a Slack channel called ‘Research nuggets’ which is used in the long run to drop research results in short summaries. The purpose of this channel is to have an open conversation about certain topics and involve the broader team in the research processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_R3vnrzgvqvZM1f-MkPWQ.png" /><figcaption>Research Slack channel</figcaption></figure><h4>Workshop</h4><p>Another way to involve the team in the research was to hold a customer journey workshop where we introduced different customer segments and defined their actions, feelings, pains, etc. together. This exercise helped other team members to step into the shoes of different customer segments and to think with their minds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*30q0zDpaTLtAW3iRxhiIGA.png" /><figcaption>Customer journey workshop</figcaption></figure><h4><strong>Research showroom</strong></h4><p>We also think that our message can be truly understood if we find another way to convey the insights instead of a frontal presentation. We’ve created a research showroom with deep-dive user stories and it was a great success in the team.</p><p>What happened is that we chose 20 random participants from the generative research in 4 age categories and introduced them to the broader team. Each story included the background of the person, the answers on what money means to them and what shaped their relationship to money. Besides these questions, we highlighted one detail which makes their story remarkable.</p><p>A story could be remarkable e.g. if someone had a unique technique for money tracking or had an experience with financial products that taught them something, etc.</p><blockquote>The main goal was with these deep-dive stories to bring customers closer to the stakeholders, developers and the design team by proving that in finances demographics are not necessarily relevant but the behaviour and attitude are the key components in creating financial products and services that customers truly need.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIaknHL9pRQ25fK-g9YFMA.jpeg" /><figcaption>Deep-dive stories</figcaption></figure><h3>Value proposition</h3><p>We’ve found that the format of the value proposition canvas is the one that makes it possible to help high-level leaders understand and utilise the research findings directly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*AWIaxz5hKszACi5quKpkLg.png" /><figcaption>Value Proposition Canvas</figcaption></figure><p>The canvas has two parts: the right side shows the customer segment where the gains, pains and jobs of the customer can be listed and the left side shows the answers to the customer profile — gain creators, products and services and the pain relievers.</p><p>What we’ve done is that we’ve created the customer profile — right side of the canvas — for each research participant — listing their gains, pains and customer jobs and facilitated a workshop with the value proposition team where we asked the leaders to think about the gain creators, pain relievers, products&amp;services and fill out the left-side of the canvas with their post-its.</p><p>Once the post-its were synthesised, the high-level value proposition was created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YuRFMC6LkLeGkwVJFhNvFw.png" /><figcaption>Creating value proposition together</figcaption></figure><h3>Main lessons</h3><p>This whole research took altogether almost half a year and we definitely realised a few things that we would do differently next time.</p><p>What we would focus on next time is to…</p><ul><li>work with a heterogeneous participant pool to consider some unique segments, e.g. rural people.</li><li>avoid mixing up quantitative and qualitative data, meaning: there’s a tendency to concentrate on quantifiable findings rather than qualitative in the research.</li><li>try to work in researcher pairs because conducting that amount of interviews and processing the data alone are overwhelming. Furthermore, it’s more beneficial for the team and in the creation of the insights to have more perspectives.</li></ul><p>I hope you found interesting and valuable thoughts in the article. Please, feel free to give any comments on it. I’m also happy to answer any questions if needed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45f12b37180b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-generative-research-about-personal-finances-can-help-design-your-banks-value-proposition-45f12b37180b">How generative research about personal finances can help design your bank’s value proposition</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[Record or not record? That is the question]]></title>
            <link>https://medium.com/design-bootcamp/record-or-not-record-that-is-the-question-1026087987dd?source=rss-c390c9fdbd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/1026087987dd</guid>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Eva Muck]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 01:06:57 GMT</pubDate>
            <atom:updated>2021-02-03T10:08:09.999Z</atom:updated>
            <content:encoded><![CDATA[<h4>When should be user interviews recorded?</h4><p>UX Researchers’ work methods may vary a lot. We come from <strong>different fields</strong> and different <strong>companies</strong> which form our <strong>work routine</strong> and <strong>approach</strong> to how we <strong>conduct research</strong>.</p><p>In <strong>UX Research,</strong> I really enjoy that you can decide which way is the most <strong>convenient</strong> for you to <strong>process</strong> data and create insights from <strong>interviews</strong>. You can come up with <strong>individual solutions</strong> and <strong>learn</strong> different techniques <strong>from</strong> your <strong>colleagues</strong>.</p><p>During one of our weekly video calls with the research team at <a href="https://medium.com/u/3c5f5e0ced0f">MKB Fintechlab</a>, we were talking about the process of interviewing customers and whether we should <strong>record</strong> the sessions <strong>or not</strong>. One of my workmates told us that he prefers not to record the conversations, which surprised me and <strong>made me think</strong>. I’ve always preferred to record every interview for multiple reasons — which I’ll list below — so I wanted to get to know his way of thinking on this topic; we <strong>discussed it</strong> and collected a few <strong>pros</strong> and <strong>cons</strong>.</p><p>Under recording, I mean a <strong>video</strong> where you can see the participant’s <strong>facial expressions</strong> and if possible their <strong>body language</strong>.</p><figure><img alt="Video Call of two people on a monitor" src="https://cdn-images-1.medium.com/max/1024/1*eiid9SnSKT9XjecJIUn-yQ.png" /><figcaption>Illustration from unDraw.co</figcaption></figure><h3>Recording Pros</h3><ul><li><strong>Won’t miss</strong> valuable <strong>information</strong> from the participant</li><li><strong>Data </strong>will be <strong>available</strong> in the future — <strong>more data</strong> <strong>is better than less</strong> because you never know when you’ll find a <strong>pattern</strong> or <strong>useful information</strong> in the <strong>later</strong> phase of the research process.</li><li><strong>Proof</strong> of content</li><li>The recording could be used for <strong>reports</strong>/<strong>workshops</strong>/<strong>education</strong> within the company/UX team…</li><li>…therefore <strong>different perspectives </strong>could be obtained</li><li>…plus recordings can be <strong>great assets</strong> to<strong> evangelise</strong> <strong>research</strong> within the company and make <strong>stakeholders</strong> <strong>empathise </strong>more with the customers</li><li><strong>Verbatim quotes</strong> are easier to <strong>remember </strong>in the future</li><li>It’s easier to analyse data by adding <strong>timestamps</strong> to the most interesting parts</li></ul><h4>What could be the disadvantages of not recording?</h4><ul><li><strong>Limitation</strong> of data collection</li><li>Researcher <strong>might miss</strong> valuable <strong>information</strong></li><li><strong>No proof</strong> of content</li><li><strong>Only one perspective</strong> is known</li><li><strong>No</strong> accessible <strong>data</strong> for the future besides the interview lead’s notes</li><li>If there’s <strong>no observer</strong> during the session, the one who leads the interview can be <strong>distracted</strong> by <strong>note-taking</strong></li></ul><h3>Recording Contras</h3><ul><li><strong>May annoy</strong> the participant and influence what they say.</li><li><strong>Participants</strong> might feel that they’re being <strong>monitored, </strong>so they wouldn’t give <strong>real feedback</strong> or <strong>criticise</strong> the topic.</li><li>The <strong>researcher</strong> might also feel <strong>discomfort</strong> if they’re not used to recording their interviews.</li><li><strong>Extra work</strong> for documentation — Since you know you can rewatch the video anytime you want, you might not want to take notes so precisely.</li></ul><h4>What could be the benefits of not recording an interview?</h4><ul><li><strong>Participants</strong> might feel <strong>more comfortable</strong> and say things that they wouldn’t, if they were being recorded.</li><li>More open and real communication</li><li><strong>No need for documentation</strong> since notes will be taken during the interview</li></ul><h3>Conclusion</h3><p>Thinking of the variety of interview formats, <strong>recording</strong> should be default when it is a <strong>longer</strong> shot, such as <strong>semi-structured</strong> or <strong>deep interviews</strong> and the <strong>environment</strong> is <strong>suitable</strong>.</p><p>In case of <strong>short conversations</strong> and when the <strong>environment</strong> is <strong>not suitable</strong>, <strong>recording</strong> might <strong>not</strong> be <strong>necessary</strong>.</p><p>Furthermore, depending on your <strong>„researcher persona”</strong> you can individually decide what is more comfortable for you. If you prefer to <strong>concentrate</strong> on the <strong>participant 100%</strong> during the interview, then invite an <strong>observer</strong> to help you in taking notes and/or record the interview so that you can <strong>watch it</strong> in the future <strong>again</strong>.</p><p>Since we had <strong>different opinions</strong> about this topic even <strong>within a team,</strong> I’m sure there are many more perspectives out there. I’d love it if you could also <strong>share your thoughts</strong> about it <strong>in the comments </strong>to further discuss this exciting element of UX research.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1026087987dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/record-or-not-record-that-is-the-question-1026087987dd">Record or not record? That is the question</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[How customer support prepared me to become a UX Researcher]]></title>
            <link>https://medium.com/design-bootcamp/how-customer-support-prepared-me-to-become-a-ux-researcher-be7a7fa93661?source=rss-c390c9fdbd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/be7a7fa93661</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[mindset-shift]]></category>
            <category><![CDATA[customer-support]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Eva Muck]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 18:33:40 GMT</pubDate>
            <atom:updated>2021-01-18T18:33:40.976Z</atom:updated>
            <content:encoded><![CDATA[<p>I think it’s fascinating how diverse UX professionals’ backgrounds can be so I thought I’d share my story on <strong>how my experience in Customer Support </strong>(CS)<strong> helped me to become </strong>the <strong>UX Researcher </strong>I am today.</p><p>The journey starts back in the day when I was working as a <strong>Support Specialist</strong> at a <strong>tech-startup </strong>while finishing my MA at the uni. At first, I considered Customer Support only as an <strong>obligatory distraction </strong>from my studies but as soon as I collected more experience, I discovered how I <strong>improved </strong>and what kind of <strong>skillset Support gave me</strong>.</p><p>Of course, <strong>these skills were</strong> realised by me only after I started to gain experience in UX Research projects, until that they were <strong>invisible</strong>.</p><p>I call <strong>invisible skills</strong> those skills which become part of you during a <strong>learning process </strong>but they’re so new that they can’t be noticed or defined yet. One of the most exciting things in <strong>change</strong> is that sometimes the <strong>results can’t be seen immediately </strong>especially if we’re talking about <strong>self-improvement </strong>which is a <strong>long journey</strong> in every way, let’s be honest.</p><h3><strong>Skills I improved in Support and can utilise in UX Research too</strong></h3><figure><img alt="A person sitting in front of a laptop." src="https://cdn-images-1.medium.com/max/312/1*kKb_VOUCMDbwp-RxUDCmxg.png" /><figcaption>Me figuring out stuff</figcaption></figure><ul><li><strong>[EMPATHY] [CONNECTING WITH PEOPLE] [BUILDING TRUST]</strong> <br>Always <strong>narrate </strong>the customer <strong>what’s happening </strong>in the background so that they feel <strong>involved </strong>and you can build trust, e.g., if there’s a technical issue, explain it or if you need a break — home office can be unpredictable sometimes. This also means that you have to pay attention to <strong>your behaviour </strong>very carefully too.</li><li><strong>[ACTIVE LISTENING] [UNDERSTANDING ATTENTION] </strong><br>Make sure the client feels <strong>comfortable</strong> — ask questions, do small talk as a warm-up and provide a <strong>friendly atmosphere</strong> during the interaction.</li><li><strong>[STEADY CONCENTRATION &amp; CALMNESS UNDER PRESSURE]</strong> <br>Fast <strong>problem-solving</strong> in case of any <strong>technical issues</strong> — in Support you deal with problems which need to be <strong>fixed asap</strong> and after a solid experience you’ll not only have most workarounds in your mind but you’ll also have the <strong>answers</strong> for those occasions <strong>when the problem can’t be solved</strong> in a foreseeable time.</li><li><strong>[MENTAL STRENGTH]</strong> <br>As I stated above in Support you deal with problems which means you experience <strong>mostly</strong> the <strong>negative</strong> side of a product or a service. We could call it like being a <strong>human box bag</strong>. It strengthens you and with time it helps you to be able to <strong>work effectively during</strong> <strong>stress</strong>ful situations.</li><li><strong>[ATTENTION TO DETAIL]</strong> <br>Often solving a technical issue requires you to <strong>think through a whole process</strong> where every little detail plays an important role. In order to solve an issue in the most effective and quickest way, you need to <strong>move your brain</strong>.</li><li><strong>[PRIORITISATION] </strong><br>In Support we had a <strong>system</strong> where we prioritised the tickets that came from the users according to the <strong>size of</strong> their <strong>license </strong>and the <strong>category</strong> and the <strong>complexity</strong> of the issue. Basically, the logic was the following:<br>Can I solve it? <br>1. Yes -&gt; How quickly? -&gt; There’s enough time. -&gt; Do it! <br>2. Yes -&gt; How quickly? -&gt; There’s not enough time. -&gt; Escalate<br>3. No -&gt; Escalate<br>When I face a technical issue during a user test or interview this mindset is a <strong>great foundation</strong> and helps me a lot in <strong>time management</strong> too.</li></ul><h3>Support mindset vs. UX mindset</h3><p>In <strong>Support</strong> the <strong>focus </strong>was mostly on the <strong>negative side </strong>or the <strong>bugs</strong> of a product/service as the customers in general reached out to <strong>report a problem. </strong>This helps to <strong>better understand the pain-points </strong>of customers; however, it was <strong>hard </strong>for me <strong>to see the big picture </strong>and imagine a <strong>long-term solution </strong>instead of a workaround.</p><p>In <strong>UX</strong> you get to know a product/service in a wider sense. That is why one of my first challenges in <strong>UX Research </strong>was to <strong>concentrate on </strong>the <strong>positive and neutral aspects</strong> <strong>too </strong>next to the pain-points. This mindset gives me a bigger knowledge of the product and helps me to <strong>think of possible long-term solutions</strong>.</p><figure><img alt="A conglomeration of Support and UX mindsets." src="https://cdn-images-1.medium.com/max/550/1*reL1d9bYGY374QHENikybw.png" /><figcaption>Support — UX mindset conglomerations</figcaption></figure><p>Considering the <strong>connections</strong> between the two fields and that both<strong> CS</strong> and <strong>UX</strong>’s focuses are <strong>user-centric</strong>, I think it’s a <strong>must</strong> to contact your CS department during a UX process and <strong>get</strong> first-hand <strong>insights</strong> from them, especially when you’re in the <strong>exploratory phase</strong>.</p><p>Please, find a useful sketch on <a href="https://uxknowledgebase.com/feedback-review-e2f408d9aa6c">this link</a> by <a href="https://medium.com/u/e229ba532c48">Krisztina Szerovay</a> about how CS insights can help you in the beginning of a UX process.</p><h3>Conclusion</h3><p>There will always be <strong>room to improve </strong>the skills I listed above (&amp; many more), I’m definitely <strong>not done with learning </strong>and will never be.</p><p>With this article, I wanted to show you in what directions my Support background has led me and what kind of <strong>skill-overlaps </strong>are in <strong>CS</strong> and <strong>UX</strong>.</p><p>As different professions put the <strong>focus on different areas</strong>, we might improve different sides of ourselves that is why it can be exciting and useful to gain <strong>experience </strong>in <strong>multiple fields</strong>.</p><p>I used <a href="https://excalidraw.com/">excalidraw.com</a> for the illustrations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be7a7fa93661" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-customer-support-prepared-me-to-become-a-ux-researcher-be7a7fa93661">How customer support prepared me to become a UX Researcher</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[Meet you on the test…I mean see you!]]></title>
            <link>https://medium.com/design-bootcamp/meet-you-on-the-test-i-mean-see-you-4d3caca7db55?source=rss-c390c9fdbd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d3caca7db55</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[mobile-app-testing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Eva Muck]]></dc:creator>
            <pubDate>Wed, 06 Jan 2021 00:38:54 GMT</pubDate>
            <atom:updated>2021-01-06T00:38:54.686Z</atom:updated>
            <content:encoded><![CDATA[<h3>The lessons of switching from in-person to remote usability testing during the pandemics</h3><p>One of the things I like about being a UX Researcher is that most of the research methods can be carried out remotely too, as well as in person which makes my work more <strong>flexible</strong> and <strong>diverse</strong>. With thorough planning and preparation, it’s possible to <strong>switch smoothly</strong> from one to another — but what if you have to switch during an ongoing research process?</p><p>Imagine the situation that the first week you arrive to your new workplace pandemics hit in and you have to <strong>convert the ongoing research project</strong> to remote in only a few hours.</p><p>In this article, I share <strong>what</strong> <strong>I’ve learned</strong> from this situation and <strong>what I would suggest</strong> my fellow researchers who may experience similar circumstances to do.</p><h3>Original research plan vs. Covid-compatible plan</h3><p>Our team has prepared a research plan to validate the new design for a mobile app and to find the usability issues. The original plan was to conduct the research in person with <strong>two cameras</strong> — one for the user’s facial expressions (<strong>GoPro</strong>), one for their hands (<strong>HueHD</strong>). The plan was to run the prototype on an <strong>iPhone 11</strong> with the <strong>Figma Mirror app</strong>.</p><p>As part of the preparation, we wrote the <strong>interview script</strong> and <strong>printed out</strong> <strong>cards with the scenarios and tasks</strong> that we wanted the participant to complete during the test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*PigDgBCNbNNO4pablGpTgw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*eqEp8l3kzqZtrTjEyvhxjg.png" /><figcaption>In person usability testing for mobile app</figcaption></figure><p>After a few tests <strong>obligatory quarantine</strong> was announced, and we had to <strong>adapt</strong> to the situation <strong>quickly</strong>.</p><p>After considering the method of “<a href="https://medium.com/@beparticular/were-still-hugging-our-laptops-8c7f22ed800e"><strong>laptop-hug</strong></a><strong>”</strong>, we all agreed that it would carry <strong>too much risk and</strong> require too much <strong>effort</strong> from the participants <strong>to install the Figma Mirror app</strong> in order to use the prototype.</p><p>In addition, the <strong>prototype </strong>was <strong>optimised</strong> <strong>for iPhone X</strong> and it was not expected from the participants to have an iPhone X device.</p><p>So we decided to complete the test with the <strong>Figma prototype’s weblink on laptop/PC</strong>, and the rest of the usability tests were completed in the <strong>Zoom desktop app</strong> where the participants shared their screen.</p><p>We sent out the <strong>Figma prototype weblink</strong> to the participants who could open it on their <strong>laptop/PC</strong> in their web browser. This way the prototype was more like a <strong>paper-prototype</strong> than a real-life mobile app.</p><figure><img alt="A screen of a laptop where  the Figma prototype’s weblink is opened and the participant and researcher’s face on the right." src="https://cdn-images-1.medium.com/max/1024/1*3Qzwt30dw1jFU1cgTX0gvg.png" /><figcaption>Remote usability testing for mobile app</figcaption></figure><h3>What we’ve learnt from going remote</h3><p>Naturally, a <strong>remote usability test on laptop/PC</strong> is <strong>not suitable for simulating </strong>a mobile experience, but it has multiple advantages.</p><p>Despite of the paper-proto display, the remote usability test made it possible to observe multiple essential qualities such as <strong>findability</strong>, <strong>discoverability</strong>, <strong>information architecture</strong> and <strong>sequence inside the user flows</strong>.</p><p>In addition, the <strong>lack of personal contact</strong> can be <strong>annoying</strong> <strong>for the researcher</strong> because it would be ideal to observe the participant’s reactions from close for the sake of efficient data collection. In contrast, remote testing can be more <strong>convenient</strong> <strong>for the</strong> <strong>users</strong> as they are able to choose a <strong>known location for the test</strong> which can provide them a <strong>comfortable environment</strong>. Furthermore, an <strong>artificial environment can lead to distortions </strong>in the research results. This means that despite of losing the lifelike situation, another benefit is added.</p><p>Furthermore, in the “non-remote” setting, the <strong>distance</strong> between the user’s location and ours <strong>played</strong> an undoubtedly <strong>big role</strong> due to the travel time to our office and back. Few of the benefits of remote testing are that you take the<strong> </strong>user’s time<strong> solely for the duration of the test</strong>. Moreover, since you don’t have to be in the same room, you can organise it <strong>anywhere with</strong> a <strong>stable wi-fi</strong> connection and <strong>silent background</strong> which makes the recruitment easier.</p><h3>Conclusion</h3><p>Although the <strong>goal</strong> of an in person and a remote usability test is the <strong>same </strong>— to observe the users’ behaviour and understand their needs — we have to <strong>consider different technical aspects</strong> during the test.</p><p>During a remote test you have to pay attention on the <strong>sound and camera quality </strong>on your and on the user’s side. Sometimes you have to have great <strong>customer support skills</strong> to solve an issue or find a workaround. For example, a user’s mic on their laptop/PC was broken, so we had to talk on the phone with the speaker on while we were looking at each other and at the prototype on the laptop/PC’s screen. Another time we were testing with a participant who wasn’t really tech-savvy and it took about 15 minutes to explain how to share their screen. These situations need <strong>patience and calmness</strong>.</p><p>On the other hand, during an in person test you have to make sure the <strong>cameras</strong> are charged, switched on and set up in the optimal position, the <strong>meeting room</strong> is reserved, and it meets the <strong>tester</strong>’s needs to <strong>feel comfortable</strong>.</p><h3>Checklist</h3><p>I’ve collected a list with a few suggestions that could help you in your future remote sessions:</p><ul><li><strong>Always test</strong> the prototype and the tools that you’ll use during the test in case any change is needed.</li><li><strong>Prior</strong> the test, send out a <strong>short guide</strong> to the tester including the <strong>test’s length </strong>and the <strong>description</strong> of the product.</li><li>Make sure you have a <strong>backup plan</strong> in case of any technical issues or if the tester doesn’t show up.</li><li>As the moderator of the test <strong>arrive ~15 minutes before</strong> the appointment in order to set up the devices and get in the mood.</li><li>It’s also worth to give ~<strong>15 more minutes</strong> to the session in case any problem occurs or the conversation with the user drags on.</li><li>I’d recommend always <strong>using a web camera</strong> if you can in order to see each other with the participant.</li><li><strong>Open the interview</strong> <strong>script</strong> in a separate window <strong>on your screen</strong> so that you don’t have to look away. It will be more comfortable for you and it won’t annoy the participant.</li><li><strong>Invite observer(s)</strong> to the session. It will <strong>help</strong> you see <strong>other</strong>s’ <strong>perspectives </strong>and it’s a <strong>great way to evangelise</strong> <strong>research</strong> in your organisation.</li></ul><p>I’m happy to share with you a webinar about this topic that we held with <a href="https://medium.com/u/5ec1cc3fd3be">Edit Horvath</a> as the part of the Design Summit 2020 Warm-Up sessions. <br>Please note that the presentation is in Hungarian.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-p4e34I-clU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-p4e34I-clU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-p4e34I-clU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc4ec9a437ae08b92f8c1bcc1c38129f/href">https://medium.com/media/cc4ec9a437ae08b92f8c1bcc1c38129f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d3caca7db55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/meet-you-on-the-test-i-mean-see-you-4d3caca7db55">Meet you on the test…I mean see you!</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>
    </channel>
</rss>