<?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 Sunidhi Kashyap on Medium]]></title>
        <description><![CDATA[Stories by Sunidhi Kashyap on Medium]]></description>
        <link>https://medium.com/@sunidhi.kashyap1?source=rss-aac4162c6d34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7rl3bxnxXrNWjLRn-mlw2A.jpeg</url>
            <title>Stories by Sunidhi Kashyap on Medium</title>
            <link>https://medium.com/@sunidhi.kashyap1?source=rss-aac4162c6d34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:33:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sunidhi.kashyap1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How we enhanced OYO’s product experience via micro-interactions & transitions]]></title>
            <link>https://medium.com/oyo-product-design/how-we-enhanced-oyos-product-experience-via-micro-interactions-transitions-1bfa91a77333?source=rss-aac4162c6d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bfa91a77333</guid>
            <category><![CDATA[ui-animation]]></category>
            <category><![CDATA[animation-and-design]]></category>
            <category><![CDATA[microinteractions]]></category>
            <dc:creator><![CDATA[Sunidhi Kashyap]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 13:10:06 GMT</pubDate>
            <atom:updated>2022-12-22T11:06:34.863Z</atom:updated>
            <content:encoded><![CDATA[<p>This article will quickly cover all that is required to plan &amp; implement a product’s interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xW-dkXLHDWrOm3UnJL0whQ.jpeg" /></figure><h3>🛠 Steps that we followed</h3><ol><li><strong>Benchmarking &amp; setting up rules: </strong>We spent about a month on this. It helped us to back our decisions at every step &amp; convince the stakeholders to implement our designs.</li><li><strong>Defining the scope: </strong>We listed down every single flow in our product &amp; mapped it with the micro-interaction required.</li><li><strong>Understanding tech &amp; physics attributes: </strong>We dived deeper into the world of motion physics to implement organic animations. We also read through android developer documentations available online to understand tech constraints.</li><li><strong>Involving the tech team: </strong>Check the tech feasibility of the designs before hand. Find out the tech stack &amp; what attributes they require to implement the designs.</li></ol><blockquote>Tip: Keep the tech team involved at all steps.</blockquote><p>6. <strong>Building, reviewing &amp; iterating.</strong></p><p>7. <strong>Presenting to a larger audience: </strong>Feedbacks from the entire design team always help in delivering the best designs.</p><p>8. <strong>Implementation!</strong></p><h3>🐤 Sneak Peak</h3><p>Below are some of our creations with the though process explained behind it.</p><h4>Transformations</h4><p>Some animations required a transformation on certain UI elements in order to have smooth &amp; delightful transitions. One of the examples is the image transformation we used on the listing page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFPTSPFKmvApC0q53OgckQ.gif" /></figure><h4>Animating atomic components</h4><p>The atomic components include buttons, steppers, icons, etc. These are the components a user’s thumb directly interacts with, hence, important to provide the most ideal feedback.</p><p><strong>Buttons:</strong> In order to make the experience organic, we applied inertial bounce effect to mimic the real-world button-press effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*IEdNQpp36gQbErcqjn_LRA.gif" /></figure><p><strong>Stepper: </strong>The slot machine animation for the stepper fit just perfectly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*eY_dhZ19cU7WqsrvQApvaQ.gif" /></figure><h4>Actions</h4><p>There are certain actions specific to a function which may vary from product to product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*m5EMG6Vi65QAeBdrTI4qag.gif" /></figure><blockquote>One must list down all the use-cases within the product that may require custom-made interactions unique to the product.</blockquote><h4>Custom Flow</h4><p>There can be certain flows where the entire journey’s animations &amp; transitions play a crucial role in terms of the user experience. The best example of it would be the <em>Booking Confirmation</em> flow, where the user has no other option than to wait for the booking to be completed.</p><p>Another example would be the <em>Rewards Flow</em>, where we need to provide a positive feedback to the user when reached a certain milestone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DhR-H6LL5H2d-lza_IFo5Q.gif" /></figure><h4>Ratings</h4><p>An organic, life like animation works really well with the interface and provides user engagement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1y9NWncD0b90XwpLkrPRTQ.gif" /></figure><h4>And much more..</h4><p>Do check out our product if you want to view the motion language of the entire journey!</p><h3>✍🏻 Why did we decide to dedicatedly think about micro-interactions?</h3><ol><li><strong>Technical Aspect</strong>: Keeping user’s attention intact in case of API calls, errors &amp; loading states is extremely important in order to avoid drop-offs.</li><li><strong>Delight factor</strong>: Leaving the users feel satisfied at each step while using the app.</li><li>Lastly, because it was practically <strong>non-existent</strong> in our app.</li></ol><h3>🤜🏻🤛🏻 Team members involved in this project</h3><p>I did this project under my manager <a href="https://www.linkedin.com/in/rajat-kashyap-46310637/">Rajat Kashyap</a>. All the transitions, micro-interactions &amp; motion graphics used in the OYO’s products were designed by us.</p><p><a href="https://www.linkedin.com/in/eshu-kalra/">Eshu Kalra</a>, <a href="https://www.linkedin.com/in/vaibhavchaudhary254/">Vaibhav Chaudhary</a> &amp; <a href="https://www.linkedin.com/in/rohand7/">Rohan Deshpande</a> were the ones who made our designs a reality.</p><p>PS: Thank you so much for reading this! Here’s a flower 🌷</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bfa91a77333" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oyo-product-design/how-we-enhanced-oyos-product-experience-via-micro-interactions-transitions-1bfa91a77333">How we enhanced OYO’s product experience via micro-interactions &amp; transitions</a> was originally published in <a href="https://medium.com/oyo-product-design">OYO Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability testing: Math behind magic number 5]]></title>
            <link>https://medium.com/oyo-product-design/usability-testing-math-behind-magic-number-5-2520983c3b9d?source=rss-aac4162c6d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/2520983c3b9d</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[jakob-nielsen]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Sunidhi Kashyap]]></dc:creator>
            <pubDate>Tue, 11 Oct 2022 11:08:04 GMT</pubDate>
            <atom:updated>2022-10-11T11:46:26.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nv9tpKdfII9pVAx_b6QB8A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jeswinthomas?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jeswin Thomas</a> on <a href="https://unsplash.com/s/photos/mathematic?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Most of us in the design community are pretty much familiar with the concept of <a href="https://www.nngroup.com/articles/usability-testing-101/">usability testing</a>. One of the methods involves conducting user interview sessions with a targeted group of users in order to test the prototype of a product. Naturally, a lot of company’s resources is spent in the process which is directly proportional to the number of users tested with.</p><p>In this article I’m gonna address the question of “<strong>How many users are enough for user testing?”</strong>.</p><h4>What is magic number 5?</h4><p>Through his article, <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">“Why You Only Need to Test with 5 Users”</a>, Jakob Nielsen very boldly suggests that using no more than 5 users for a user testing session can give us the best results. And using any more will only result in a waste of resources.</p><p>The basic idea is, 5 users can uncover most of a product’s usability problems.</p><h4>Math behind the magic</h4><p><a href="https://www.nngroup.com/articles/author/jakob-nielsen/">Jakob Nielsen</a> &amp; <a href="https://fabbs.org/our_scientists/thomas-k-landauer-phd/">Tom Landauer</a> wrote a <a href="https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.544.5899&amp;rep=rep1&amp;type=pdf">research paper</a> together which gave us the following relationship between the number of users and the proportion of all problems found;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*_4HOOi8GnHjm3v-0o43NwQ.png" /></figure><p>Where <strong>p</strong> is the probability of detecting a given problem. The value of p is taken to be <strong>31%</strong>, averaged across a large number of tests conducted (data available on the research paper).<br><strong>n</strong> is the number of users &amp; <strong>N</strong> is the number of total problems in a test session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Xc3UNdRAD40cfJfZsWPJ6Q.png" /><figcaption>Image source: <a href="https://usersnap.com/blog/user-tests-5-users/">Usersnap</a></figcaption></figure><p>By this relation we find that 5 users can uncover approximately 80% of the usability issues.</p><h4>But what about the remaining 20% ???</h4><p>Well, increasing the number of users will clearly make us reach closer to that 100. But note that <strong>the graph is asymptotic, </strong>it will never really reach there. Plus, the decrease in slope suggests that eventually, no matter now many users you add, there will be very insignificant growth in the percentage of usability problems to be found.</p><p>Lost you there? Let me explain.</p><p>Testing with <strong>1 user</strong> will uncover approximately 33% of the total problems.</p><p>Testing with <strong>2 users</strong> will uncover more than 50% of the total problems.</p><p>.</p><p>.</p><p>Testing with <strong>5 users</strong> will uncover more than 85% of the total problems.</p><p>Testing with <strong>6 users </strong>will uncover about 87% of the total problems.</p><p>The increase in percentage is less for higher number of users.</p><p>At this point there’s a high chance of getting repeated insights. Given that our <strong>users are humans</strong>, we can’t expect most of them to uncover that remaining 10–15 percent of the total problems. We might not find that <strong>Nth </strong>user<strong> </strong>ever, and the amount of resources spent will linearly increase giving us <strong>no new information.</strong></p><h4>Should 5 be the absolute number?</h4><p>NO! The point of this article was not to restrict your mind into thinking this approach is the best. I wanted to explain the math behind this concept in order to show that you don’t need 50 users to test a product.</p><p><strong>You can definitely go further than 5 but you must stop once you see most of your insights repeat!</strong></p><p>Don’t have a linear approach thinking more users will give more insights. Because number of users and number of problems are not directly proportional, which we can see from the graph itself.</p><h4>Is this equation helpful in the real world?</h4><p>Hell yes! Here at OYO, I had to conduct multiple user interviews to test out the design 2.0 version of the consumer app. And I myself observed the insights getting repeated a lot after the 5th or 6th user. Most of my tests involved 7–8 users at max but the insights I had received were tremendously useful.</p><p><strong>This equation helps us understand when to stop</strong> worrying about the number of users and start thinking about other factors that can help us get more insights.</p><h4>Other factors to help make best of the user testing</h4><ul><li>Focusing more on the <strong>test design</strong> and complexity of the tasks given to a user.</li><li>Targeting the <strong>persona</strong> very thoughtfully.</li><li>Analysing the results <strong>after each user testing</strong> to look for repeating insights or patterns that may or may not seem familiar.</li><li>Using better tools for conducting sessions and analysing results.</li><li>Looking out for <strong>faulty data and biased feedbacks. </strong>In case you feel that a certain user was being biased with the feedbacks or the test environment was not very ideal, learn to discard that data and replace with a new user with same persona.</li></ul><p>Thanks for coming this far! I hope this article proves useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2520983c3b9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oyo-product-design/usability-testing-math-behind-magic-number-5-2520983c3b9d">Usability testing: Math behind magic number 5</a> was originally published in <a href="https://medium.com/oyo-product-design">OYO Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Design Internship Story— A trip to the land of OYOpia]]></title>
            <link>https://medium.com/oyo-product-design/design-internship-story-a-trip-to-the-land-of-oyopia-8658cc3681b7?source=rss-aac4162c6d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/8658cc3681b7</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[employees-corner]]></category>
            <dc:creator><![CDATA[Sunidhi Kashyap]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 15:28:10 GMT</pubDate>
            <atom:updated>2022-07-22T06:36:00.677Z</atom:updated>
            <content:encoded><![CDATA[<p><em>💫 Highlights from my product design internship with the OYO design team</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUJsF5xqZEgsw6uhEXcgGA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thoughtcatalog?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thought Catalog</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>I‘ve been with OYO since September of ’21. I had quite an experience working here and I’m going to tell you all about it.</blockquote><h4>The start of something new ✨</h4><p>The online state of my college due to the pandemic allowed me to apply for internships, so I prepared a portfolio and started reaching out to companies via LinkedIn. I also cold-emailed some of the employees of the companies that I wanted to work with. Luckily, I got a call from OYO. Then after 3 interview rounds and 10 days of waiting I finally had the offer letter in my mailbox.</p><h4>The timing couldn’t be any better ✨</h4><p>The team was upto something big. They had just started building an entire design system and I got to be a part of this! <strong>OYO design is currently in a state of a total renewal</strong>. And as a designer, there couldn’t be a better learning opportunity.</p><h3>The Work at OYO ⚔</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ENwy6405TbCNyla5Cm-b_g.jpeg" /></figure><p>Every weekday, <strong>skipping Monday</strong>, the team meets at 12 noon for a quick stand-up. Perfect for normal people who want Mondays to start a little later!</p><p>There are 2 major divisions, namely, the <strong>Consumer</strong> side &amp; the <strong>Merchant</strong> side. Luckily, I got to work on the projects concerning both the departments. These were the projects that I majorly worked on;</p><p><strong><em>1. Micro-interactions &amp; animations for the consumer mobile app &amp; desktop site</em></strong></p><p>I worked on this task with my manager &amp; the director of product design, <a href="https://www.linkedin.com/in/rajat-kashyap-46310637/">Rajat Kashyap</a>. What started for me as a <em>benchmarking &amp; competitive analysis</em> task, took a drastic turn when a unanimous decision was made to trust Rajat &amp; me with the responsibility of <em>creating</em> all the micro-interactions.</p><p>Every interaction was built from scratch. We would spend hours learning how to introduce <em>real-world physics</em> into it. The most challenging &amp; interesting part was meeting up with the developers and finding out ways to implement our designs.</p><p><a href="https://www.linkedin.com/in/vaibhavchaudhary254/">Vaibhav Chaudhary</a>, <a href="https://www.linkedin.com/in/rohand7/">Rohan Deshpande</a>, <a href="https://www.linkedin.com/in/eshu-kalra/">Eshu Kalra</a>, Rajat &amp; I would sit for hours, go through countless feedback sessions and meetings to make sure absolutely nothing was being overlooked.</p><blockquote>Tip : Have a habit of making an exhaustive list of all the use-cases.</blockquote><p><strong><em>2. Conducting usability tests &amp; research for the consumer app in India, US &amp; China</em></strong></p><p>I worked on this task with the director &amp; head of product design for consumer side, <a href="https://www.linkedin.com/in/sandeepparashar/">Sandeep Parashar</a>. I recommend you to check some of his case studies as I learned a lot on UX research and its importance while working with him.</p><p>The best part was that not only did I get to apply &amp; test all my theoretical knowledge of UX research, but also that I got to do it on a global scale. I can’t explain the excitement I felt in talking to the translator for China’s product team and walking her through the test we had designed!</p><p><strong><em>3. Conducting usability tests &amp; research for the Realisation hub on the Merchant platform</em></strong></p><p>I worked on this project under <a href="https://www.linkedin.com/in/shekhar-design/">Shekhar Kadam</a>, who’s the Director Of Product Design &amp; User Experience. Conducting user research with the Hotel Managers as our primary target audience was a whole new game! It was extremely challenging to understand and categorise them into different personas. Moreover, it was so important to prevent usability from being compromised while building everything in the new design language.</p><p>Luckily, I also had tremendous amount of help from <a href="https://www.linkedin.com/in/janithedesigner/">Himanshu Jani</a> and the project was completed successfully.</p><h3>Designathons 🧩</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hw_shlwHnN4gbQFiKmWo-w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kelly Sikkema</a> on <a href="https://unsplash.com/s/photos/work?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Each quarter, the design team takes 2–3 days off from the regular work to shake things up a little bit &amp; compete in a hackathon. Groups are formed and each quarter the competition gets more intense. This is the best time to wake up the experimental side of our minds and just brainstorm on problem statements without worrying about your regular work.</p><blockquote>We would be asked to turn down any work related call to focus on the hackathon !</blockquote><h3>Time away from the virtual desk 🎳</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibp4LOjpKYUGugQPKfPEzA.jpeg" /><figcaption>Photos by <a href="https://www.linkedin.com/in/sheethal-krishna/">Sheethal Krishna</a></figcaption></figure><p>On ordinary days the team would meet up on a zoom call occasionally to play Scribble, Geoguesser, etc. But then there were not-so-ordinary days where an offsite meet-up was arranged by our wonderful team.</p><p>This was my first time meeting everyone in person. The nicest set of people I must say! We had a lot of fun just hanging out, going out for lunch, competing hard in the bowling alley, Go-Karting, and ending each night with some karaoke and drinks.</p><h3>My 10 Months long internship 👩🏻‍💻</h3><p>’cause it just didn’t feel like looking around for something else. Let me explain why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_r6dIIpS8sMKZdIGCfymdA.jpeg" /></figure><h4>You are not just an ‘intern’ here 🙅🏻‍♀️</h4><p>You get to work and take a <strong>lead </strong>on critical, challenging and <strong>impactful</strong> projects regardless of your designation. Which was huge for me given it was my first internship.</p><p>I faced a lot of challenges and made many many mistakes but thanks to my managers I could complete all the projects successfully. This brings me to my next point;</p><h4>The mischief was always managed 🔮</h4><p>You are encouraged to learn and make mistakes here. I mean, if we were perfect from the start wouldn’t we all be directors of design instead of interns? Not just the manager but anyone from the team was always there anytime I got stuck and needed help.</p><h4>No-meeting-Wednesdays 🚫</h4><p>It was introduced for us so we could have one day in a week to focus solely on our work and not get carried away by endless meetings. Our calendars would be blocked for the whole day and we could turn down meeting requests unless it was necessary for the progress of our work.</p><h4>One-on-ones 🤜🏻🤛🏻</h4><p>Each member has monthly one-on-one sessions with their respective managers and the Program Manager. The session was always a safe space to communicate your needs, problems and your ongoing experience in the company.</p><h4><strong>The acknowledgment ✨</strong></h4><p>The team never fails to acknowledge &amp; appreciate the efforts you put in. It’d always encourage me to keep working.</p><p>They even have their <strong>Award Ceremonies</strong>!</p><h3>Key Takeaways 👩🏻‍🏫</h3><p>There were quite a few takeaways for me from this internship:</p><h4><strong>1. Communicate</strong></h4><p>You have to always remember that your work is never your work alone. In a company of this size, your work has a dependency on other people/projects and vice versa. Hence, it is important to keep everyone on the same page at all times. Which requires clear communication.</p><h4>2. Understand the time constraints</h4><p>It is extremely important to keep track of the deadlines and the progress of a certain task. Once you do that, it’ll become fairly easy to develop the art of time management. If you ever get confused or even forget the deadlines just ask your manager, and <strong>communicate</strong>!</p><blockquote><strong>Tip: </strong>Take it one week at a time. Listing down your targets for the week makes it easier to track.</blockquote><h4>3. Understand your limitations</h4><p>You are invincible! But also a human &amp; humans have certain limitations. Hence, you need to avoid over-commitment to a project. Always take a buffer when asked to provide a timeline. And communicate right away when your estimations go wrong. <strong>No one will kill you or worse, take your job away!</strong> Trust me. People always understand as long as you are being honest towards your work &amp; give your best.</p><h4>4. Take breaks</h4><p>Don’t get too absorbed by your work that you forget to take out time for yourself. If you don’t, you’ll just end up burning yourself out which will do your productivity more harm than good.</p><h4>5. Have fun</h4><p>Internships are the best time because you have the flexibility to make mistakes and learn from them. So, don’t get too much into your head. Just try to enjoy yourself and the rest will follow.</p><p>I hope this article helped you get an insight into not just how the OYO design team works but also what to expect from a product design internship. If you too want to be a part of the team, <strong>we’re hiring</strong>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8658cc3681b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oyo-product-design/design-internship-story-a-trip-to-the-land-of-oyopia-8658cc3681b7">Product Design Internship Story— A trip to the land of OYOpia</a> was originally published in <a href="https://medium.com/oyo-product-design">OYO Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>