<?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 Fabrizio Ponzelletti on Medium]]></title>
        <description><![CDATA[Stories by Fabrizio Ponzelletti on Medium]]></description>
        <link>https://medium.com/@fab2L2T?source=rss-c11dce332254------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OAXsSxqszNd-8TsVRF-v0w.jpeg</url>
            <title>Stories by Fabrizio Ponzelletti on Medium</title>
            <link>https://medium.com/@fab2L2T?source=rss-c11dce332254------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:18:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fab2L2T/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[Case study: Design a faster, better, stronger booking tool]]></title>
            <link>https://medium.com/design-bootcamp/case-study-design-a-faster-better-stronger-booking-tool-61693a67aa5a?source=rss-c11dce332254------2</link>
            <guid isPermaLink="false">https://medium.com/p/61693a67aa5a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[pandemic]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Fabrizio Ponzelletti]]></dc:creator>
            <pubDate>Tue, 01 Dec 2020 07:09:27 GMT</pubDate>
            <atom:updated>2020-12-01T07:09:27.110Z</atom:updated>
            <content:encoded><![CDATA[<h4>Some tips to increase the conversion of an online booking tool, sharing the design process I took to identify pain points and actions.</h4><figure><img alt="Introductive image" src="https://cdn-images-1.medium.com/max/1024/0*uI-p3kKxb8K0wabo" /><figcaption>Photo by <a href="https://unsplash.com/@k8_iv?utm_source=medium&amp;utm_medium=referral">K8</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sight plays an important role in every aspect and phase of our life. We often take it for granted and don’t realize how much we depend on it until it passes away or simply gets worse as we age. According to the <a href="https://www.who.int/health-topics/blindness-and-vision-loss#tab=tab_1">World Health Organization report</a>, cases of myopia will double between now and 2030. Quite impressive uh? These estimates are based on many factors, including lifestyle changes, the increase in average age, and usage of digital devices. As the data suggests, here (but not only), periodic checks can prevent it from worsening. As consequence, these numbers are leading to a growing trend in eye exam requests (and recommendation!).</p><p>But let’s get to us. Working as a UX designer in a large company close to these topics, I was able to learn more about these user journeys.<br>First of all, how hard can it be to book an eye exam? Which are the pain points for the user? If you need a check, you can call and book, or go to the store directly. Often this decision came after the doctor’s advice or simply guided by the desire to get a new pair of glasses. Back in early 2019, I had many questions when I was asked to optimize an existing exam booking tool.</p><blockquote>Work it harder, make it better, Do it faster, makes us stronger. <br><em>This was pretty much a synthesis of the brief 🙊</em></blockquote><h3>More than ever</h3><p>Yes, “more than ever” this change seems to be necessary, quoting Daft Punk. It’s a booking flow, not a spaceship, sure, but we must remember that nowadays the user experience is not just “doing things right in our home”. The journey doesn’t start and end within the website or within marketing emails. Today, the competition isn’t just between medical exam booking flows, the challenge involves all the successful booking experiences we are surrounded (Deliveroo, Uber, Airbnb…).</p><blockquote><em>Let’s also consider that now, at the time I’m writing, we are in the middle of a world pandemic that for sure is making booking tools popping out everywhere.</em></blockquote><p>The question is no longer how it should be, but how users expect it to be. It’s Jacob’s law. In any case, as the overthinker I am, I was considering that it’s still a medical exam booking tool, it could play a different game. Given the complexity of this topic, there is probably a different focus and it may be necessary to find a balance between navigation simplicity and the amount of information to be displayed. And at this point, which pieces of information are essential to the user? How do they expect the interface to behave?</p><p>So, to answer all these questions, I started with an analysis of the current system, doing some heuristics. This was useful to familiarize with the tool and above all to create research questions for some user tests. Now, given a set of parameters retrieved from <a href="https://semanticstudios.com/user_experience_design/">Peter Morville’s user experience honeycomb</a>, I made some evaluations.</p><figure><img alt="Morville’s ux honeycomb used for a preliminary heuristic analysis of the state of art." src="https://cdn-images-1.medium.com/max/1024/1*FkuVKAVh0-kmkS33k1957w.png" /><figcaption>How it was in 2018</figcaption></figure><p>From here, the next step is to recruit the participants and start the interviews. In order to do this, there was a recruiting phase to find a group of participants that actually needed an eye check. To reach this, some screening questions were made to get the proper sample. To cover more scenarios, no age limits were set in the recruitment phase. This, to understand the differences in behavior between younger users and those older in age. Considering that the tool offers the possibility of booking multiple exams in the same session, (i.e a family booking scenario), among the pre-interview screening questions, they were asked if they had other people with this need in the family. All this was functional to fit the interviewed user as much as possible in a real and reproducible scenario. Another requirement for the screening was to establish how much time had passed since the last eye exam performed. The idea is that users aren’t too influenced by a process recently experienced. At the same time, it was also asked if the booking had been made online, by phone, or directly in the store. By integrating this last point, we also want to investigate familiarity with online booking tools, not necessarily related to clinical examinations.</p><p>The recruiting phase gathered a total of ten participants. For the purposes of the test, it was decided to divide them into two groups, one set up for desktop, the other for mobile. The first insights were already explanatory on the quality of the state of art. Based on what we saw so far and summarized in the table below, it is noted that especially on the desktop not all users were sure they correctly booked their appointment. Only two of them stated with certainty that they did it right, one failed the test due to a system error, and the rest didn’t feel confident of success (despite they land on the confirmation page). On mobile, on the other hand, only one user said she was unable to book.</p><figure><img alt="Table to show the success rate of the booking tool. How many user succeeded." src="https://cdn-images-1.medium.com/max/1024/1*ex6-poog7vvzPLbkMfGAiw.png" /></figure><p>For each interview, I checked the time needed to complete the tasks, taking into account only the users who managed to complete the flow and didn’t give up. there wasn’t a big difference, the results were pretty aligned between desktop and mobile in both task scenarios. What surprised me is that a task that should be simple (also considering just the first), took a lot of minutes and not everyone was sure of success, as seen above.</p><figure><img alt="Task duration timings on average" src="https://cdn-images-1.medium.com/max/1024/1*FkIMUxmSKhOGmhO926YSFQ.png" /><figcaption>Average timings of task completion</figcaption></figure><p>Analyzing how users felt during the test experience, below I summarized the satisfaction in each stage of the flow. This comparison aims to indicate in which points respectively between desktop and mobile, users have experienced the most uncomfortable situations.<br>The graphs are constructed by overlapping every user mood graph, for each stage of the flow the experience was judged on a scale.</p><figure><img alt="Mood graph to visualize where the user felt discouraged." src="https://cdn-images-1.medium.com/max/1024/1*ShxG7IxuEO9SinwOkl3XXg.png" /><figcaption>Mood graph comparison</figcaption></figure><p>As shown, on desktop it can be seen that the pain points are almost equally distributed between the form and the confirmation page. On mobile instead, the confirmation page is clearer and most of the issues were found in the previous steps. We need to keep in mind that there are many factors that may influence the mood of users, so this graph is not to be considered indicative of the usability problems encountered. To give a perception of that, I’m listing below the questions and doubts that emerged the most.</p><figure><img alt="Tag cloud of the most asked question during the testing phase." src="https://cdn-images-1.medium.com/max/1024/1*28nRXLLm5lWBtfvfajA1Tw.png" /><figcaption>The most frequent doubts and question expressed by users</figcaption></figure><h3>Work it, make it better</h3><figure><img alt="Animated image describing the pillars of the redesign." src="https://cdn-images-1.medium.com/max/1024/1*T_3zJqI9nxRZmOS5Ogf8qg.gif" /><figcaption>The new booking tool layout, 2020</figcaption></figure><p>… and finally, after collecting enough data, I was ready to design the new layout 🧐. The main change I did, as you can see above, was to abandon the one page form by creating a “step by step” structure. The reduction of the elements on the page improves the readability of the form and makes the information more accessible during the navigation. The goal is to create an experience as effortless as possible, thus becoming competitive again and in line with today’s user needs.</p><p><strong>👉 #1 Tip</strong><br>Simplify choices for the user by breaking down complex tasks into smaller steps (<a href="https://www.interaction-design.org/literature/article/hick-s-law-making-the-choice-easier-for-users">Hick’s law</a>). <strong>Let the user control the system, not the opposite.</strong> Show actions and information when it is necessary to make them visible, do not overload the user.</p><p><strong>👉🏼 #2 Tip</strong><br>As possible, try to <strong>anticipate the view of available appointment slots</strong>. Many users feel discouraged if they need to immediately provide contact or personal information even before having seen the availabilities.</p><p><strong>👉🏽#3 Tip</strong><br>Elder users tend to read everything on the screen. Having a summary that is always visible, as happens in checkouts, helps to keep track of the choices previously made and so to proceed with confidence. <strong>Let’s avoid users to go back and forth to check</strong> (or scroll the page continuously).</p><p><strong>👉🏾 #4 Tip<br></strong>It may sound trivial, <strong>but let people know they’re done!</strong> A clear confirmation message and possibly a description of the next steps increases the value of the service. To do this, a good practice is to send the confirmation email as soon as possible. We are now used to have things immediately thanks to Amazon and apps that automatically mark the appointment in your calendar without requiring “manual” actions from the user.</p><h3>Faster, Stronger</h3><p>Now, let’s talk about some success metrics. The new layout was brought to the validation phase, and the same tasks described above were proposed to a new group of users.<br>The new insights were positive and encouraging, in both tasks no criticalities or blocking elements were found during navigation. Starting from a general overview, it was immediately noticed that the new navigation is fluent and allows users to complete tasks quicker.<br>The average times calculated for the first and for the second task are much better than the previous one. The most surprising percentages can be seen in the second task, where users were <strong>71% (desktop)</strong> and <strong>65% (mobile)</strong> faster compared to the previous version. The new layout in steps allowed users to proceed faster despite the same number of information asked during the booking experience. <strong>Adjusting the error prevention system</strong>, in terms of positioning and copy clarity contributed to improving the service value.</p><p>Further confirmation is given by the new success rate. <strong>Now, none of the interviewed users doubted the appointment confirmation.</strong> The message has become more evident and users have not lost themselves in search of doctor or insurance information, as they have been placed within the flow, in order to prevent page exits.😎</p><h3>Work is never over</h3><p>It may seem an easy task to redesign a booking flow, whether it’s for an eye exam or just to order your own lunch. This experience has shown how useful and valid the Design thinking methodology is. Collecting data from user research allows us to understand the user’s mental model, identify flaws and prioritize changes. But this isn’t over. <br><strong>Design is by definition an iterative process</strong>, my experience with this project won’t end here. Users and needs are constantly changing. Just think about the growth of the mobile-first business. This is not a standalone project, this is intended to be as a flexible framework to share with similar businesses. And by expanding it in many realities we need to keep testing and testing, to keep track of performances. User research is the core of every successful design process.</p><p>This work is the product of great team cooperation, thanks to everyone that contributed and shared with me the best times (and the hardest😜).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fg9582DNuQppxC%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fhero0fwar-karmawhore-rhyming-g9582DNuQppxC&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fg9582DNuQppxC%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/75764283bda1d0d614d467272b5ad98c/href">https://medium.com/media/75764283bda1d0d614d467272b5ad98c/href</a></iframe><p><strong><em>Thanks for reading it!</em>❤️</strong><em> If you arrived here, I hope you found it interesting or useful! I would love to hear your thoughts and ideas, if you want to chat feel free to connect with me via </em><a href="https://www.linkedin.com/in/fabrizioponzelletti"><em>Linkedin</em></a><em>. Oh, and check </em><a href="https://www.youtube.com/watch?v=K2cYWfq--Nw"><em>this video</em></a><em> if you never saw it, it was my soundtrack while I wrote all of this.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61693a67aa5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-design-a-faster-better-stronger-booking-tool-61693a67aa5a">Case study: Design a faster, better, stronger booking tool</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>