<?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 Heidi Taperson-Lelumees on Medium]]></title>
        <description><![CDATA[Stories by Heidi Taperson-Lelumees on Medium]]></description>
        <link>https://medium.com/@heiditaperson?source=rss-40499227cfff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Cyd_ygiS7zEm5phBMz8koA.jpeg</url>
            <title>Stories by Heidi Taperson-Lelumees on Medium</title>
            <link>https://medium.com/@heiditaperson?source=rss-40499227cfff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:50:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@heiditaperson/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[10 Steps to Creating a Data-Driven Design Culture]]></title>
            <link>https://heiditaperson.medium.com/10-steps-to-creating-a-data-driven-design-culture-25e10b701664?source=rss-40499227cfff------2</link>
            <guid isPermaLink="false">https://medium.com/p/25e10b701664</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[data-driven-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Heidi Taperson-Lelumees]]></dc:creator>
            <pubDate>Tue, 07 Sep 2021 07:03:52 GMT</pubDate>
            <atom:updated>2021-09-07T07:03:52.591Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published in Qminder blog in August 2021: </em><a href="https://www.qminder.com/data-driven-design-thinking/"><em>https://www.qminder.com/data-driven-design-thinking/</em></a></p><p>At Qminder, we pride ourselves on having a data-driven, systematic approach to design. But it wasn’t always like this. Three months ago, we didn’t have data to visualize our product usage, we didn’t do user interviews or usability testing, nor did we have design objectives or research know-how.</p><p>Sounds familiar? Then this article is for you.</p><p>Today, we’re going to discuss how we started to build a data-driven design culture and what we have achieved within three months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*86glFBNGogi6ryOM" /><figcaption>Photo by <a href="https://unsplash.com/@melpoole?utm_source=medium&amp;utm_medium=referral">Mel Poole</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What is data-driven design?</h3><p>Data-driven design is an approach in which decisions are made based on both quantitative and qualitative data, leaving personal (gut) feelings or opinions aside.</p><p>For example, let’s say the team wants to build a mobile app, but interviews with the users tell us that 85% of the user base have to use desktop computers due to their company policies. Then it doesn’t make sense to go with a mobile app, instead focus on improving the existing desktop application. If we didn’t have that data, we might go with our personal opinions and start building mobile apps that will cost both time and money for the company (and end up with only a few people using the product).</p><h3>Why do we want to be data-driven?</h3><p><strong>In short: products designed with users in mind are more likely to succeed.</strong></p><p>Doing research at an early stage helps confirm the viability of products and saves a lot of time and cost for the company. It doesn’t matter how much a designer, software developer, or product manager loves the product. It only matters what users think. To design user-focused products, we need to understand our users and the problem we’re trying to solve.</p><p>Collecting both quantitative and qualitative data about user behavior helps to answer critical business questions, such as:</p><ul><li>Who are our users?</li><li>Why are they using our product?</li><li>What is the value of our product?</li></ul><h3>Data-driven design 101: where to start</h3><h4>1. Do a design audit</h4><p>Start by doing research. Good news: you’re on the right track since you’re already reading this article! But with all seriousness, audits help you understand where your company stands in terms of design maturity. We started by asking questions about the data:</p><ol><li>Do we know how many people visited this page during the past month?</li><li>Do we know how many people are using our product via desktop or mobile phone?</li><li>Do we know how many people signed up last week?</li></ol><p>In our case, most of the answers were <em>no</em>. So we collected everything we wanted to find out and needed to start tracking into one document.</p><p>Secondly, as a new member of the team, I tried to understand what resources we have, what are the main procedures, who is responsible for what, and who can help me with specific tasks. This included talking to different stakeholders and team members.</p><p>For instance, I found out that even though some tracking events were available, we did not visualize it nor had everyone from the company access to the data. That incentivized us to find a tool where to keep the data and share it with the whole team.</p><p>Moreover, talking to team members helped me learn about the product and understand our users better.</p><p>In short, you can start by analyzing the following:</p><ul><li><strong>Data:</strong> Start asking questions about your product’s usage. Collect everything you want to know (including existing and missing data) into one document, and use it as a backlog.</li><li><strong>People and resources: </strong>Talk with people to learn as much as you can about the product, users, and how work is being done.</li><li><strong>Procedures and tooling:</strong> Find out which design methods and tools are being used and how information is being shared.</li></ul><p>💡 Tip: When doing an audit, you can also try out Nielsen Norman Group UX Maturity Quiz. It helps estimate your organization’s <a href="https://forms.nngroup.com/s3/Maturity-Quiz">UX maturity level</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B3lo7XKz1VJTO7iF.png" /><figcaption><em>Stages of UX maturity, image courtesy of nngroup.com</em></figcaption></figure><h3>2. Data-driven culture starts at the top</h3><p>One of the mistakes I have seen in the past when trying to build a data-driven design culture is goals not being aligned between teams and upper management.</p><p>It’s important to set the expectations and agree with your managers about what, why, and how you plan to build. Top management can set an example and propagate the data-driven mindset downwards.</p><p>When I joined Qminder, I had several conversations with our CEO and CPO to agree on our goals.</p><p>Here’s how we enhance data-driven mindset on a day-to-day basis:</p><ul><li>CEO shares data insights during a company-wide all-hands meeting.</li><li>Team leads share monthly reports (based on data) during the all-hands meeting as well as in written form in chat.</li><li>We challenge each other (both leaders as well as individuals) during weekly product sync meetings by asking, “do we know how many users…”, “do we know why…”, and more.</li></ul><h3>3. Set specific goals</h3><p>After joining Qminder, I asked myself immediately: “Where do we want to be at the end of 2021?”</p><p>One of our company-wide objectives was to build a feedback loop between us and our clients, which meant establishing a data-driven design process. We split this into smaller, more specific goals:</p><ol><li>We measure the impact of what we create (for example, when we release a new feature, we have methods to measure whether the feature is performing well or not).</li><li>We make decisions based on the data we have collected (this means we won’t start working on a new project just because we like the idea; instead, the idea is backed with data).</li><li>We collect quantitative data where the results can be presented in numbers, i.e., “how many, how often or how much”, and qualitative data where the results take the form of observations, interviews, feedback, and feelings and answer to “why”.</li></ol><p>Again, agree on these goals with your manager or team lead or even with the CEO, depending on the size and structure of your company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8SpuyTBXy4KdM7SZgRnCg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@karlahrnndz?utm_source=medium&amp;utm_medium=referral">Karla Hernandez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>4. Start collecting quantitative data</h3><h4>Product analytics</h4><p>We need data to get a bird’s-eye view of what people are doing and understand how the product works. We had already created a backlog of questions that need answers. With the help of product and development teams, missing tracking events were added to the code. The next step was to find a data analytics tool that would allow everyone from the company to explore patterns in data, find answers, and share their findings.</p><p>There are many tools that can help you with that, depending on your needs and budget: Google Analytics, Mixpanel, Looker, etc. We chose Looker because that suited the best with our needs at the time, and it still does.</p><p>We started building dashboards one step at a time to see how users interact with our product. It’s often easy to get overwhelmed by all the possibilities, especially when starting out. For instance, we started one feature at a time (say, Data Insights) that we broke into smaller views (Team Performance and Visitor History). You don’t need everything at once. Go slow and prioritize.</p><p>We also created a separate Slack channel called #analytics, where people can ask questions, raise topics, and share updates. Communication is key.</p><h4>Surveys and questionnaires</h4><p>Surveys and questionnaires are easy to use and low-cost ways to produce a combination of quantitative and qualitative data.</p><p>At Qminder, we measure CSAT (customer satisfaction score) to understand how our users perceive the product — i.e., what they say and how they feel. The question that CSAT asks is simple: “How satisfied are you with Qminder?”, with an answer being a single number on a scale from 1 to 5. As a follow-up question, we ask them to tell us more about why they chose a certain score. From January this year, we have increased CSAT from 69 to 85, which is another indicator of users’ well-being.</p><p>In addition, we use on-page surveys to gather feedback on new or existing features. For example, we’ve been using Hotjar on-page surveys to ask users how they would rate their experience with a new feature on a scale from 1 to 5 and if there’s anything they were missing on the page. We use this data to measure features’ performance as well as to improve the product.</p><h4>Measuring visual design and aesthetics</h4><p>Visual design and aesthetics are often quite hard to measure and therefore categorized as subjective matters. One of the interesting ways to measure a design is by looking at how it makes users feel and what words they associate with it.</p><p>At the beginning of this year, we conducted an email survey where we asked our users to pick up to five words out of 26 that best describe how they feel about Qminder.</p><p><em>(</em><a href="https://www.nngroup.com/articles/desirability-reaction-words/"><em>There are 118 words in the full list of the product reaction words originally included in the Microsoft Desirability Toolkit.</em></a><em>)</em></p><p>Then, we explained the term “branding” and asked users to rate the branding of Qminder on a scale from 1 (I hate it) to 7 (I love it). This survey aimed to measure and understand how users feel about the brand, visual design, and aesthetics.</p><p>Our goal was to collect data before redesigning a product so we can repeat the survey after the major update(s) and compare the results.</p><h3>5. Start collecting qualitative data</h3><p>Once you have gathered insights on what people are doing, it’s time to deep dive into your users’ behavior, problems and needs.</p><p>I highly recommend combining quantitative data with qualitative methods, such as interviews, surveys, usability tests, observations, etc. Quantitative data gives us an understanding of what is happening, but we also need to figure out <em>why</em> it is happening.</p><p>Three months ago, working at Qminder as the only designer (and without a researcher), that’s where my biggest struggles started. One of my goals was to stop making guesses and instead make the improvements I knew our users needed. What helped me the most back then was this:</p><ul><li>Writing down the most important things I need to find answers for (that answered to why).</li><li>Getting the most out of <a href="https://www.hotjar.com/">Hotjar</a>. I started watching screen recordings that captured thorough user behavior, like mouse hovers, clicks, and scrolls. This helped me understand what users actually do. For instance, I discovered a new user flow; I found out that users couldn’t find a search option and spend over half a minute doing a manual search instead; and how often a specific user group used a feature that we didn’t know they even needed.</li><li>I started experimenting with on-page surveys. For example, I began asking users, “What’s the one thing we should change on this page?”, “What other information would you like to see on this page?”. In addition to getting feedback about the product, we discovered a few bugs while doing those surveys.</li></ul><p>Moreover, I ended up with even more questions which we did not know we should have been asking — <em>you don’t know what you don’t know</em>. These questions were valuable input for the next step — user interviews.</p><p>Finding participants, preparing, scheduling, and analyzing interviews most probably deserves another blog post, so stay tuned.</p><p><strong>In short, quantitative and qualitative data complement each other well.</strong></p><ul><li>Quantitative data sets a great foundation for understanding user behavior and helps identify UX trouble spots.</li><li>Qualitative data reveals users’ needs by creating a new narrative to the story.</li></ul><h3>6. Analyze the data</h3><p>So you have the data? Great. But we’re far from over.</p><p>Now you have to do something with this data.</p><p>Transforming raw data into valuable information, making it presentable, and finding a conclusion from that can often be challenging. Interpreting quantitative data (yes, <em>quantitative</em>, not qualitative) in a rational and objective way is one of the biggest obstacles I have encountered when analyzing the data.</p><p>Depending on your resources, you may not have a dedicated role for that in the team. If you don’t, no worries — we don’t, either. You’ll just have to figure it out by yourself. (It’s not that scary, I promise.) That’s where mixing and combining different methods comes in handy.</p><p>For example, when working on one of the core features at Qminder, we came across having too many ideas that we did not know how to prioritize. We also had loads of data collected from different sources such as user interviews, support tickets, surveys, screen recordings, product analytics, etc. After working on that data, organizing it, and making it presentable, we were able to use a modified <a href="https://www.productplan.com/glossary/ice-scoring-model/">ICE framework</a> to prioritize our list.</p><p>Analyzing data helped us understand both the impact of a specific feature as well as boosted our confidence level. It is not bulletproof but helps summarize research and gives a clear overview of what we should work on next.</p><h3>7. Hire a product researcher</h3><p>You cannot, and should not, do everything alone. I’m lucky to have a really supportive team that trusts me 🤗 Right after joining the company, I recommended hiring a product researcher. The team heard my reasoning on the value of user research, and we posted the job ad soon after.</p><p>Like hiring for any other new role, you should first clarify the responsibilities and expectations for the future team member.</p><p>Our goal was to find someone passionate about answering the most challenging questions in design by helping our team understand users’ behavior, problems, and needs. The primary responsibility for the role was to research multiple aspects of products and experiences through user interviews, usability tests, surveys, and observations.</p><p>Fast forward three months, and many candidates later, we found the person we feel can do all of that.</p><h3>8. Show your work</h3><p>Showing how design and research impacts business goals is important for learning and improvement, as well as sharing knowledge and increasing transparency in the company.</p><p>The definition of data-driven design is not always consistent across the organization. Therefore, it is vital as a designer or researcher to increase the visibility of design by sharing information and opening conversation.</p><p>There are many different ways to showcase your work and keep the team in the loop. Here’s a quick rundown of what we do at Qminder:</p><ol><li>Weekly syncs between product, development, design, and research.</li><li>Separate Slack channel called #design-showcase where design and research team share their work such as feature updates, visuals of UI, new design system components, research reports, upcoming plans, work in progress, etc. This channel is also an opportunity for people from other teams to ask questions and share their perspective.</li><li>Presentations at company-wide meetings. I think that’s one of the most important ones — you can include everyone and provide context by covering why, how, and what you’re working on.</li><li>Sharing know-how and articles about UX, research, and data-driven design. Once again, we have a specific channel for that — #read.</li></ol><h3>9. Review your goals</h3><p>Goal-setting is an ongoing process, and you need to constantly review your goals if you want to succeed.</p><p>I keep an eye on my goals weekly, if not daily. It doesn’t mean everything we do must support our objective (aka establish a data-driven design process). But, it’s an excellent place to ask why we are doing it if it doesn’t.</p><p>Besides keeping an eye on the goals myself, I try to involve the whole team to increase transparency and share what and why we’re working on. At most of our company-wide all-hands meetings, I start by reviewing the goals we set at the beginning of this year, what we have achieved, and then identifying opportunities for improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D_LKwKJ9xwGEr1Hr" /><figcaption>Photo by <a href="https://unsplash.com/@artic_studios?utm_source=medium&amp;utm_medium=referral">Daniel Öberg</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>10. Form a habit of data-driven mindset</h3><p>It’s a big commitment to adopt data-driven design practices. You might complete all the steps at once, but the key to success is to keep the momentum going. Being systematic and forming a habit of a data-driven mindset is what prevents the organization from falling back.</p><p>I have seen many companies start using new tools to either conduct user research or collect data on their products’ usage. But after a month or so, these tools end up collecting dust.</p><p>What makes a difference and helps minimize the risk of wasting effort and resources is to understand what the company wants to achieve, set goals and agree on these goals on a team and company level.</p><p>Make sure that the whole team is on the same page and you have each others’ back.</p><p>Don’t worry if something is not going as swimmingly as you hoped. At Qminder, we have a lot to improve and many challenges ahead, but we are also on the right track to becoming a fully user-centered company where data-driven design is a norm.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25e10b701664" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design & Research Collaboration at Veriff]]></title>
            <link>https://heiditaperson.medium.com/design-research-collaboration-at-veriff-d98b27ba7401?source=rss-40499227cfff------2</link>
            <guid isPermaLink="false">https://medium.com/p/d98b27ba7401</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[veriff]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Heidi Taperson-Lelumees]]></dc:creator>
            <pubDate>Sun, 02 May 2021 20:33:01 GMT</pubDate>
            <atom:updated>2021-05-02T20:33:01.980Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published in Veriff blog: </em><a href="https://www.veriff.com/our-people/design-research-collaboration-veriff"><em>https://www.veriff.com/our-people/design-research-collaboration-veriff</em></a></p><p>In the first two blog posts, we talked about the importance of understanding the problem in the design process and how the time between research and development should be split 50–50. We also talked about how we measure design and rely on quantitative data. To give you more food for thought — in this post, we will discuss how Design and Research collaborate at Veriff and how we use qualitative data to support our product development process. In order to do so, I had a chat with our User Researcher Marilyn Koitnurm who shed light on doing research and the importance of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmLkYBfDMRoXujjcm1m-WA.jpeg" /></figure><h3>What is user research and how is it conducted?</h3><p><em>Heidi:</em><strong> </strong>To start, can you tell us, what is user research and what does a user researcher do?</p><p><em>Marilyn:</em> In a nutshell, user research focuses on understanding users’ behaviour, problems and needs. The goal of user research is to replace in-house hypotheses and assumptions about what users think or do with actual facts and knowledge about user behaviour. Instead of blindly guessing what the users do and need, user research asks for people’s feedback, runs different tests and analyzes this information to guide meaningful product development.</p><p>User researchers use a variety of qualitative and quantitative research methods, but I personally rely heavily on qualitative methods, such as interviews, usability tests, surveys, observing user interaction with the product, etc. My role in the company is to make sure that the user is being thought of and that we keep the “user first” mindset.</p><p><em>H:</em><strong> </strong>What’s the value of user research? What problem does it solve?</p><p><em>M:</em> One of the secret formulas behind creating a successful product is knowing well who the people are who are using this particular product or service and catering to their needs. An important thing to keep in mind is that a software engineer or designer who creates the product is actually not the “average user”. And this is why we need to do research — to understand and bring in the user’s perspective. User research provides a direction about how to build a product and uncovers how well the design meets the user needs, based on feedback from real and potential users.</p><p>The value of user research is to uncover ideas that we couldn’t see from statistics or randomly assume from our desks — research goes “out there”, among people, in order to test ideas and collect data about “real” people. Researching users helps to answer important business questions, such as “who are our users” and “why do they need our product”. Also, doing proper research before the development phase saves a lot of time and costs for the company.</p><h3>UX design or UX research</h3><p><em>H:</em> User research focuses on understanding users’ behaviour, similarly to product or user experience design. I often get asked why couldn’t the designer do the research part, what’s the difference? Also, how can design and research successfully collaborate?</p><p><em>M: </em>The way I see it is that the researcher’s or UX researcher’s role has very organically grown out from the UX designer’s — it used to be typical that the designers did some research themselves. However, it became clear that actually splitting the roles into two — a designer and a researcher — allows deep specialization which is very valuable because then both of the professions can focus on their respective areas, and when these perspectives are brought together in one team, the value created is a lot bigger. A researcher has been trained to employ a variety of methods and thanks to this diversity of skills, a researcher brings analyses and insights that a designer might have not achieved on their own.</p><p>Having a dedicated research function takes the burden off from the designer’s shoulders, as the designer can fully dedicate to the design process, but at the same time be data-informed throughout the process thanks to being supported by relevant research.</p><p>Based on my own experience, I see that design and research can successfully collaborate when both acknowledge that they bring different perspectives to the table which complement each other. Also, it’s very important that the underlying motivation for both a designer and a researcher’s work is the same — keep the users in mind and create the best possible product and experience for them.</p><p>But Heidi, as we’re talking about this, I’d love to hear your thoughts — what kind of research helps you as a designer the most?</p><p><em>H: </em>Good question.<strong> </strong><a href="https://www.veriff.com/our-people/how-we-measure-the-impact-of-design">Metrics help us to demonstrate the impact of design in a tangible way, and connect the dots between design and business growth.</a> This idea was discussed in more depth in a previous blog post in the series. However, metrics such as conversion rates, page views etc do not always give us enough insights into the user’s experience — what’s their perspective, why people are using or not using certain products or features, why they drop-off. In short, quantitative data usually answers the <em>what</em> but not the <em>why</em> — we as designers need both to build user-friendly products. For me as a designer I often find interviews and observations of user interactions the most valuable when it comes to problem solving.</p><h3>How do qualitative and quantitative data complement each other?</h3><p><em>H:</em> There is always a drop-off in a company’s funnel (in most cases). In our case, we noticed that a number of people exit our verification flow by using the cancel button at the top of the screen. We knew <em>what</em> was happening but we didn’t know <em>why</em>. So we started asking why. When the user wanted to exit the flow, we asked a simple question: “Is there anything stopping you from finishing this verification process?”. It was optional, however, we received tons of feedback stating how their camera didn’t work, or their document wasn’t accepted, how they got confused, stuck, tired of the steps they had to pass to reach the flow in the first place. Understanding the why, creates a whole new narrative of what to keep in mind during day-to-day tasks.</p><p>To give another, perhaps more comprehensive, example — Design and Research collaborated on a project about NFC (near-field communication) in late 2020. NFC <a href="https://www.veriff.com/blog/what-is-nfc">allows different electronics to communicate by bringing them close to each other</a>. The very same technology allows us to make contactless payments with smartphones. Our goal with the NFC project was to offer a faster, safer, and more user-friendly way for users to scan ePassports and compatible IDs in order to verify themselves. However, a feature that was supposed to be more convenient, ended up with negative results in our funnel. The question was why, and we needed to figure it out.</p><p>We ran both moderated and unmoderated usability tests. The moderated usability test itself was very straightforward: the tester was asked to go through our flow, where they had to snap photos of themselves to verify their identity and also scan their NFC-compatible passport. While going through the flow, participants were encouraged to talk out loud and share their thoughts and feelings about the process. Based on the tests and collected data, we made a thorough analysis and put together a list of improvement ideas for the flow. For example, we realized that the usability tests brought out very important problems that we had to fix, such as unclear copy and design illustration improvements, but also a couple of critical technical bugs. Also, one of the things that the usability tests demonstrated was that users did not know what a “biometric passport” was nor what they could exactly use it for (in our case, for identity verification). This meant that in the second phase of the research, we ran unmoderated usability tests to understand what terminology do people tend to use when talking about ePassports.</p><p>In short, quantitative data gave us a great foundation for making certain business decisions, and qualitative data revealed users’ needs that helped to define problems and areas of improvement.</p><p>***</p><p>To sum up, the value of user research is to uncover ideas that we couldn’t see from statistics or randomly assume from our desks. User research focuses on understanding users’ behaviour, problems and needs. The outcome of the research can be applied in product design. Splitting the roles — a designer and a researcher — allows deep specialization where both of the professions can focus on their respective areas. However, it’s important to keep in mind that UX design and UX research aren’t two entirely separate disciplines — they are expected to have a common ground and understanding. When these perspectives are brought together, you’re able to achieve a deeper understanding of all aspects of your business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d98b27ba7401" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Design Can Improve Conversion]]></title>
            <link>https://heiditaperson.medium.com/how-design-can-improve-conversion-ddb72dec7651?source=rss-40499227cfff------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddb72dec7651</guid>
            <category><![CDATA[conversion]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Heidi Taperson-Lelumees]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 08:41:19 GMT</pubDate>
            <atom:updated>2021-03-15T08:41:44.712Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This was originally published in Veriff blog: </em><a href="https://www.veriff.com/resources/how-design-can-improve-conversion"><em>https://www.veriff.com/resources/how-design-can-improve-conversion</em></a></p><p>I believe that design is inherently optimistic and helps to tackle some of the most complex business problems.</p><p>At Veriff, our approach to design is systematic as well as data-driven. That means our design language is consistent, we use design systems and patterns, we measure the impact of our design (I’ll talk more about that in a later blog post) and we make decisions based on the data we have collected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cfuQxTEOO7U3Rnce" /><figcaption>Photo by <a href="https://unsplash.com/@willvanw?utm_source=medium&amp;utm_medium=referral">Will van Wingerden</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>A deepdive into data</h3><p>First and foremost — everything around design is about understanding the problem. Every project or task starts with a deeper look into the problem we are trying to solve. It involves collecting both quantitative and qualitative data, then synthesizing and analyzing the information. Once we have an understanding of the problem, we can move on to the next phase where we come up with potential solutions, pick out one (or two) and build it.</p><h3>The difference between desktop and mobile web conversion</h3><p>We used to encounter a problem where conversion rates in our desktop web were a lot lower compared to conversion rates in mobile web. So, less users were getting verified when they were going through verification in our desktop web flow. In some cases, the difference was up to 30%. It was clear that we needed to improve the user experience on the desktop, right? Because that’s what the numbers showed us. However, we decided to go further and get a clear picture of the problem, to understand the root cause — so we dug in.</p><p>What we discovered while collecting and analyzing the data, was that the quality of desktop cameras (your average computer webcam) was lower compared to mobile phone cameras. Therefore, photos taken of ID documents (ID cards, passports, driver’s licenses) on webcams were often blurry and hard to read, understandably affecting the conversion rates.</p><p>Without this seemingly small discovery, we could have kept fixing something that could not be fixed. Of course, there’s always room for improvement which is why we constantly experiment and strive to improve the overall experience on desktop as well as mobile.</p><h3>50/50 for research and development</h3><p>In my experience, it’s often easy to jump into a solution that hasn’t been defined first. Understanding user problems is the most important step in one’s design process. Ideally, the time between research and development should be split 50/50.</p><p>With the example above, we’ve now reached the development phase in our design process where we try to come up with solutions to the problem.</p><h3>Mobile fallback solution</h3><p>After brainstorming and mocking up ideas, we decided to try out something we now call Mobile Fallback. Based on the camera quality, we either let the user proceed on desktop or recommend them using their mobile device. In order to do so, we give the user a link they can send themselves via SMS, or a QR code which can be scanned to open the link on another device.</p><p>Results have been excellent — we’re offering a better experience without continuous hiccups caused by the poor quality of photos. By understanding the problem, we managed to increase the overall conversion rate by almost 5%.</p><p>Designers are often called problem solvers and that’s true. However, design is not only about solving problems — it’s about being passionate and curious, challenging every idea. But also, taking into account the company’s business goals and objectives in order to have a deeper understanding of the users, the product and the problems.</p><p>📝<em> Let me know what do you think and how much time you can (or want to) spend on research — before start coming up with solutions?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddb72dec7651" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Measure The Impact of Design at Veriff]]></title>
            <link>https://heiditaperson.medium.com/how-we-measure-the-impact-of-design-at-veriff-af1705709ccb?source=rss-40499227cfff------2</link>
            <guid isPermaLink="false">https://medium.com/p/af1705709ccb</guid>
            <category><![CDATA[ab-testing]]></category>
            <category><![CDATA[qualitative-data]]></category>
            <category><![CDATA[value-of-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Heidi Taperson-Lelumees]]></dc:creator>
            <pubDate>Tue, 09 Feb 2021 08:52:54 GMT</pubDate>
            <atom:updated>2021-02-09T08:52:54.634Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published in Veriff blog: </em><a href="https://www.veriff.com/resources/how-we-measure-the-impact-of-design"><em>https://www.veriff.com/resources/how-we-measure-the-impact-of-design</em></a></p><p>At Veriff, our approach to design is systematic as well as data-driven. That means our design language is consistent, we use design systems and patterns, we measure the impact of our design and we make decisions based on the data we have collected.</p><p><a href="https://www.invisionapp.com/talks/valueofdesign">Communicating the value of design is something that often proves challenging, in any organization.</a> It is difficult to connect the dots between design and business. This can lead to design being under-valued within the organization. Though the design field has matured a lot during the past decades, design is too often described as being subjective. When someone says design is subjective, it means design is based on personal feelings, tastes, or opinions. Objective design is rather based on research, both quantitative and qualitative data, leaving personal feelings or opinions aside.</p><p>In order to make the shift of bringing design from subjective to objective — we need metrics. Metrics help us to demonstrate the impact of design in a tangible way, prove the effort was worthwhile, find answers to design discussions, make decisions, learn from our mistakes and successes, and connect the dots between design and business growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7rBW0jAvPxyv_O_Q" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles Deluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>How do you measure design?</h3><p>Basically, you need to figure out your goals. The most commonly used metrics are retention, churn and conversion. At Veriff, we use <a href="https://medium.com/@joonatansamuel/effective-okrs-getting-them-right-the-first-time-around-1f520d93e653">OKRs to connect company, team, and personal goals to measurable results</a> while having all our team members and leaders work together in one, unified direction. That approach applies to design and designers as well. Before each quarter we set (design) team level OKRs that are connected with the company’s for the next 3 months.</p><h3>Step #1: Define your goals</h3><p>Let’s use the example of launching a new design update. How do we know if the update is successful or not?</p><p><a href="https://www.veriff.com/resources/how-design-can-improve-conversion">We do our research, collecting both quantitative and qualitative data, synthesizing and analyzing the information</a>. However, one can never be 100% sure until the feature or update is live and we can gather real-life data and feedback from the users.</p><p>The easiest way to know if your design update was successful or not is to make it measurable using quantitative metrics. Here are some examples:</p><ul><li>Number of people who visited your website</li><li>Number of people who signed up</li><li>Number of people who are using your product on a regular (daily/weekly) basis</li><li>Number of people who completed a certain task</li><li>Number of people who passed the funnel</li></ul><p>Once you know what your goals are, it is easier to both measure the impact and to actually decide in the first place, what you should focus on and prioritize based on that.</p><h3>Step #2: Set hypothesis</h3><p>In science, a hypothesis is an idea or explanation that you then test through study and experimentation. In design, a theory or assumption can also be called a hypothesis. At Veriff, we do our best to measure our design in order to understand the impact. Before every experiment, we set one or more hypotheses. For example:</p><ul><li>New illustrations help users to understand what they have to do better, therefore conversion rate will increase.</li><li>Showing real-time, onscreen feedback to the user, will increase the funnel conversion rate.</li><li>Consistent navigation experience helps users to find a specific page and increase the funnel conversion.</li><li>Onboarding will increase the number of weekly active users.</li></ul><h3>Step #3: Test</h3><p>We have talked about setting goals and hypotheses but you also need to test your designs in order to tell. At Veriff we AB test every single design update and feature before releasing it to the full user base. The idea of AB testing is to present different content to different user groups, measure it, gather data, and use the results to make conclusions and decisions.</p><p>I’ll give you some illustrated examples to demonstrate the idea better.</p><p>Our objective was to increase conversion rate. However, we had two hypotheses in the team: one, stating that users who see the photo frame have a higher conversion rate than those who do not, and another stating that it doesn’t matter.</p><p>We decided to test the idea in two groups:</p><ul><li>Group A (or the control group) didn’t see the frame when taking photos</li><li>Group B saw the frame when taking photos</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSA3ahAE6j2iqq5eBaMCsg.jpeg" /></figure><p>Statistically speaking, it is of utmost importance to have a considerable sample size for the results to be reliable. For that reason, we use the Bayesian equation to find out if the test results are statistically significant.</p><p><em>You can try out this simple </em><a href="https://marketing.dynamicyield.com/bayesian-calculator/"><em>Bayesian AB testing calculator</em></a><em> to find out if the results of your AB test are statistically significant.</em></p><p>Once the results came in, it appeared that group A had a conversion rate of 74,55% and group B had a conversion rate of 74,88%.</p><p><em>Was the test useful at all?</em></p><p>The test showed us that having a photo frame doesn’t have any statistically significant effect on our business KPIs i.e. conversion rate. That was something that needed to be proven. It is also something that could help you to finish ongoing design discussions inside the team and take design from being subjective to objective. The reason why I decided to demonstrate an example as such, is because that’s what happens in real life. Testing your designs doesn’t always have to mean having over 10% increase or decrease in your metrics. It’s about understanding what matters and what doesn’t.</p><p>Here’s another example of how AB testing has helped us to validate our research findings as well as measure the impact of our design.</p><p>Our research team was investigating problems in our funnels, which led us to develop the hypothesis that our users don’t understand they have to take photos of both sides of their document in the case of an ID card or driver’s license. Design proposed a solution that used an animation showing the user how to turn around the document, instead of visualizing it with a static image.</p><p>We decided to AB test the idea. The objective of this task was to understand if the animation on the document back instructions screen has a positive or negative impact on the conversion rate. Again, we tested it on two groups — group A who didn’t see the animation and group B who did.</p><p>As a result, conversion rate improved 2,7% with 99% probability of feature enabled being the best choice. It was a definitely successful experiment and we rolled it out to the whole user base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MP8vF5R_D6ARdOvOILla5A.jpeg" /></figure><h3>Conclusion</h3><p>The design field has developed and matured to the point where we have the knowledge, experience and tools in order to communicate the value of design outside the design team. Metrics give us powerful ways to explore, learn and elevate the role of design. It is important as a designer to understand your goals, test your ideas and show how design can lead the way in achieving business targets.</p><p>📝<em> Let me know what do you think and how do you measure the impact of design?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af1705709ccb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hey Designer!]]></title>
            <link>https://heiditaperson.medium.com/hey-designer-40674d582eac?source=rss-40499227cfff------2</link>
            <guid isPermaLink="false">https://medium.com/p/40674d582eac</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Heidi Taperson-Lelumees]]></dc:creator>
            <pubDate>Tue, 27 Sep 2016 07:41:07 GMT</pubDate>
            <atom:updated>2016-11-07T07:40:56.408Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Update: designer found!</em></p><p>I’m looking for a talented product designer to join our awesome <a href="https://www.instagram.com/togglteam/">Toggl Team</a>.</p><p>For the past few weeks we’ve been working on a big secret project. Because it’s a secret I can’t tell you what it is (yet), but we need help from a passionate designer to help us bring the project to life. We think it’s world-changing stuff.</p><p>You can’t create world-changing stuff by just moving pixels or swapping out background images. You’ll be working across desktop and mobile experiences, building eye-catching visuals and focusing on every little detail in the product functionality. That is why I’m looking for someone who can think outside the box and work with a team. I need a partner.</p><p>Don’t worry, our team is nice — and talented too. It’s great if you have experience with a prototyping tool, know basics of motion and typography— but being a team player is a must.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*QG5U7ioVOi6oX37wShlDyg.jpeg" /><figcaption>Toggl Team in Tallinn, Estonia</figcaption></figure><h4>What is Toggl?</h4><p><a href="https://toggl.com/">Toggl</a> is a time tracking tool. We think time tracking should be simple, even fun — if you can believe that. 1.6 million users seem to agree. We have a team of 49 very special people working on making the product better every single day. We’re based in Tallinn, Estonia, but most of our team works remotely from their homes — because we believe great work shouldn’t be hindered by borders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5_xFIsJgfr7YX4OrN9M3-w.jpeg" /><figcaption>This is us in Tel Aviv last year. We love to get together. It’s the human touch, we crave it.</figcaption></figure><h4>Design and experiences</h4><p>We’re driven by the why and we want to make things we’d actually use. Design makes us crazy. In a good way. Really. We love good design. Yet, we’re lack of one passionate girl or guy who can help us to grow bigger and better. Someone who wants to join our team and takes us to the next level. Someone who doesn’t see design as just a job — someone who cares about what they do. Previously we’ve been working together with great design studios from Estonia <a href="http://fraktal.co/">Fraktal</a> and <a href="http://haiku.ee/">Haiku</a>, and with <a href="https://3dro.ps/">3drops</a> from Sweden. We love them.</p><blockquote>We want to make things we’d actually use. Things like this:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4E7rCZ_GNv4Xh1CuRhoDg.png" /><figcaption>Toggl Webapp redesign by <a href="https://dribbble.com/shots/2717433-Toggl">3drops</a></figcaption></figure><blockquote>And this:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQwCdubKbYyBNxkHIFDT1A.png" /><figcaption>Toggl Webapp redesign by <a href="https://dribbble.com/shots/2721760-Toggl-Illustrations">3drops</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oy9PTZDEm6jC1YrgM7-LMA.png" /><figcaption>Toggl public web by <a href="http://fraktal.co/">Fraktal</a></figcaption></figure><p>I know we’re asking a lot — we’re looking for a designer who solves problems, asks questions and thinks big. But in return we can offer you an amazing team to work together with. Great product and awesome projects. And we travel a lot, go to conferences, meet clients, visit other team members. And when you come to visit us in Estonia where we get together once in a while, we have our brand new office ready for you! If you still hesitate, our people can tell you <a href="https://youtu.be/vU3QC0NNoDo">why they like working at Toggl</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Awt_Rn1GLHO5iLivxYjK8A.jpeg" /><figcaption>Toggl HQ in Tallinn by Kalle Veesaar</figcaption></figure><p>I know there’s people out there who don’t just want to follow orders. People who want to create their own path — and who own up to their choices whether good or bad. If you feel enthusiastic about working with us and know what it means to transform ideas into outstanding user-centric digital products, please send your portfolio to <a href="/service/mailto:heidi@toggl.com"><em>heidi@toggl.com</em></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40674d582eac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>