<?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 Namratha Patel on Medium]]></title>
        <description><![CDATA[Stories by Namratha Patel on Medium]]></description>
        <link>https://medium.com/@namratapatel_69309?source=rss-39b0253578f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4MFUIilpyAuoXL6phnX1XQ@2x.jpeg</url>
            <title>Stories by Namratha Patel on Medium</title>
            <link>https://medium.com/@namratapatel_69309?source=rss-39b0253578f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:29:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@namratapatel_69309/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[Voice Assistant for a food ordering system — QSR’s]]></title>
            <link>https://medium.com/@namratapatel_69309/voice-assistant-for-a-food-orderig-system-qsrs-93d5d9de027b?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/93d5d9de027b</guid>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[voice-ai]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Mon, 11 May 2026 09:12:41 GMT</pubDate>
            <atom:updated>2026-10-14T01:28:16.226Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRtyGUohUxguA_d-esQLkA.png" /></figure><h3>Designing a Voice Assistant for Order Support</h3><p>Voice interfaces are no longer futuristic concepts. They are becoming an essential part of customer support, especially in industries where users expect instant assistance and seamless communication.</p><p>In this project, I explored how a Voice UX solution could improve the order support experience by reducing customer frustration, streamlining conversations, and helping users resolve issues faster.</p><p>This case study walks through the process behind designing <strong>Order Assist</strong> — a conversational voice experience focused on handling order-related queries.</p><h3>The Problem</h3><p>Customer support experiences often become frustrating during high-demand situations. Users are left confused when:</p><ul><li>Orders are delayed</li><li>Delivery timelines change unexpectedly</li><li>Support systems provide generic responses</li><li>Users are forced to navigate multiple steps to get answers</li><li>Existing chat or IVR systems fail to understand intent properly</li></ul><p>Traditional support systems frequently create friction instead of solving problems.</p><p>The goal of this project was to design a conversational experience that could:</p><ul><li>Understand user intent naturally</li><li>Reduce support effort</li><li>Provide contextual responses</li><li>Handle edge cases effectively</li><li>Improve overall trust and satisfaction</li></ul><h3>Research Phase</h3><p>To understand the gaps in existing support systems, I conducted research around customer conversations, support pain points, and conversational behavior.</p><h3>Order Conversation Analysis</h3><p>I analyzed different types of order-related customer conversations and mapped recurring patterns.</p><p>Some common scenarios included:</p><ul><li>Users checking order status repeatedly</li><li>Customers asking about delays</li><li>Requests for cancellation or refunds</li><li>Users wanting faster delivery updates</li><li>Customers struggling to reach human support</li></ul><p>The analysis helped identify where conversational breakdowns usually happen.</p><h3>Key Observations</h3><p>A few strong insights emerged from the research:</p><ol><li>Users want quick reassurance more than lengthy explanations.</li><li>Most conversations revolve around a limited set of recurring intents.</li><li>Delayed responses increase frustration rapidly.</li><li>Users prefer conversational and empathetic responses over robotic flows.</li><li>Customers expect contextual continuity during conversations.</li><li>Escalation to human agents should feel seamless.</li></ol><p>These insights became the foundation for the Voice UX strategy.</p><h3>User Stories</h3><p>Based on the research, I created user stories to define the ideal conversational outcomes.</p><p>Examples included:</p><ul><li>As a user, I want to know where my order is without navigating multiple menus.</li><li>As a user, I want updates about delays in simple language.</li><li>As a user, I want the assistant to understand my issue naturally.</li><li>As a user, I want to cancel or modify my order quickly.</li><li>As a user, I want to speak to a human agent when necessary.</li></ul><p>These stories helped align the product experience around real user needs.</p><h3>Stakeholder Interviews</h3><p>I also collaborated with stakeholders to understand operational constraints and business priorities.</p><p>The discussions focused on:</p><ul><li>Customer support efficiency</li><li>Reducing repetitive support tickets</li><li>Improving first-response resolution</li><li>Handling peak-hour support load</li><li>Creating scalable conversational systems</li></ul><p>This helped balance both user experience goals and business expectations.</p><h3>Competitor Analysis</h3><p>To benchmark the experience, I analyzed existing conversational support</p><p>The comparison focused on:</p><ul><li>Conversational tone</li><li>Error handling</li><li>Escalation flows</li><li>Personalization</li><li>Context awareness</li><li>Recovery from failed interactions</li></ul><p>One major insight was that many existing systems sounded transactional rather than human.</p><p>This created an opportunity to design a more empathetic and intelligent support experience.</p><h3>Designing the Conversational Flows</h3><p>The next step was mapping conversational journeys.</p><p>I designed flows for different scenarios such as:</p><ul><li>Order status inquiries</li><li>Delivery delays</li><li>Refund requests</li><li>Order cancellation</li><li>Failed deliveries</li><li>Escalation to support agents</li></ul><p>The goal was to keep conversations:</p><ul><li>Simple</li><li>Context-aware</li><li>Action-oriented</li><li>Natural and human-like</li></ul><p>Each flow was optimized to reduce cognitive load while still providing clarity.</p><h3>Conditional Flows &amp; Edge Cases</h3><p>Voice experiences become truly useful only when they can handle unexpected situations.</p><p>To improve reliability, I mapped conditional flows for scenarios like:</p><ul><li>Incomplete user responses</li><li>Incorrect inputs</li><li>Ambiguous intent</li><li>Multiple active orders</li><li>Failed authentication</li><li>Network or system issues</li></ul><p>Designing these edge cases helped ensure smoother recovery during conversations.</p><h3>Response Design</h3><p>I created conversational response patterns for multiple user intents.</p><p>The responses were designed to:</p><ul><li>Acknowledge user concerns</li><li>Maintain clarity</li><li>Avoid robotic phrasing</li><li>Provide actionable next steps</li><li>Create trust through transparency</li></ul><p>For example, instead of saying:</p><blockquote><em>“Your order has been delayed.”</em></blockquote><p>The assistant would respond with something more human-centered like:</p><blockquote><em>“Your order is taking slightly longer than expected, but it’s currently being prepared and should reach you soon.”</em></blockquote><p>Small changes in tone significantly improved the overall experience.</p><h3>Testing &amp; Validation</h3><p>Finally, I documented test cases to evaluate:</p><ul><li>Intent recognition</li><li>Conversational success rate</li><li>Error recovery</li><li>User comprehension</li><li>Escalation handling</li><li>Flow completion</li></ul><p>Testing helped identify gaps in conversation clarity and edge-case handling.</p><h3>Key Learnings</h3><p>This project reinforced several important Voice UX principles:</p><h3>1. Conversations should reduce anxiety</h3><p>Support interactions are emotional moments. Tone matters as much as functionality.</p><h3>2. Simplicity improves trust</h3><p>Users prefer concise and clear communication over overloaded information.</p><h3>3. Edge cases define the experience</h3><p>The real strength of conversational systems appears when things go wrong.</p><h3>4. Voice UX requires systems thinking</h3><p>Designing conversational experiences involves flows, context management, psychology, and operational constraints.</p><h3>Final Thoughts</h3><p>Voice UX is not just about making systems speak.</p><p>It’s about designing conversations that feel intuitive, supportive, and human.</p><p>Order Assist explored how conversational design can transform stressful support interactions into smoother experiences through empathy, clarity, and intelligent flow design.</p><p>As voice interfaces continue to evolve, designing meaningful conversational systems will become an increasingly important skill for product designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*INl3UM2oqIopu_ZfF5rxgA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93d5d9de027b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Persona Craft — concept!]]></title>
            <link>https://medium.com/@namratapatel_69309/persona-craft-concept-75da8c5f64a3?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/75da8c5f64a3</guid>
            <category><![CDATA[genai]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Wed, 06 May 2026 17:14:28 GMT</pubDate>
            <atom:updated>2026-05-06T17:14:28.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WXmN6vrQp1THyDE0DvVo6w.png" /></figure><h3><strong>Why PersonaCraft?</strong></h3><p><strong>Concept:</strong><br> PersonaCraft is an innovative generative AI tool that assists UX/UI designers in creating user personas for their design projects.</p><p><strong>Scenario-based Persona Creation:</strong></p><ul><li>Allows designers to input specific scenarios or use cases relevant to their project, and generates personas with behaviors and preferences aligned to those scenarios.</li><li>Ensures personas are tailored to the unique needs of the design project.</li></ul><p><strong>Customization and Iteration:</strong></p><ul><li>Enables designers to customize generated personas by adjusting attributes, preferences and scenarios.</li><li>Supports iterative persona development, allowing designers to refine and evolve personas over time.</li></ul><p><strong>Integration with Design Tools:</strong></p><ul><li>Seamlessly integrates with popular design tools such as Figma, Sketch or Adobe XD, allowing designers to directly import generated personas into their projects.</li></ul><h3><strong>User Flow</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*n_mpsCNj3F0ZEqLb91P3Tg.png" /></figure><h3><strong>Landing screen</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8m7Vxc3fISyKvnafcEaAVw.png" /></figure><h3><strong>Prompt it and generate it!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtkDQUJiNcQkBdXjvnTSWA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_65i8ddFwntAyxeCFkx2g.png" /></figure><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75da8c5f64a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why content commerce?]]></title>
            <link>https://medium.com/@namratapatel_69309/why-content-commerce-c4457bb1469d?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4457bb1469d</guid>
            <category><![CDATA[content]]></category>
            <category><![CDATA[e-commerce-solution]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Wed, 06 May 2026 11:47:08 GMT</pubDate>
            <atom:updated>2026-05-06T11:47:08.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwS9GjOpJDX2Wfw7M1wDWg.png" /></figure><p><strong>Problem:</strong> Mobile users face difficulties navigating the website or accessing relevant information.<br><strong><em>Content Commerce Solution:</em></strong> Optimize content for mobile devices, create mobile-friendly product pages, and implement visual and interactive content that enhances the mobile shopping experience.</p><p><strong>Limited Social Proof:</strong><br><strong>Problem:</strong> Customers are skeptical due to a lack of social proof and peer recommendations.<br><strong><em>Content Commerce Solution:</em> </strong>Showcase customer reviews, testimonials, and user-generated content on the website to build trust and credibility, reassuring potential buyers about the quality and popularity of products.</p><p><strong>Ineffective Cross-Selling and Upselling:</strong><br><strong>Problem:</strong> Cross-selling and upselling efforts are not yielding significant results.<br><strong><em>Content Commerce Solution</em>:</strong> Integrate dynamic content recommendations and product bundles based on customer preferences and behaviors to enhance the cross-selling and upselling experience.</p><p><strong>Lack of Personalization:</strong><br><strong>Problem:</strong> The online shopping experience feels generic, and customers are not presented with personalized product recommendations.<br><strong><em>Content Commerce Solution:</em></strong> Utilize data analytics and customer profiling to deliver personalized content recommendations, product suggestions, and targeted promotions based on individual preferences and behavior.</p><p><strong>Low Customer Engagement:</strong><br><strong>Problem:</strong> Customers are not actively engaging with the online store, resulting in low conversion rates.<br><strong><em>Content Commerce Solution:</em></strong><em> </em>Implement interactive and engaging content such as product videos, tutorials, and user-generated content to enhance the customer experience and encourage interaction.</p><h3><strong>Current Product listing pages </strong>(PLP)<strong> of E-coms</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewwTQrjghx6qR08vYQfHGA.png" /></figure><h3><strong>Concept content commerce</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lV9xxYkP_kvLVcxTXoAH0w.png" /></figure><p>Reels-style content is highly engaging and can drive conversions.</p><p>Thanks for your time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4457bb1469d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s create Short form videos from long form content!]]></title>
            <link>https://medium.com/@namratapatel_69309/lets-create-long-form-videos-to-short-from-contents-5cd55bca0b70?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cd55bca0b70</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[genai]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Tue, 05 May 2026 16:52:19 GMT</pubDate>
            <atom:updated>2026-09-05T05:15:40.810Z</atom:updated>
            <content:encoded><![CDATA[<p>Gen AI</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*Jj-pwqagSwE0yUz9nEQ0EA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*kmv8Ms4b7kAnteh8MrQ4nA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*nA4MHSXbDRc6VsepeeUdRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*jKoBDn1TQ8qs0MQjlIIW_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*SNYSlnuIwv2rUBHutkE_cw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*knPg-xtFtVQoljWO2Gdjnw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*H2hXSK8T13cV47MCYy1SvQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*DsW9Py8d-eAxYiMtxD1ExQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*F03XSX3qMajQMJ5zoEZmZA.png" /></figure><p>Competitive Bench Marking</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PoLHeYp-CsrB4pHaMRPS5A.png" /></figure><p>How long form videos are uploaded and short from are created and edited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bqagrJARFflOcBGtmm2IQ.png" /></figure><p>Video Editor UI V1 &amp; V2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5lc4lay_mxgGlkfoJpjrhw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgT9Nrqf1uZvHm3KgcHLIA.png" /></figure><p>Thanks for your time here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cd55bca0b70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zomato — Reducing food order cancellation]]></title>
            <link>https://medium.com/@namratapatel_69309/zomato-reducing-food-order-cancellation-a615133c47c3?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a615133c47c3</guid>
            <category><![CDATA[zomato-case-study]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 07:19:28 GMT</pubDate>
            <atom:updated>2026-04-28T07:19:28.557Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xdT6BZnk8XSJknVPzNR4g.png" /></figure><p>Deepindar Goyal X’ed (tweeted) that about 4 lakh orders cancellation per month, inspite if their no-refund policy.</p><p><em>We were curious to understand what could be the reason?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omVGYbC1JCZHxnI5a7hpEw.png" /></figure><p><strong>Research 1st approach</strong> always works. So we did send out out <strong>UX survey.</strong><br>Meanwhile our <strong>secondary research</strong> was in progress while we waited for the UX survey responses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMnS0OB-GnnN65WjrJPsIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kwCDCM8klX7pcyhlkvpmQQ.png" /><figcaption>Online tweets</figcaption></figure><p>Post that we received a good sample of 21 responses. And we did the analysis of that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ADfuuweNqvdtXyXhCHgVeA.png" /><figcaption>The data distribution</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2mDaTyoSfBRkGqImlQVvKA.png" /><figcaption>What the actual users said / meant</figcaption></figure><p>Post this we spoke to a few users to understand their pain points</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWGoG2bnoo9KABVGVNHJhg.png" /><figcaption>Actual user words</figcaption></figure><h3><strong>Why users cancels orders?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sy3UeI_4hhqOnncXOhBsSA.png" /></figure><h3><strong>Key problems identified!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFVA9RiN6yIkuopFoMXefQ.png" /></figure><h3><strong>How users are placing the order currently and the their pain points!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*skzlsFMebO4lU8On5o8i7g.png" /></figure><p>Post all the research, it was during ideation I got some 3–4 idea that can improve the experience for the users and avoid cancellation.</p><p>There we failed ideas as well, where the user experience wasn’t great, due to taking them to mode where they need to click thrice before they cancelled.</p><p>High fidelity designs solutions and the <strong>prototype.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibczlj8hlyJFfQwQeiReZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Jza0_cH8no6sMLKp639og.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*H8pYmecnc7T4FhtObLnsYw.gif" /></figure><p>This is what I came up post the research, the actual issues users were facing and solution that could help them build trust while placing the orders, where we communicate and over comminicate to our users at every point.</p><p>Thanks for your time here!🌼</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a615133c47c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zoomcar — Unified App]]></title>
            <link>https://medium.com/@namratapatel_69309/zoomcar-unified-app-67e770db6a4e?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/67e770db6a4e</guid>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 16:56:44 GMT</pubDate>
            <atom:updated>2026-04-27T16:56:44.214Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/feed/update/urn:li:share:7227162060634079232/">Link here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSLRrTGTssk3aQKei7djJg.png" /></figure><h3><strong>What is unified app?</strong></h3><p>Zoomcar rolled out a completely redesigned and feature-rich <strong>Zoomcar app</strong>, built to make both hosting and renting cars simpler, faster, and more intuitive.</p><p>With over <strong>20,000+ hosts</strong> already on the platform and with this update a <strong>unified app experience</strong> that serves both sides of the marketplace (<strong>Guest &amp; Host</strong>). This redesign is a step forward in building a more efficient, trustworthy, and scalable car-sharing ecosystem in India.</p><p><strong>Role : Lead end to end from research to design.</strong></p><p><strong>How did I start?</strong></p><p>As a designer it was very important for me to cater to both the persona’s (Host’s &amp; Guest’s), and the scary part was designing the experience for both of them on the same application.</p><p><strong>Story behind the scenes!</strong></p><p>We started talking to our users to understand their booking journey, and later on we realised we need to understand their thinking, behaviour everything they do before they decided to rent a car…, etc.</p><p>So we shifted out research goal to understand pre booking journey as well, Like, <br>How do they plan?<br>Where do the stay?<br>How many people travel?<br>With friends or family?…….and so on.</p><p>So one one of the persona’s was — a guy who just joined a company recently wanted to spend time with his friends, so he decided to plan somewhere near by, he also wanted something affordable to stay, and travel.</p><p>That’s where he came across AirBnb and Zoomcar, that’s how we understood the pre booking journey.</p><p>Boom! That’s when I thought should we explore Airbnb? Love them for their simply sleek designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*bZRpQhkVIzOeFYmMeRxYJQ.png" /></figure><p>That’s when I realised that, host’s and guests are both on the same platform, so explored their switching journey etc. And a few other competitors.</p><p>Post that we started discussing about the different entry point for the users on the home page or the profile and how will the user navigate through the system if they are hosts or guests.</p><p>How can user easily switch from Host to Guest! vicea versa.<br>Is it going to help business in anyway? What if it backfires?<br>Host see how his car looks like etc….., tons of things running on top of my head.</p><h3><strong>User flow — after all the brainstorming</strong></h3><p>This is how we decided the different user persona navigates within the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UlbzD8DZiNxyFlQN4BrPKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*OELQ-e2PqcCFPjwycjElUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*liQSmTdCF7YIML6DMO_8tA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*VRLbsfwki4gVlZ5B6Lrsjg.png" /><figcaption>These are the design mocks for the user that can switch between Host and Guest experiences.</figcaption></figure><p>Thanks for the reading!🌸</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67e770db6a4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Myntra-Reducing Return-driven Logistics Losses (Business case study)]]></title>
            <link>https://medium.com/@namratapatel_69309/myntra-reducing-return-driven-logistics-losses-business-case-study-f44b7d10cc73?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f44b7d10cc73</guid>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 08:28:24 GMT</pubDate>
            <atom:updated>2026-04-21T08:28:24.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmYdOF36esI0wejDQnrncw.png" /></figure><h3><strong>Background :</strong></h3><p>In a recent interview, former CEO Ananth Narayanan highlighted that over <strong>30% of fashion products purchased online are returned</strong>. A large share of these returns stem from<strong> size and fit issues or a mismatch between the product and its online representation.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VP92fcb1k8xFJ5C-6Ny4Ow.png" /></figure><p>Time taken for the Research (UX survey &amp; user interviews), Ideation &amp; Design is 4 days!</p><h3>📖 <strong>How we understood our users </strong>:</h3><p>According to Don Norman a <strong><em>true design must be grounded in research and understanding of human needs.</em></strong><br>So the first thing to do was to understand why are users returning the fashion products on Myntra! (Link to UX Survey is <a href="https://docs.google.com/forms/d/e/1FAIpQLScVd3tqzjIrqnv0QR85Za8JflL7-45A8Ey0jT6Grrgd8Y8MAQ/viewform">here</a> &amp; User data <a href="https://docs.google.com/forms/d/e/1FAIpQLScVd3tqzjIrqnv0QR85Za8JflL7-45A8Ey0jT6Grrgd8Y8MAQ/viewform">here</a>).</p><p><strong>Some research data :</strong></p><p>Importance of asking right questions! You get great data in return.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nfMSAJKHxGcZd3_OtstIBg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9-_XTvgGJX-Z700HuZtaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8edablEuF05jy5qq078ryw.png" /></figure><p>This is what we understood from the survey that was shared.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YyI9CkVd4CFVzFicLNbMEA.png" /></figure><h3>🧑 <strong>What our users actually said (<em>users voice</em>)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OsvzGfnp-LYtvmc4-APzTw.png" /></figure><p><strong>Pattern that was drawn</strong> : Most complaints centre on fit/sizing surprises and material quality, both are solvable with better PDP information before the purchase.</p><p><strong>Top insight from data </strong>: Half the users want comparison with standard sizing, followed closely by photos on different body types, both are actionable PDP improvements.</p><p><strong>Audit note:</strong> Brand rating of 4.2 vs only 2 product reviews with 3.5 rating creates a trust gap — users can’t tell if the brand score reflects this product.</p><h3>💡<strong>4 PDP Improvements for Size &amp; Fit</strong></h3><ol><li>A “<strong>Fit assist</strong>” button sits directly on the PDP. Tapping it opens a chat conversation with a Myntra AI assistant. The assistant first asks the user what their issue is (not finding right fit / colour was different / not finding right style), then asks for body type (Pear, Triangle, Apple, Hourglass), followed by waist size. Based on these inputs, the AI recommends a specific size (e.g. “I’d suggest size M based on the information you provided”) and shows a photo of the product in that size. It then shows a side-by-side comparison of two sizes (e.g. M vs S) so the user can see the difference visually. Finally it asks whether to add the recommended size directly to cart, reducing friction to zero.</li></ol><p><strong><em>High fidelity designs here :</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*HtvvawSz0kDpOne-A6PaEQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*7PHiTIDzobe-W5IJzopKZQ.png" /><figcaption>Fit Assist” button on PDP → chat flow → size recommendation → add to cart</figcaption></figure><p>2. <strong>Size Comparison</strong> Dynamic Model Photos Per Size. When a user taps on a size (S, M, L, XL, XXL) in the size selector on the PDP, the main product photo instantly updates to show a model of the matching body type wearing that exact size. For example, tapping “S” shows a slim model in the kurti; tapping “L” shows a plus-size model in the same kurti — giving an immediate, realistic sense of how the fit changes across sizes. Users can also tap “Compare Sizes” to see two sizes displayed side by side in the same screen — making the difference in cut, length, and silhouette immediately obvious. The same feature works for menswear — tapping L on the blazer shows a larger frame model, and the comparison screen shows two models side by side.</p><p><strong><em>High fidelity designs here :</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEVc8DLYbzbeyxJxRqYsqw.png" /><figcaption>Tapping S/M/L/XL on PDP changes product photo to a model matching that size, with side-by-side comparison.</figcaption></figure><p>3. A small <strong>Badge </strong>“<strong>Low return rate</strong>” helps users to make a decision.</p><p>4. An <strong>AR (Augmented Reality</strong>) icon is placed on the top-right corner of the product image on the PDP. Tapping it activates the phone camera and overlays the garment on the user in real time — letting them see exactly how the item looks on their body, in their real lighting, before making any purchase decision. This directly addresses the “<strong>I couldn’t visualize how it would look on me”</strong> problem cited by<strong> 23.3% of survey respondents.</strong> Users can check colour accuracy, fit silhouette, and proportions all at once, reducing both size-related and colour-mismatch returns.</p><p><strong><em>High fidelity designs here :</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*HtvvawSz0kDpOne-A6PaEQ.png" /></figure><p>Thank you for you time here! 🌼</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f44b7d10cc73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ChatBot Design Process]]></title>
            <link>https://medium.com/@namratapatel_69309/chatbot-design-process-2f1e30aaf378?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f1e30aaf378</guid>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[conversational-commerce]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Thu, 20 Dec 2018 15:08:47 GMT</pubDate>
            <atom:updated>2018-12-20T15:08:47.662Z</atom:updated>
            <content:encoded><![CDATA[<p>The chatbot design process includes all the research involved while designing the conversations for the chatbot.</p><p>It is important that you have clear goals for your bot before you even start to think about the design.</p><ol><li>Understand if the business really needs a chatbot.</li><li>If yes, know your potential or target users and interview them. (Requirements and Scope from the stakeholder.)</li><li>In the first place, come up with the possible use-cases where chat works the best to solve a user query/problem. Start analyzing the personas for the product.</li><li>Next, we can proceed with user flow, how the user will have his journey throughout, for every use-case.</li><li>Now, let’s get started with the task flows. Define each of the tasks flows for the use-cases, step by step.</li><li>Give your bot a personality and a face on the basis of the goal set. Introduce your Bot to the users.</li><li>Start designing the conversations. Convert the task-flow to a chat. Write the scripts like what should the Bot respond and what would the user ask in a common excel sheet (Which will be helpful for the developer while he starts to build the Bot)</li></ol><ul><li>Once the bot is developed on the bot platform, start testing as a real user. Get the insights.</li><li>Ask the test users to start having conversations with the chatbot. You will have a lot of insights on exactly where the chat flow is breaking, or the users are hanging etc.</li><li>Now, go through the chat logs, analyze the observations made.</li><li>Make a note of all the utterances or the keywords and use cases which were missed in the initial draft. Add them while you train the Bot.</li></ul><ol><li>Since these are chatbots very few GUI components are suggested.</li><li>Have a Bot Review session. Get a test user. Start having the conversations. Get the insights. Observe. Analyze. Train the Bot. Repeat.</li></ol><p>(This is how you can improvise the user experience, retain the customers and acquire more of them.)</p><h4>When designing conversations keep these seven things in mind:</h4><p>1. <strong>Engage: </strong>Be responsive and poignant. Reply if not interrupting.</p><p>2. <strong>Recall: </strong>Be aware of context. Listen, don’t ask things you already know.</p><p>3. <strong>Anticipate: </strong>Be predictive when possible.</p><p>4. <strong>Adapt: </strong>Conversation is organic, it flows, it has a rhythm. It’s not mechanistic or rule-based.</p><p>5. <strong>Reflect: </strong>Repeat important pieces of information to confirm user needs.</p><p>6. <strong>Pull: </strong>Use cues, directions, or instruction to steer the flow of the conversation.</p><p>7. <strong>Flow: </strong>If your service operates asynchronously, send users a simple message if no-one is online. If your service is synchronous (<em>powered by a bot/machine</em>) don’t bombard them when they send their first message.</p><p><strong>It is important that you have clear goals for your bot before you even start to think about the design.</strong></p><ul><li>What do you want your chatbot to do?</li><li>How do you want your bot to accomplish the goals?</li><li>What do you want users to get out of their interaction with the bot?</li><li>How do you want users to interact with your bot?</li></ul><p><strong>It is equally important for you to remember that you are designing your bot for a two-fold purpose.</strong></p><ul><li>To meet the expectations of the end user.</li><li>To convince potential clients that purchasing your bot will be worthwhile.</li></ul><h3>Build Your First Interaction</h3><ul><li>Making familiar with a key expectation (key offerings)</li><li>Giving users hint or guide user in further conversation building</li><li>Provide a call to actions (Ex: Quick Replies Or Buttons)</li><li>Provide default actions (Card Views etc)</li></ul><h3>Build Conversations &amp; Intelligence</h3><ul><li>Think from user’s point of view, in how many ways they can ask for a particular use-case or a journey?</li><li>Humazine your Bot.</li><li>A personality for Chabot</li><li>Tackle ambiguous inputs</li><li>Break messages into simple and small sentences. (Don’t bombard)</li><li>Intelligence — for recommending, suggesting and analyzing the user’s context, motives, and expectation</li><li>Keep a record of user’s previous interactions, their choices, queries, messages, demographics</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f1e30aaf378" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Acquisition vs User Retention]]></title>
            <link>https://medium.com/@namratapatel_69309/user-acquisition-vs-user-retention-28acf7b17640?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/28acf7b17640</guid>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Mon, 10 Dec 2018 05:01:01 GMT</pubDate>
            <atom:updated>2018-12-10T05:01:01.053Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey guys!</p><p>This article is about customer acquisition and retention. Hope you enjoy reading this.</p><p><strong>What is Customer Acquisition?</strong></p><p><strong>Gaining new customers is the main goal of customer acquisition.</strong> It means that the process is focused mostly on <strong>marketing</strong>, which is basically communicating with the customers or attracting new customers through targeted messages or emails while giving some interesting information or offers etc.</p><p>Most companies market via ads or commercials in order to trigger the interest of potential customers. Companies may also use <strong>direct marketing</strong>, which is when an employee of the company speaks directly to potential clients in hopes of gaining their business.</p><p><strong>Acquisition Strategy Typically Includes :</strong></p><ul><li>Identify your potential customers (users)</li><li>Designing and implementing marketing strategies for users in order to use the product</li><li>Measuring the success of strategies</li></ul><p>Regardless of the marketing strategy, it is still expensive and time-consuming gaining new customers/users. More importantly, the company can’t be sure that they will even gain a new customer through these processes.</p><h4>* Acquiring Customers Isn’t Enough. Here’s Why You Need to Focus on Retention.</h4><p><strong>What is Customer Retention?</strong></p><p>Retaining the acquired customer becomes very important. The focus on customer retention is on nurturing the relationship with current customers so that they will continue to use the product.</p><p><strong>Retention Strategy Typically Includes :</strong></p><ul><li>Feasibility</li><li>User-Friendly</li><li>User Interests</li><li>Anything that encourages customers to continue using the product.</li></ul><p><strong>Why customer retention is better than customer acquisition?</strong></p><ul><li>According to <strong>Linda Bustos from </strong><a href="http://getelastic.com/"><strong>getelastic.com</strong></a><strong>, 44% </strong>of companies focus more on <strong>customer acquisition</strong> vs<strong> 18% </strong>that focus on<strong> retention.</strong></li><li>Which is a shockingly low percentage considering that <a href="http://www.forbes.com/sites/alexlawrence/2012/11/01/five-customer-retention-tips-for-entrepreneurs/?__hstc=32807841.12fdf7f0d9e1a4e4127eacd91e9e7015.1420565079181.1420565079181.1420565079181.1&amp;__hssc=32807841.1.1420565079181&amp;__hsfp=111348769#32252e7f17b0">increasing your<strong> customer retention efforts by just 5% can increase a company’s profitability by 75%</strong></a><strong>…!</strong></li><li>It is much easier to convince existing customers to continue using the product.</li><li>Acquiring new customers is much more expensive than keeping the ones you already have. You don’t need to go through the lengthy, costly process of finding and converting potential leads.</li><li>Your current users just need a small nudge to keep them engaging with your app.</li><li>It’s faster and cheaper.</li></ul><p><strong>How to retain your users?</strong></p><ul><li>Keep them engaged on a regular basis this can be done by <strong>push notification</strong>. Push notifications have the ability to<strong> boost retention rates by a staggering 180%.</strong></li><li>Know their interests.</li></ul><p><strong>Final thoughts</strong></p><p>In case, if you’ve just launched your mobile app, user acquisition is going to be your primary concern and this is certainly the most important thing to concentrate on at the very beginning of your app’s life. But in the long run, app user retention is going to allow you to build a relationship and develop loyal app users. One loyal app user is of more value to you than 10 one-off users.</p><p><strong>Customer Retention = Customer Acquisition</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28acf7b17640" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Friendly Error Message Conversational Design]]></title>
            <link>https://medium.com/dtalks/user-friendly-error-message-conversational-design-b614505a7e3c?source=rss-39b0253578f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b614505a7e3c</guid>
            <category><![CDATA[error-handling-design]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <category><![CDATA[conversation-design]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <dc:creator><![CDATA[Namratha Patel]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 07:37:17 GMT</pubDate>
            <atom:updated>2022-02-16T13:42:32.423Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey guys!</p><p>This article is all about Error Handling conversational design.</p><p>While having conversations with <strong>chatbots</strong> we happen to come across several error messages like “<em>I’m sorry I didn’t get you” ,“I think you’re looking for something I cannot help you with.” ,“Sorry! I didn’t understand</em>” etc.</p><p>These kind of messages keep the user confused like what next?🤔 Or keep the user hanging and he won’t be able to exit out of the conversation and he might drop off (this in turn affect the business).😕</p><p>You might have experienced that your chatbot is receiving random questions 🤷from the users who are clearly testing the chatbot in every possible way. These irrelevant and random questions can be named as <strong>conversational divergences</strong>, which cannot be prevented.</p><p>Here are some of the conversational design as Error Message examples:</p><ol><li>If the user enters invalid phone number — <em>Invalid Phone number!<br> Please enter your10 digit valid Phone number.</em></li><li>If the user enters invalid policy number — <em>Invalid Policy number!<br> Please enter the valid Policy number.</em></li><li>If the user enters invalid email address — <em>Invalid Email ID! <br> Please enter your valid Email ID.</em></li><li>If the user enters invalid OTP— <em>Invalid OTP! <br> Please enter the 4 digit valid OTP.</em></li></ol><p>* If the user enters anything that is invalid always ask them to enter the valid one. Here the conversations are straightforward.</p><p>*The Bot explains what is the error and ask the user to enter the valid input.</p><p>*Making user understand what exactly the Bot expects is very important.</p><p><strong>Always know that your users are never wrong…! </strong>😉😜</p><ul><li>In general a chatbot, conversations are designed and created for a particular use-case or expecting a certain input from the user. Therefore it is clear the it will be not able to answer all the possible questions asked. 💔</li><li>If you can deal with the user in such situations, there are a good chance of ensuring a <strong>positive user experience</strong> while having the conversation.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b614505a7e3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dtalks/user-friendly-error-message-conversational-design-b614505a7e3c">User Friendly Error Message Conversational Design</a> was originally published in <a href="https://medium.com/dtalks">Dtalks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>