<?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 Vinicius Leitao on Medium]]></title>
        <description><![CDATA[Stories by Vinicius Leitao on Medium]]></description>
        <link>https://medium.com/@viniciusleitao?source=rss-b8f5cbbb8306------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Hw76Yl7oqeKxFvkjEelv-w.jpeg</url>
            <title>Stories by Vinicius Leitao on Medium</title>
            <link>https://medium.com/@viniciusleitao?source=rss-b8f5cbbb8306------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:45:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@viniciusleitao/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[Designing for Delight in a Transactional World]]></title>
            <link>https://medium.com/design-bootcamp/designing-for-delight-in-a-transactional-world-d42e0a71e411?source=rss-b8f5cbbb8306------2</link>
            <guid isPermaLink="false">https://medium.com/p/d42e0a71e411</guid>
            <category><![CDATA[delight]]></category>
            <category><![CDATA[transactional]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Vinicius Leitao]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 23:03:48 GMT</pubDate>
            <atom:updated>2026-05-12T16:09:58.915Z</atom:updated>
            <content:encoded><![CDATA[<h3>Designing for delight in a transactional world</h3><h4>Or why sometimes the most impactful design work is the kind users never notice</h4><figure><img alt="A grid of iPhone mockups showing Preply’s lesson scheduling interface in pink tones, displaying screens for booking confirmations, weekly and single lesson setup, and calendar selection across different stages of the scheduling flow." src="https://cdn-images-1.medium.com/max/1024/1*ypLRktCYN9AiOaKqBN9zjA.jpeg" /></figure><p>I spent most of my time at Preply designing scheduling tools that learners and tutors use every day to manage their lessons, and it took me longer than I’d like to admit to really understand what that work was about.</p><p>Designing these tools may not initially sound like glamorous portfolio material, but the true value of this work lies in crafting complex, high-frequency interactions that are efficient, clear, and most importantly, trustworthy. And I’ve grown to love that, even if it’s the type of work nobody notices when done right.</p><p>What made it genuinely hard is that every design decision lived at the intersection of three competing forces: what’s best for learners, what’s best for tutors, and what’s best for the business. And they rarely push in the same direction. Helping a learner to secure their favorite spot might create a conflict for a tutor, and a feature that drives more short-term bookings might quietly erode the consistency that keeps learners coming back.</p><p>Learning to navigate that tension and choosing trust and long-term retention over short-term gains is what this work was really about.</p><figure><img alt="Desktop lesson scheduling interface for Preply, showing a weekly calendar grid with available time slots across Monday through Sunday; Wednesday at 15:00 is selected with a bold border, and 15:30 appears greyed out. A summary panel on the right displays the tutor details, the selected recurring time (Every Wednesday · 15:00–15:50), and a pink “Schedule weekly lesson” CTA. Two tabs at the top let users switch between Weekly and Single lesson modes.​​​​​​​​​​​​​​​​" src="https://cdn-images-1.medium.com/max/1024/1*uEjeaHEtpLcUCpmRjMW9ow.jpeg" /><figcaption>Weekly lesson scheduling</figcaption></figure><p>But something followed me through these years. I remember hearing this many times during checkpoints and design reviews: <em>“It’s solid, but it’s missing some sparkle.”</em> And they were right. My team was shipping features, hitting OKRs, and keeping things reliable. But the functionality itself was not quite enough. I always came back to one question: What does this <strong><em>sparkle</em></strong> mean when your canvas is a scheduling flow?</p><h3>Delight isn’t decoration</h3><p>Delight is a word that gets thrown around a lot in product design these days. It might sound like confetti animations, fun copy, or playful empty states. But there’s more to it.</p><p>Don Norman broke design down into three levels: <strong>Visceral</strong>, your immediate sensory reaction; <strong>Behavioral</strong>, how well something works; and <strong>Reflective</strong>, the meaning it carries for those using it. He noted that a delightful product experience only happens when a product addresses these three layers. Later, Aarron Walter built on top of that, distinguishing between <strong>Surface delight</strong>: the fun copy, the animations, the satisfying transitions; and <strong>Deep delight</strong>, when a product feels so carefully considered that users feel genuinely understood.</p><p>In transactional flows, such as scheduling a lesson, the three design levels appear in surprisingly tangible ways. The visceral layer is the interface that feels fast and uncluttered, the kind that makes you feel calm and trust what you’re looking at before you’ve even read it. The behavioral layer ensures that the flow actually works: time zones are handled correctly, conflicts are surfaced early, and confirmations feel certain. The reflective layer is a bit harder to pin down, but it’s still possible. It’s a learner who just booked a lesson, noticing the product remembered their preferred time and feeling that someone thought carefully about how they learn.</p><blockquote>Delight is not a layer you add on top. It’s the result of intention and craft applied consistently, including in the parts of the product no one notices.</blockquote><p>In practice, this level of delight comes from removing friction and anticipating needs. It means going just a little beyond what users expect. That might not be as eye-catching as a confetti animation, but it’s harder to achieve. It’s when your product behaves like a knowledgeable assistant, handing you the exact tools you need when you need them, without ever getting in your way.</p><h3>The invisible work</h3><p>The problem with working on these flows is that they disappear when they work well. You don’t tell your friends about how frictionless it was to book your lesson or how your calendar just worked. That’s part of the goal, but it also makes it easy to overlook the details that will build trust over time.</p><p>To make things more complicated, users have a negativity bias. A single frustrating moment can erase months of smooth ones. In high-frequency flows like scheduling, that asymmetry becomes even more apparent. The invisible good work doesn’t accumulate over time. But the moment something goes wrong, users doubt the product. And that sticks.</p><p>I spent a lot of time working on these details. Take the moment right after a learner books a slot: we nudge them to grab the same time in the following weeks before it’s gone. Simple, but it anticipates something the learner was already thinking about. It turns a routine step into something helpful and a little bit thoughtful. After launching it, we saw an increase in recurring bookings from learners who received the nudge, and learner feedback confirmed it helped their routines.</p><figure><img alt="Single lesson scheduling flow on mobile across four screens: time slots grouped by day with Weekly/Single tabs and a sticky tutor footer; a day view with 15:00 selected and 15:30 greyed out; a conversion nudge with “Great news! This time works for your tutor going forward.” and a recurring lesson card; and a pink confirmation screen with “Weekly lessons scheduled. Let’s keep making progress.“​​​​​​​​​​​​​​“" src="https://cdn-images-1.medium.com/max/1024/1*PV6ZRPaHqGYfbjr-OiB-Dw.jpeg" /><figcaption>Nudging learners to grab the same time in the following weeks</figcaption></figure><p>Another example: we tested adding small markers to the tutor calendar to highlight that a lesson was already paid for. Nothing too fancy. But if you rely on Preply as your main source of income, it turns anxiety into clarity.</p><p>We also changed what made a recurring slot available in the first place. The original logic would only suggest a weekly slot if it were conflict-free across many weeks. It felt safe, but in practice, it left many learners with limited availability. After talking with learners, we discovered something surprising: they were fine with a few conflicts early on if it meant securing their preferred spot in the long run. Relaxing this logic and helping them resolve these conflicts increased recurring bookings by over 20% and reduced the number of learners seeing zero availability by almost 80%.</p><p>These are the details that often go unnoticed when they’re done well. And that’s the point.</p><h3>The pattern holds</h3><p>Calendly’s calendar sync is one I come back to often. Connect your calendar, and your events show up directly in the scheduling flow, no cross-checking your schedule in another tab. It’s not flashy, but it removes the exact type of friction that makes people give up halfway through.</p><p>Google Calendar’s “propose a new time” is another. Instead of a simple decline, it shows both calendars side by side so you can quickly suggest an alternative without any back-and-forth. A small shift that makes the whole interaction feel faster and more human.</p><p>Or how Fresha prompts users who land on a booking page with no availability to jump straight to the next available date. One nudge, one less dead end.</p><p>None of these required huge redesigns. They’re quiet additions to existing flows, built on a genuine understanding of what users actually want to accomplish and what might get in their way.</p><h3>What I’m leaving with</h3><p>Working on scheduling all these years taught me that delight in transactional products is about consistently showing up in the moments that matter. The confetti animation? That might earn a tweet. But the nudge that saves a tutor from anxiety, or a learner from losing their favorite spot? Those get the trust.</p><p>That trust is slow to build and fast to lose. Shipping is just the visible part. The true craft lies in the hundred small decisions that led there, the ones nobody applauds because they didn’t even notice they needed them.</p><p>The best interactions in this context are transparent. They don’t draw attention. They simply remove the next obstacle before you even think about it. You know you’ve got it right when people stop noticing the design and focus on what they came to do.</p><h3><strong>Related reading</strong></h3><ul><li><a href="https://jnd.org/books/emotional-design-why-we-love-or-hate-everyday-things/">Emotional Design: Why We Love (or Hate) Everyday Things</a>, Don Norman</li><li><a href="https://web.archive.org/web/20170504230233/http://www.jnd.org/dn.mss/emotional_design_pe.html">Emotional Design: People and Things</a>, Don Norman</li><li><a href="https://abookapart.com/products/designing-for-emotion">Designing for Emotion</a>, Aarron Walter</li><li><a href="https://www.nngroup.com/articles/theory-user-delight/">A Theory of User Delight: Why Usability Is the Foundation for Delightful Experiences</a>, Therese Fessenden, Nielsen Norman Group</li><li><a href="https://www.lennysnewsletter.com/p/a-4-step-framework-for-building-delightful-products">A 4-step framework for building delightful products</a>, Nesrine Changuel, Lenny’s Newsletter</li><li><a href="https://www.nngroup.com/articles/negativity-bias-ux/">The Negativity Bias in User Experience</a>, Hoa Loranger, Nielsen Norman Group</li><li><a href="https://www.nngroup.com/articles/minimize-cognitive-load/">Minimize Cognitive Load to Maximize Usability</a>, Kathryn Whitenton, Nielsen Norman Group</li><li><a href="https://www.smashingmagazine.com/2016/09/reducing-cognitive-overload-for-a-better-user-experience/">Reducing Cognitive Overload For A Better User Experience</a>, Danny Halarewich, Smashing Magazine</li><li><a href="https://uxpsychology.substack.com/p/guiding-choices-in-ux-the-role-and">Guiding Choices in UX: The Role and Ethics of Nudging</a>, Dr. Maria Panagiotidi, UX Psychology</li></ul><p><em>This article was written by me based on my four-year period at Preply. I used AI (Grammarly and Claude) to proofread, suggest alt text for images, and help me refine a few sentences along the way.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d42e0a71e411" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-for-delight-in-a-transactional-world-d42e0a71e411">Designing for Delight in a Transactional World</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 FREE NOW uses design principles to build a better driver app]]></title>
            <link>https://medium.com/inside-freenow/how-free-now-is-using-design-principles-to-build-a-better-driver-app-857072b6c59?source=rss-b8f5cbbb8306------2</link>
            <guid isPermaLink="false">https://medium.com/p/857072b6c59</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[free-now]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Vinicius Leitao]]></dc:creator>
            <pubDate>Tue, 01 Feb 2022 18:00:22 GMT</pubDate>
            <atom:updated>2026-04-28T12:26:42.141Z</atom:updated>
            <content:encoded><![CDATA[<h4>Design Principles</h4><h4>A walk through ​the creation process, the principles, and how we are using them today</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0q4_CCiBZ6Uk1il49Ra8w.png" /></figure><p>Here at FREE NOW, we have a distributed team of designers working on various products, including our rider and driver apps, internal and external management tools, etc. These products have significant differences regarding where, why, and how users interact with them.</p><p>As a team, we split up the work on the different projects and topics, but we soon realised that we were focusing too much on our respective areas. We noticed that design decisions were inconsistent across product squads, mainly because they were taken based on the individual designer’s perspective.</p><p>Over time, mostly during our design critiques, the designers working on the Driver app found that it was getting increasingly challenging to design for drivers despite having a shared context of how to do it. ​​We needed proper guidance to improve the design process and the output across the squads.</p><h3>Considerations when designing for drivers</h3><p><strong>Fact:</strong> It’s dangerous to use a mobile phone while driving. Taking your eyes off the road and checking your phone for 5 seconds at 70 km/h is the same as driving 100 meters blindfolded. With this in mind, our design starting point has been to minimise drivers’ need to look at their phones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_iquingHSSEWXq2wLym7g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thibaultpenin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thibault Penin</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Making things a bit more complex, drivers usually have their phones mounted on the car dashboard, approximately 70 cm away from them. Compare that to a person holding a phone in their hand, where the usual distance between their face and phone is 15 cm.</p><p>As for their environment, most of the time, passengers are in the back seat, likely traffic around them, and bright sunlight or other vehicles&#39; headlights coming through their windshield.</p><p>Our driver app also has a dedicated area where drivers can track their earnings or plan their day. The design of these features, which they may access while not necessarily driving, should also be considered.</p><h3>Creating our design principles</h3><p>What guidance should we follow? Here’s how we created a set of design principles for our driver app.</p><h4><strong>Alignment</strong></h4><p>We decided to set up a task force to create a set of design principles that would help us design our driver app in the FREE NOW way. We asked ourselves a question: <strong>What should our design principles stand for?</strong></p><p>To get more context on what we were dealing with, we sent a survey to the designers in our team, asking when, where, and how they would use design principles. With this survey, we understood that these principles should be our guiding star, reflecting our design philosophy and articulating what is essential for us when designing.</p><p>We also agreed that the principles are not just for designers but for everyone influencing the design direction of our products. They should guide tradeoff-type decisions during product development and provide a framework for designers and stakeholders to make better decisions.</p><h4><strong>Ideation</strong></h4><p>The ideation phase started with a session where the driver design team analysed the survey results and defined the design principles’ main characteristics.</p><p>We also had a team workshop. First, we generated ideas individually, then grouped them into clusters, and eventually voted on what we considered the most relevant concepts based on our initial discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*64ElR7OC92yhN8R-o0gtGQ.png" /><figcaption>Screen capture with the results of the first workshop we did with the team</figcaption></figure><p>And after some work from the UX writers on our team, a draft version of the Driver Design Principles was ready to be tested in the real world.</p><h4>Feedback</h4><p>The next step was to test the principles in context, so we decided to run another workshop with the team. This time, we reviewed the current app and gave feedback using the principles we had recently defined.</p><p>This session helped us delve into each principle, highlighting some areas that needed clarification.</p><h4>Refinement</h4><p>Once the feedback round was wrapped up, we realised that we still needed to address some grey areas in the definitions. So we went back to the drawing board to discuss and better define each principle. Pretty much refine, align, test, and refine again.</p><h3>Our five driver design principles</h3><p>Now that you know how we crafted our principles let’s take a look at each of them and how they work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYGdTzq5fR3gMOMsWG71Jw.png" /></figure><h4>Contextual</h4><blockquote>We consider the scenarios in which our products are used — keeping in mind driving, non-driving, and managing use-cases and their implications.</blockquote><p>Our designs don’t exist in a vacuum. When exploring a new idea, we always consider the context it will be used. What type of driver, manager, or representative are we designing for? Where do they interact with our products? And, what might be distracting them or taking away their attention while they use any of our tools?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6HT_Uy-rZZgzPO5AvfORw.png" /></figure><h4>Safe</h4><blockquote>We encourage safe behaviour to minimise any potential risks while driving and using our app — avoiding distractions and helping drivers to keep their hands on the steering wheel.</blockquote><p>Our designs never distract drivers or demand their complete attention while driving. We prioritise navigation and passenger details over unrelated information, showing the relevant information where and when drivers expect to find it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lWWeqb2DiQKISOs4GWGlaw.png" /></figure><h4>Simple</h4><blockquote>We design in such a way that enables our users to quickly see and understand at a glance, allowing them to act confidently.</blockquote><p>Our designs do not overwhelm users. This is achieved by removing any superfluous information. We always display legible fonts, both in size and contrast. Buttons, icons, or action targets are easy to identify and act on, especially in driving use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zP-LVeV5kCDhuObQV5Vbqg.png" /></figure><h4>Reassuring</h4><blockquote>We empower our users to take control when using our tools, removing any doubts and helping them make conscious decisions about things that impact their daily working lives.</blockquote><p>Our designs help our users to understand any action they choose to perform and what to expect. They decide which action to take, not us: it’s the opposite of “do it, because we said so”. If we want them to change a behaviour or perform a specific action, we provide them with a clear benefit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rWImBxbteNfThKpK1YHrUw.png" /></figure><h4>Well-crafted</h4><blockquote>We craft delightful micro-interactions and pixel-perfect design solutions to positively impact our everyday users and their well-being.</blockquote><p>Our designs are carefully considered, functional, and visually appealing. We do this to delight users and enhance the overall experience, whether generating engagement, preventing mistakes, providing feedback, or communicating our brand.</p><h3>Design Principles, now what?</h3><p>OK, now we have a set of design principles. But if a tree falls in a forest and no one is around to hear it, does it make a sound? It was essential to spread awareness of the driver design principles to the rest of our colleagues.</p><p>First, we used the product syncs to share the principles and give visibility of how we use them in our design. Then we had a round of feedback workshops — following the same format we had with the design team — with each cross-functional squad in the Driver tribe to help PMs, developers, data analysts, or anyone else see them in the context of their teams.</p><p>The principles are also included in our team activities, allowing designers to provide feedback based on this shared perspective during our critiques, round tables, or any ideation session. We also updated our Figma template file to include the principles on the readme page so that every time designers start a new project, they can recall it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*id056raR6CJckItrGAEcUg.png" /><figcaption>Figma template file</figcaption></figure><p>Our design team has grown a lot since we introduced the principles last year. To get everyone on board, we included the principles in the newcomers’ onboarding and did a recap session with all the designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckTzrOHQ9NZBB50NveUaaw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3wdoeTx_vcbSGBXMAGBzUA.jpeg" /><figcaption>Design principles card deck and posters by Vinicius Amaro</figcaption></figure><p>And why not make it fun with some cool stuff to keep the principles fresh in our minds, like wallpapers, cards, posters, stickers, etc.</p><p>This story was only written because of the work of many people, including, but not limited to, Charlotte McCourt, Ferran Lajara, Bruno Ferrari, Marc Bayona, Miguel Coletta, Alicia Hector, and many others.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=857072b6c59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-freenow/how-free-now-is-using-design-principles-to-build-a-better-driver-app-857072b6c59">How FREE NOW uses design principles to build a better driver app</a> was originally published in <a href="https://medium.com/inside-freenow">FREENOW Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>