<?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 Damilola odulesi on Medium]]></title>
        <description><![CDATA[Stories by Damilola odulesi on Medium]]></description>
        <link>https://medium.com/@damilolaodulesi?source=rss-1807966079d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_91ItYonsAiTSI4q95ztYg.jpeg</url>
            <title>Stories by Damilola odulesi on Medium</title>
            <link>https://medium.com/@damilolaodulesi?source=rss-1807966079d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:08:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damilolaodulesi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to find the right UX metrics to measure product performance]]></title>
            <link>https://medium.com/design-bootcamp/finding-the-right-ux-metrics-a23da1d62db9?source=rss-1807966079d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a23da1d62db9</guid>
            <category><![CDATA[ux-metrics]]></category>
            <category><![CDATA[metrics-and-analytics]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Damilola odulesi]]></dc:creator>
            <pubDate>Sun, 29 Sep 2024 19:43:19 GMT</pubDate>
            <atom:updated>2024-10-02T08:43:43.457Z</atom:updated>
            <content:encoded><![CDATA[<p>When building digital products, it is always important to measure how well your product is performing in the market. In order to measure product performance, metrics are a useful tool that help indicate your current position and inform your future direction. However, with so many metrics to choose from, it can be difficult to know which ones are most important.</p><figure><img alt="A diagram showing the types of metrics used by most companies to measure product performance" src="https://cdn-images-1.medium.com/max/1024/1*95jhpilSzAYc_mawLccOaQ.png" /></figure><p>UX metrics are often not taken into consideration when measuring product performance. Many companies struggle to identify the right UX metrics to help assess customer satisfaction and the overall user experience of their product.</p><h4>What are UX metrics?</h4><p>They are <strong>user-centered </strong>datasets used to measure product performance.</p><p>Compared to other metrics, UX metrics focus on the details of how users interact with your product. They provide valuable insights into user behaviour, satisfaction, and the overall effectiveness of your design. By tracking these metrics, you can identify areas for improvement, measure the impact of design changes, and make data-driven decisions to enhance the user experience.</p><p>There are various types of UX metrics that help measure user behaviour, these four metrics are the most commonly used in the industry:</p><figure><img alt="Four commonly used UX metrics in measuring user experience" src="https://cdn-images-1.medium.com/max/1024/1*BBIR8s4G_ahlV1fT3Ijl5Q.png" /></figure><p><strong>1. Task success rate:</strong> This measures the percentage of users who successfully complete a specific task or goal within a product or feature.</p><p>For example; If 1000 users start the ordering process on a food delivery app, but only 800 users complete the order and receive their food, then the task success rate is <strong>80%. </strong>This is measured by:</p><p>(Number of Users Who Completed the Task / Total Number of Users) x 100</p><p>Note: A higher TSR indicates that the product or service is easy to use and meets the needs of its users.</p><p><strong>2. Error rate: </strong>Measures the frequency of errors or mistakes made by users while interacting with a product or feature.</p><p>For example; If 1000 user interacted with a signup form and 200 errors are reported, then the error rate is <strong>20%. </strong>This is measured by:</p><p>(Number of Errors / Total User Interactions) x 100</p><p>Note: A high error rate suggests that the product or service is difficult to use and may lead to user frustration or abandonment.</p><p><strong>3. Time on task: </strong>Measures the average amount of time it takes users to complete a specific task within a product or service.</p><p>For example: Measuring the time it takes 100 users to complete a checkout process on an e-commerce website.</p><p>Average Time on Task = Sum of Times for All Users (2 + 3 + 1 + … + 4) / Number of Users(100)</p><p>Note: A high average time on task metric can help you identify areas where users are experiencing delays or difficulties.</p><p><strong>4. Customer satisfaction score: </strong>Measures how satisfied customers are with the experience of a product or service.</p><p>For example, rating a driver on a scale of 1 to 5 after an Uber ride or a new Nike sneakers that has just been delivered to you. Feedback is usually gotten immediately after an interaction with a product or service to capture the most accurate feedback.</p><p>To calculate the CSAT score for your product or service:</p><p>CSAT Score = %Promoters + %Passives</p><p>Where:</p><p>Detractors: customers who rate your product 1 or 2 out of 5</p><p>Passives: customers who rate your product a 3 out of 5</p><p>Promoters: customers who rate your product 4 or 5.</p><p>Note: most of the metrics mentioned can be gotten automatically using analytics tools like Adobe or Google Analytics. If you don’t have access to such tools, you can collaborate with your backend engineers to obtain the necessary parameters for manual calculation.</p><h3>Benefits of UX metrics</h3><figure><img alt="Some benefits of applying UX metrics" src="https://cdn-images-1.medium.com/max/1024/1*QpvsbLB8UnaUcFfcvVxSLA@2x.jpeg" /></figure><ol><li><strong>Improved user experience: </strong>By leveraging UX metrics, you can gain valuable insights into how users interact with your product. This knowledge then allows you to identify and address pain points, and create a more accessible and satisfying experience.</li><li><strong>Increased engagement and retention: </strong>UX metrics provide essential data for understanding user behaviour and engagement. Tracking metrics like time spent on-site, task success rate, and bounce rates, helps identify areas where users may be losing interest and take steps to improve engagement. This, in turn, can lead to increased user retention, enhance customer lifetime value and drive revenue growth.</li><li><strong>Product development prioritisation:</strong> UX metrics play a crucial role in informing product development decisions. By analysing your user data, you can identify which features are most valuable and prioritise their development accordingly. By using data, resources are allocated effectively and helps to avoid wasting time and money on features that may not be as impactful.</li></ol><h3>How do I find the right UX metrics?</h3><p>To find the right UX metrics, it’s essential to first define your product’s goals. Consider the specific outcomes you aim to achieve, such as increasing user satisfaction, improving engagement, or optimising conversion rates. Once you have a clear understanding of your objectives, you can select metrics that directly align with them. Remember that context is crucial, as there are numerous metrics available, and the most relevant ones will depend on your unique product and target audience.</p><p>Leveraging established frameworks can also be beneficial in defining the context and providing guiding principles for choosing appropriate UX metrics. A very common framework is HEART, developed by Google.</p><p><strong>The HEART framework</strong></p><figure><img alt="The HEART framework developed by google" src="https://cdn-images-1.medium.com/max/1024/1*gA5jFmKc-1vxj2YM3bfWKQ@2x.jpeg" /><figcaption>The Heart framework</figcaption></figure><ul><li><strong>Happiness:</strong> Measures user satisfaction and positive sentiment through surveys and feedback. Some common metrics to employ if your goal is to measure happiness include Customer Satisfaction Scores (CSAT), and Net Promoter Score (NPS).</li><li><strong>Engagement:</strong> Tracks user involvement and interaction frequency with your product. If this is your goal, some common metrics to help measure user engagements are click through rate, Time on Site, and Pages per Session.</li><li><strong>Adoption:</strong> Evaluates the rate at which new users discover, try, and start using your product. Some common metrics to measure adoption are new user sign-ups, conversion rate, trial-to-paid conversion rate</li><li><strong>Retention:</strong> Measures the ability to keep existing users engaged and loyal over time. Some metrics used to measure user retention include user retention rate, churn rate, customer lifetime value (CLTV).</li><li><strong>Task Success:</strong> Assesses how effectively users accomplish their goals within your product, using metrics like completion rates and error rates.</li></ul><p>The HEART framework is a helpful guideline, but it’s not one size fits all. Feel free to explore other frameworks, such as the QX score, to find the right UX metric for your specific context. While you can use various metrics to align with your product goals, many UX metrics are quantitative. To gain a deeper understanding, consider conducting additional research to gather qualitative insights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a23da1d62db9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/finding-the-right-ux-metrics-a23da1d62db9">How to find the right UX metrics to measure product performance</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[Improving the loan application and savings process for cooperatives in Nigeria- a UX case study.]]></title>
            <link>https://medium.com/@damilolaodulesi/improving-the-loan-application-and-savings-process-for-cooperatives-in-nigeria-a-ux-case-study-70e60508b8d7?source=rss-1807966079d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/70e60508b8d7</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Damilola odulesi]]></dc:creator>
            <pubDate>Thu, 04 Nov 2021 08:58:13 GMT</pubDate>
            <atom:updated>2024-10-02T07:05:44.910Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EqUYrkUi_hesw_hbpK-Uyw.jpeg" /></figure><h3><strong>Background</strong></h3><p>Wema bank is one of the top banks in Nigeria for providing financial services to millions of users. over the years it has offered a platform for members of cooperatives to save and access loans. Although a manual process has been used by the bank, it was time to adopt a more digital approach to increase efficiency and create an easily accessible data storage centre.</p><h4><strong>Goals</strong></h4><p>The primary goals were to:</p><ol><li>Digitise the savings process to improve members saving habit by eliminating long queues in banks.</li><li>Improve the loan application process to increase the number of completed requests.</li></ol><p>Some of the business goals were to:</p><ol><li>Increase the conversion rate of cooperatives and their members.</li><li>Increase the amount of loan applications as well as savings made by cooperatives.</li></ol><h4><strong>My role and responsibilities</strong></h4><p>I led the design of the product from start to finish. I was responsible for the product strategy, conducting user research, Wireframes, prototyping, product design, and Usability Test. Although I was the sole designer on the project, I collaborated closely with a product manager and three engineers.</p><h3><strong>User research</strong></h3><h4>Interviews</h4><p>To get started, i had an online interview with 35 customers of the bank who were cooperative members. The goal at this stage was to understand the challenges they had and try to get a picture of what the process was like whenever they tried to access loans or save money and how to better approach this within the digital platform.</p><p>Key takeaways where.</p><p>1. users needed a way to easily access information about how much savings they have made, and easily top up their savings.</p><p>2. Users had no way of knowing the loan amounts they were eligible for which resulted in a lot of declined loan requests.</p><p>3. Users needed to be able to easily access information about how many unpaid loans they had pending and be able to easily pay off these loans every month.</p><h4><strong>Ideation</strong></h4><p>At this stage, I did a bit of brainstorming and came up with a few ideas aimed at resolving the issues that were uncovered during my interaction with the users at the interview stage. The top three ideas were:</p><p>1. Provide users with details of how much they have saved and also allow them top up their savings online.</p><p>2. Provide clarity around the loan amount, repayment amount, interest rate, and loan duration, thereby making it easier for users to make an informed decision about their loan.</p><p>3. Provide clarity around how many loans they had pending, how much interest each loan has accumulated, and a detailed process on how to easily pay off loans.</p><h4><strong>User Flows</strong></h4><p>There are three main flows been covered, they include savings top-up, loan request, and loan liquidation.</p><p><strong>Savings top-up: </strong>After ideating around a few steps enable users to easily top up their savings, I came up with these simple steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-vETaNUm5cpy4nho9SeYg.jpeg" /><figcaption>User flow for savings top-up</figcaption></figure><p><strong>Loan request: </strong>Users needed to be able to see how much loan they were entitled to and select how much loan they wanted and for how long.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aKZEgxkhimLweGAkMsiSWQ.jpeg" /><figcaption>User flow for making a loan request.</figcaption></figure><p><strong>Loan Liquidation: </strong>This flow enables users now much debt they owed and easily pay them off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJpm05bcXyHLkX0AKJgAIQ.jpeg" /><figcaption>User flow for liquidating a loan</figcaption></figure><h4>Sketching</h4><p>After drawing up the user flows, i went ahead to create a few sketches to help me have a better view of how items and buttons should be positioned as well as text hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnvJZDrbl8w7mg7kY7JZnw.jpeg" /></figure><h3><strong>Design and Implementation</strong></h3><h4>Wireframes</h4><p>At this stage, I tried to still limit my focus to the flow and functionality of the app while also including some interface details to give more clarity to the purpose of each screen. This allowed me to rapidly test and improve my ideas before moving on to designing the interface properly.</p><p><strong>Savings top-up</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u4SYaGA7nhofZdcb4ONBMQ.png" /><figcaption><strong>Wireframes for the savings Top-up flow.</strong></figcaption></figure><p><strong>Loan request</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VMCfI225YSfgJOOCoHeFw.png" /><figcaption><strong>Wireframes for the loan request</strong></figcaption></figure><p><strong>Loan Liquidation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9jJPNpDhpFFJEuYsNeufw.png" /><figcaption><strong>Wireframes for loan liquidation</strong></figcaption></figure><h4>User Testing, Feedback &amp; Iteration</h4><p>I tested the wireframes with a different set of users and about 85% of users were able to easily understand and navigate from end to end. A few notes were taken from the usability test session, some which were key to improving the experience. Here are some of the key updates I made to the design based on the feedback and observations I made while testing the wireframes (The updates are reflected in the high-fidelity screens).</p><ul><li><strong>Include the option to use a different bank account to receive the loan.</strong></li></ul><p>At the point of submitting the request, I created an option for the user to receive the loan using a different account. Upon adding the new bank account, they would also have the option to save it to their profile for later use.</p><ul><li><strong>Allow users generate E-statements for all their savings.</strong></li></ul><p>While users can view all their savings transactions, they wanted to be able to generate an E-statement for easy reference. I created an option to enable users to input the date range for their statement, upon submitting their request, an email would be sent to them with their E-statement.</p><ul><li><strong>Include the guarantor tab to enable users to view all guarantor requests (Surety)</strong></li></ul><p>While requesting for loans, you would be required to select a guarantor within the organisation, Users needed to be able to manage their guarantor request such that they can either accept or decline a guarantor request.</p><h4>Savings top-up</h4><p>Here’s what the final flow for savings top-up looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hYY2O6J5uPD_tdcVCRV8w.jpeg" /></figure><h4>Loan Request</h4><p>Here’s what the final flow for requesting a loan looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UwVBAeXefzfwL8o5nr13Zw.jpeg" /><figcaption>Select a amount and duration to set interest rates.</figcaption></figure><p>Using a different bank to receive funds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*liBu6SkFCIssJUCkuQkt8A.jpeg" /></figure><h4>Loan Liquidation</h4><p>Here’s what the final flow for loan liquidation looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tER_xL-sd9hSiDPpU3OjCg.jpeg" /></figure><h4>Takeaways</h4><p>It was a really interesting project and I’m pleased with how much we were able to get done in a small amount of time. To summarise, a key part of designing products is interacting with users early and often. Relying on our assumptions of the problems (and possible solutions) is never enough. It’s also interesting to see how three small changes to the process could have such a huge impact on product usage as a whole.</p><p><strong>Key Wins In A Nutshell</strong></p><ul><li>Eliminated manual loan approval and disbursement.</li><li>Increased efficiency of the internal team.</li><li>Eliminated loan request failures.</li><li>Increased disbursement rate by 25%.</li><li>Improved the savings process</li></ul><p><strong>Next Steps</strong></p><p>For the next version of the app, we’ll be looking at areas of friction around the registration and onboarding process. The thinking here is, the more people get onboarded, the more loan requests would be made on the platform. I’ll be sure to share more about this endeavour in the near future.</p><p><strong><em>Thanks a lot for reading all the way to the end. Please leave a comment and 👏🏻 if you enjoyed reading. You can follow me on Twitter; @Damo_Scorpion , if you’d like to chat about design or business. Also, leave a comment if you think there’s something I missed out or if you have any thoughts at all. Cheers.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70e60508b8d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>