<?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 Ninad Kotasthane on Medium]]></title>
        <description><![CDATA[Stories by Ninad Kotasthane on Medium]]></description>
        <link>https://medium.com/@ninad.kotasthane?source=rss-cc9e5e54d0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gOCATOiRSlXeF0SOUys8NA.jpeg</url>
            <title>Stories by Ninad Kotasthane on Medium</title>
            <link>https://medium.com/@ninad.kotasthane?source=rss-cc9e5e54d0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:23:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ninad.kotasthane/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[When Data & Intuition Clash: Navigating the UX Alchemy]]></title>
            <link>https://medium.com/design-bootcamp/when-data-intuition-clash-navigating-the-ux-alchemy-3ed97b1bd897?source=rss-cc9e5e54d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ed97b1bd897</guid>
            <category><![CDATA[data-driven-decisions]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[decision-making]]></category>
            <dc:creator><![CDATA[Ninad Kotasthane]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 12:11:48 GMT</pubDate>
            <atom:updated>2026-01-06T12:17:45.496Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BKvZNYKJ9I_FghPK" /><figcaption>Photo by <a href="https://unsplash.com/@wikisinaloa?utm_source=medium&amp;utm_medium=referral">Wiki Sinaloa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>In digital design, the blend of data and intuition is a powerful alchemy. While research provides concrete insights, intuition allows us to anticipate needs that data hasn’t captured yet. But what happens when they point in opposite directions?</blockquote><blockquote>Recently, I faced this while introducing a new payment system for a successful B2B product in the US/UK. The users mental models were already “trained” to a specific flow. Changing it felt right intuitively for future-proofing, but the data showed users resisted the change.</blockquote><blockquote>Here is how to navigate the tension between the <strong>“what” (data) and the “why” (intuition) </strong>as per my understanding.</blockquote><figure><img alt="Different Payment Methods" src="https://cdn-images-1.medium.com/max/1024/1*_6-Mz8DOl7d7pqI0TrRc1w.png" /><figcaption>Different Pay Methods</figcaption></figure><h3>1. Intuition: The Designer’s Unseen Compass</h3><p>I recently experienced this difficulty in my latest project, where I wanted to introduce <strong>Apple Pay</strong> as a new payment method for a very successful B2B product in <strong>US/UK region. </strong>The data shows a good success in checkout experience, where the user selects the preferred pay method and continues to checkout. When wanted to introduce Apple Pay as a new pay option, it was <strong>mandated to follow Apple Pay Experience Guidelines,</strong> which were not as per current checkout experience. Due to this, we have to add <strong>additional steps</strong> in between including Apple Paysheet confirmation.</p><p>When I was discussing with Apple folks to make minor modifications as well as more suitable to our checkout experience (Most B2B has already approched) but since it was not in their roadmap, we had to follow their experience. It was equally important to keep the consistent experience across all pay methods to avoid new surprises. For this, have to come up with a new experience, which was hard to convince stakeholders since the data was giving different insights.</p><p>After creating pay method-based experiences, the success rate dropped by 4%, and the real activity of intuition starts from here.</p><p>Intuition isn’t “guessing” — it is pattern recognition based on our experience.</p><blockquote><strong>The Emotional Gap:</strong> Data tells you <em>what</em> users do; intuition suggests <strong><em>why</em></strong> they feel a certain way.</blockquote><h3>2. When the Data is Conflicting</h3><p>Now in my scenario, the data was not great as it drop off was 4%, we started <strong>looking for more qualitative data to do RCA</strong>. Qualitative data shows that after introducing Apple Pay, new users selected Apple Pay as the default method and completed the checkout process more <strong>quicker than the existing customers,</strong> even when there are more steps to complete. It was more of existing users who switched <strong>from the default pay method to Apple Pay.</strong></p><p>When we had interviews with the existing users, we realized that their <strong>mental model had already adopted the current checkout experience</strong> but since Apple Pay has a bit different, they took more time due to a lack of trust which led to drop off. But when we talked to the new users, they felt <strong>quicker compared to other pay methods</strong> even though it has more steps to complete. The insights was, since the journey was breakdown to multiple steps in Apple Pay checkout experience, users can <strong>focus on only a specific task</strong> at a time which was more easier for them as per <strong>Aesthetic and Minimalist Design.</strong></p><p>Data isn’t always a perfect truth. Algorithms can miss the nuance of human frustration. When your metrics are giving mixed signals, try these filters:</p><ul><li><strong>Prioritize High-Usage Scenarios:</strong> If a high-traffic feature has mixed reviews, fix it first. Don’t get distracted by conflicting data on features nobody uses.</li><li><strong>The “Human” Review:</strong> A tool might show high satisfaction because a task was completed quickly, but qualitative interviews might reveal the user was actually “rushing” out of frustration.</li></ul><p><strong><em>Key Takeaway:</em></strong><em> Other payment methods has less number of steps but still it has high drop off since user need to focus on many pieces of information at the same time where as in Apple Pay there were more steps to complete the flow with a higher success rate since it was easier for users to complete those steps quickly.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*qvqywKgrtlfrfNnIp-5fDw.avif" /><figcaption>Data vs Intuition</figcaption></figure><h3>3. Strategies for Balance</h3><p>To build a design culture where data and intuition coexist, follow these three rules:</p><ol><li><strong>Personas as a Bridge:</strong> Use data to build personas, then use intuition to “speak” for them. In my scenario, I had Old and New users as 2 catagories but for long term solution, I had to choose the quicker or simpler solution even if old users are not satisfied.</li><li><strong>Continuous Feedback Loops:</strong> Don’t wait for a redesign. Review analytics weekly to see if your “intuitive” tweaks are actually helping. Dont try to build all feature sets together, instead build miniature and take feedback whether users are interested in it or not. This will also help to set the right expectations to stakeholders.</li><li><strong>Validate, Don’t Just Guess:</strong> Use A/B testing to prove your “gut feel” works. This turns intuition into data.</li></ol><h3>Final Thought</h3><p>The best designs are <strong>data-validated</strong> but <strong>intuitively crafted</strong>. When the two clash, don’t view it as a roadblock — view it as a signal to dig deeper. Data gives you the foundation, but intuition gives you the “human touch” that makes a product delightful.</p><p>This will also help you. Watch the full video on <a href="https://youtu.be/mwOu0cDLlyk?si=XB4QtoAASqPZq3oR">YouTube.</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fl8imQNCxrt0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dl8imQNCxrt0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fl8imQNCxrt0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c250c5af997e891b0a2a22edb0656ead/href">https://medium.com/media/c250c5af997e891b0a2a22edb0656ead/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ed97b1bd897" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/when-data-intuition-clash-navigating-the-ux-alchemy-3ed97b1bd897">When Data &amp; Intuition Clash: Navigating the UX Alchemy</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[Modal vs Drawer — When to use the right component]]></title>
            <link>https://medium.com/@ninad.kotasthane/modal-vs-drawer-when-to-use-the-right-component-af0a76b952da?source=rss-cc9e5e54d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/af0a76b952da</guid>
            <category><![CDATA[ui-component]]></category>
            <category><![CDATA[user-behavior]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[design-decision]]></category>
            <category><![CDATA[critical-thinking]]></category>
            <dc:creator><![CDATA[Ninad Kotasthane]]></dc:creator>
            <pubDate>Tue, 01 Apr 2025 08:59:13 GMT</pubDate>
            <atom:updated>2025-04-01T09:00:02.486Z</atom:updated>
            <content:encoded><![CDATA[<h3>Modal vs Drawer — When to use the right component</h3><blockquote>In the world of web and mobile design, choosing the right UI component can make or break the user experience. Two of the most commonly used elements, modals and drawers, each serve distinct purposes and can significantly impact how users interact with your application. Understanding when to use each can elevate your design to the next level. Let’s dive into the nuances of modals and drawers to help you make the best choice for your next project.</blockquote><h3>How this comparison came to my mind</h3><p>Recently, I was wrestling with a classic UX question: side drawer or modal? It sounds simple, right? But when you’re deep in the weeds of a project, even the smallest decision can feel monumental.</p><p>I was working on a configurator, one of those tools where users deal with <em>tons</em> of data. Imagine a giant list of data filled with settings and many other options. My challenge was to make it super easy for users to add new entries. They just needed to fill out a form with multiple combinations, but here’s the kicker: they’d likely be adding <em>multiple</em> entries at a time, one after the other.</p><p>That’s when the side drawer vs. modal debate started raging in my head. I think you also might stuck in similar scenarios, so let’s check out which one is best to decide!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t96tUM4gSUpq6LRMXhsUow.jpeg" /><figcaption>Know the solution but is it good for correct behaviour</figcaption></figure><h3>Understanding modal and drawer basics</h3><p>To effectively leverage modals and drawers in your designs, it’s essential to understand their fundamental characteristics and how they influence user interaction. Modals are temporary and require user interaction to be dismissed. This makes them particularly useful for critical information that needs immediate attention. The temporary nature of modals ensures that users are aware of the importance of the content and are prompted to take a specific action.</p><p>On the other hand, drawers slide in from the edge of the screen, offering additional content or navigation options without fully disrupting the user’s flow. This seamless integration allows users to access supplementary information or navigate to different sections of the application while maintaining context.</p><p>When deciding between a modal and a drawer, it’s crucial to consider the context and user needs. By understanding these fundamental differences, you can make informed design decisions that align with the goals of your application and the needs of your users.</p><h3>Use cases for modals</h3><p>Shifting our focus to modals, these UI components are particularly powerful when you need to capture the user’s attention and ensure they focus on a specific task or piece of information. One of the most common use cases for modals is in confirmation dialogs. This not only prevents accidental changes but also reassures the user that they are making an informed decision.</p><p>Modals are also effective for displaying detailed information or additional content without navigating away from the current page. This is particularly useful in scenarios where the user needs to reference supplementary information while continuing to interact with the main content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JXPE6sE5ybNSwurnGp-Yw.jpeg" /><figcaption>Different types of modal based on context</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uMvRyNSBdhHvdScydUFJwA.jpeg" /><figcaption>Modal Do’s &amp; Don’t’s</figcaption></figure><p>When it comes to forms that require user input, modals can significantly enhance the user experience. By presenting a form in a modal, you ensure that the user completes the task before returning to the main interface. This is especially useful for tasks such as signing up for a newsletter or providing feedback BUT, a high chance that it won’t be the best choice to use for long forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pl-zyl1OVkoUsaRPMBx3oQ.jpeg" /><figcaption>Some Pros &amp; Cons of modal</figcaption></figure><h3>Best scenarios for drawers</h3><p>Moving on to explore the best scenarios for implementing drawers in your design. Drawers are particularly advantageous when you need to provide easy access to navigation menus without overwhelming the user interface. Unlike modals, which demand immediate attention, drawers slide in from the edge of the screen, offering a less intrusive way to present additional options. This makes them ideal for accessing additional related information without losing their place in the main content.</p><p>In mobile designs, where screen real estate is at a premium, drawers are especially valuable. They expand the available space, allowing for a more organized and clutter-free interface. By sliding in from the side, drawers can house a variety of secondary actions or information, such as settings, user profiles, or additional content, without dominating the user’s attention. This seamless integration is further enhanced by smooth, animated transitions, which make the drawer feel like a natural part of the interface, rather than an interruption.</p><p>Furthermore, drawers are perfect for secondary actions or information that should be readily available but not the primary focus. For instance, in a news app, a drawer can provide quick access to different categories or user settings, allowing users to customize their experience without disrupting their reading. In my project it was useful to create quick data entries to add on the main page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wJoAfANh9ck0Ey2XHta9Gg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*40MTJEO3SRCMGI7JoKpdWA.jpeg" /></figure><h3>Comparing user experience</h3><p>Building on the fundamental differences between modals and drawers, it’s crucial to delve into how each component impacts the user experience. Modals are designed to create a strong focus on the task at hand by temporarily blocking out the rest of the interface. This intense focus is particularly useful for critical actions or information that require immediate attention.</p><p>In contrast, drawers offer a more subtle and less disruptive way to access additional content or navigation options. By sliding in from the edge of the screen, drawers provide a seamless transition that does not fully interrupt the user’s flow. For instance, a user browsing a product catalog can open a drawer to filter by price and the product list remains visible, making the process more intuitive and user-friendly. This design choice helps maintain the user’s context and reduces the cognitive load associated with navigating back to their original task.</p><p>When deciding between modals and drawers, it’s essential to consider the user’s mental model and the context of use. By aligning the choice of UI component with the user’s expectations and goals, you can create a more intuitive and satisfying user experience.</p><p>Ultimately, the choice between modals and drawers should be guided by the specific needs of your application and the preferences of your users. By carefully considering these factors, you can design interfaces that not only meet the functional requirements but also enhance the overall user expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TaGTLYMbjFjoNpBK1T038Q.jpeg" /></figure><h3>Design tips for effective implementation</h3><p>As we delve into the practical aspects of implementing modals and drawers, it’s essential to focus on the user’s journey and ensure that these components enhance, rather than hinder, their experience. Both modals and drawers should present concise and focused information to maintain user attention and prevent information overload. For modals, this means keeping the message short and to the point, with a clear call to action. Similarly, drawers should offer streamlined options and content, ensuring that users can quickly find what they need without feeling overwhelmed.</p><p>Clear and intuitive triggers are also paramount for a seamless user experience. Users should easily understand how to open and close both modals and drawer.</p><p>Conducting usability tests can help you identify whether the triggers are intuitive or not. By carefully considering these design tips and based on use case, you can create modals and drawers that not only meet the functional needs of your application but also delight your users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NvyIPHI_9EmNkdc2SDR0RQ.png" /><figcaption>Make a wise choice between those</figcaption></figure><p><strong>Here are some extra helpful links for your reference:</strong><br>1. IxDF: <a href="https://youtu.be/8_s-pyqvOUI?si=_kdgyOSF2idfyAZ6">https://youtu.be/8_s-pyqvOUI?si=_kdgyOSF2idfyAZ6</a><br>2. User Pilot: <a href="https://userpilot.com/blog/ui-modal-examples/">https://userpilot.com/blog/ui-modal-examples/</a><br>3. uinkits: uinkits.com/blog-post/what-are-ui-ux-drawers-and-how-to-use-them-in-ui-ux-design</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af0a76b952da" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>