<?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 Divya Mangal on Medium]]></title>
        <description><![CDATA[Stories by Divya Mangal on Medium]]></description>
        <link>https://medium.com/@divyamangal?source=rss-51c8a7fb438a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*1-zwrZYjWka3TSqpgJOVLA.jpeg</url>
            <title>Stories by Divya Mangal on Medium</title>
            <link>https://medium.com/@divyamangal?source=rss-51c8a7fb438a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:02:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@divyamangal/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[Learnings from organizing Figma for enhanced collaboration among cross-functional teams]]></title>
            <link>https://medium.com/@divyamangal/learnings-from-organizing-figma-for-enhanced-collaboration-among-cross-functional-teams-4b8c7f8687e3?source=rss-51c8a7fb438a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b8c7f8687e3</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[organisation]]></category>
            <category><![CDATA[designer]]></category>
            <dc:creator><![CDATA[Divya Mangal]]></dc:creator>
            <pubDate>Sun, 28 May 2023 07:00:50 GMT</pubDate>
            <atom:updated>2023-05-31T10:00:43.300Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tA6Fa0JE8oF0iDDUXkp4jQ.png" /></figure><h3>Context &amp; Problem</h3><p>We at PhonePe were building ONDC Shopping App and the product timeline was defined as 6 months. Our team comprised two designers and a design manager. As our organization and product expanded, accommodating a growing team of designers working on the same pod on figma. <strong>Problems like multiple files getting created, PM &amp; Dev getting lost in the sea of files &amp; screens and above all figma file crashing due to overloading. </strong>Hence it became crucial to establish a file structure in Figma that worked seamlessly for everyone involved.</p><blockquote><strong>Goal</strong></blockquote><blockquote>The goal was to foster more collaborative work between UX and UI designers while enabling easy navigation for other stakeholders such as product managers, developers, and additional designers</blockquote><p>In this article, I will share my learnings from the process we followed and insights we got while organizing Figma files for greater efficiency and collaboration.</p><h3>Process</h3><p>Before diving into file organization, it was important to consider the needs of different stakeholders. While designers primarily worked on Figma files, other roles like product managers, developers, and senior management also accessed and collaborated within these files. Through research and discussions, we discovered <strong>that stakeholder involvement primarily occurred during collaboration stages, while the majority of the file organization was aimed at supporting designers’ work.</strong></p><p>In the early stages of our project, where we developed the entire flow from end to end, we organized our work in Figma based on user flows and screens (view image for reference — login, address, homepage..). This approach allowed for collaboration on a single Figma file, aligning the entire flow. However, as discussions with stakeholders progressed, multiple versions of the file emerged, leading to its significant size and numerous duplicate screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C4hMYmbMXpeqfhuvuSaOkw.png" /></figure><p>This presented <strong>several issues, including overloaded Figma files crashing, new files being created by different designers, missed comments within a pool of comments, and an endless cycle of “final.final.final.”</strong></p><p>We started breaking up the files into smaller files for new requirements. Initially, we divided the flow into five major files, grouping them by relevant sections such as login, address &amp; profile,(5 files in image) etc., while structuring pages based on main releases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-8TlJTrsCyu3HzlQaqqtQ.png" /></figure><ul><li>During this phase, we realized that <strong>designs were spread across live, in-development, and conceptual phases without clear differentiation.</strong></li><li>Small silos formed within the Figma file due to different designers’ work, and there was <strong>no defined process for transitioning final designs to the master file.</strong></li><li>The<strong> master file</strong> <strong>lacked structure and clarity</strong> and prevented efficient access/reference by developers for release changes, product managers for new design updates, and QA for live versions.</li></ul><p>Following the approach led to the addition of new problems rather than solutions. We understood that this is not working.</p><p>At this time we embarked on a journey of iterations, in the hope of a better future for our Figma files and a structure that helped focus on design and our users rather than troubleshooting the process. Here are a few iterations that we tried.</p><h3>Iterations</h3><h4>Idea 1</h4><p>The segregation was such that there was a master file for all stakeholders to see what is live, the WIP version of the whole flow was divided into 2 main files i.e. Pre-purchase file and Post-purchase file. On top of it there was separate global files such as serviceability, offers etc. Now the pages within files still needs proper structuring based on collaboration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2DO1mv5lg4PWZL-GCAbZoA.png" /></figure><p>Problems that persisted with this option</p><ul><li>Overloading of files is still possible</li><li>Dev &amp; PM getting confused in the sea of screens</li><li>No proper UI &amp; UX work division</li></ul><p>After further brainstorming with the team, we developed a new idea.</p><h4>Idea 2</h4><p>Adding project formation to club files according to the usecases. The segregation was done in 3 projects.</p><ol><li><strong>Master (For stakeholders) — </strong>Source of truth for everyone after development</li><li><strong>Workarea (For Designers) — </strong>All WIP files considering main flows and global flows</li><li><strong>Depreciation — </strong>This was home to our older and retired versions.</li></ol><p>Master was for all stakeholders(including PMs, QA, bussiness and founders) who can see what is live and where the app is currently. Workarea was for designers, to get PM approvals and to give the final designs to developers to code. Depreciation was for older versions and unapproved or rejected designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdrVmPEV77H4ElEocjR4Cg.png" /></figure><p>After extensive discussions and refinements, we settled on our second idea and evolved it further. Since the work happens according to deliverables why not make a separate project exclusively for the development team? So we introduced the <strong>“releases project” which has all the finalized designs ready for development.</strong> This separation ensured that the working section and the final section remained distinct and unaffected. So now we have RDX(Master files), Releases(Development files), Workarea(In progress work files), Graveyard (Depreciated files)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-8LaVx-QfLXi0auVWXLchg.png" /></figure><p>We implemented this approach and observed significant improvements in collaboration among designers, developers, and product managers.</p><blockquote>Design Manager — “The structure is working good for us so far”</blockquote><blockquote>PM &amp; Dev — “Its much easier to find the designs now”</blockquote><p>However, it’s important to acknowledge that no approach is perfect, and <strong>design is an iterative process that evolves over time. As a result, we decided to merge the flows every four months to identify any potential issues or areas where our working methods could be enhanced.</strong></p><p>The purpose of writing this article is to share our experience and provide insights into organizing files within a growing company. While the exact techniques may not be directly applicable to every organization, the aim is to help you identify what might not be working for your team and modify the approach accordingly.</p><p>Thank you! ✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b8c7f8687e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scheduler — a calendar application]]></title>
            <link>https://medium.com/@divyamangal/scheduler-a-calendar-application-108f4321a55f?source=rss-51c8a7fb438a------2</link>
            <guid isPermaLink="false">https://medium.com/p/108f4321a55f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[calendar-apps]]></category>
            <dc:creator><![CDATA[Divya Mangal]]></dc:creator>
            <pubDate>Thu, 23 Jul 2020 07:39:11 GMT</pubDate>
            <atom:updated>2020-07-23T09:10:41.033Z</atom:updated>
            <content:encoded><![CDATA[<h3>Scheduler — a calendar application</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cq0d7tzvco2C8sqs9JiKqQ.png" /></figure><h4>Overview</h4><p>Acme is fast-growing with a large number of employees and workspace. To <strong>ease the process of scheduling a meeting and booking a room</strong> I have designed this application.</p><p><strong>CALENDAR APPLICATION</strong></p><p>Acme is a fast-growing company that is adding employees and workspace at a very fast pace. They are doubling every year both in terms of employees and workspace. Given a highly collaborative environment, employees need to schedule a large number of meetings ranging from 1:1s to large brainstorming sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_CKWdWsX82au6tDOEVFTg.png" /></figure><p><strong>Things to consider</strong></p><ul><li>The employees are spread across <strong>two different buildings in two different locations.</strong></li><li><strong>Rooms come in different sizes and not all the rooms are equipped </strong>with the same set of features and facilities.</li><li>Since<strong> new employees </strong>are joining every month, there should be a way to find out <strong>who it is that they are inviting to the meeting.</strong></li><li>Also, there needs to be a way for <strong>new employees to schedule meetings and find meeting rooms easily</strong> even when they are not familiar with the layout of the facility.</li></ul><h3>Understanding the problem</h3><p>There are several traditional calendar apps in the market which lets you schedule and track your meetings, you can even integrate some useful plugins.</p><blockquote>So why make another app?</blockquote><p>To understand <strong>why</strong> I needed to find the problems in the current system of scheduling a meeting in various types of companies. I started with research to know <strong>why to have a meeting, how to communicate, who to communicate, when to have a meeting, and where to meet.</strong> Here are the user Interviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MVuMuVCgyO_wqIAXS9GUfg.png" /><figcaption><a href="https://docs.google.com/spreadsheets/d/1LCIHqjfen8n2PnKg1f0OJQXQMB78wsKacojlJyeJR_4/edit?usp=sharing">Click here for detail view</a></figcaption></figure><h3>Insights</h3><ol><li>I founded mainly 4 types of systems —</li></ol><p><strong>System 1:</strong> Dedicated collaboration platform (ex. slack) and google calendar for scheduling and booking.</p><p><strong>System 2:</strong> No dedicated collaborated system as communication is through distributed channels. And a different tool for scheduling a meeting.</p><p><strong>System 3:</strong> Communication system is fine but no tool used for scheduling &amp; booking.</p><p><strong>System 4:</strong> Fully collaborated system where communication, scheduling, and booking is done. (ex. Microsoft teams) — since the system well collaborates it ensures no such problems occur.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4rGYtfNRmW-70xSoDur0sg.png" /></figure><p>2. Key Problems <strong>Scheduling for multiple people, Rooms info. not directly available, Switching between platforms.</strong></p><p>3. Some companies have a separate <strong>dashboard </strong>in every room which tells the booking details for the day, people can book the room from there and they have to check in while entering.</p><p>4. Some problems like missing assets in the room and people taking someone else room without booking are also there.</p><p>Considering all the use cases the <strong>user journey steps</strong> are as follows -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hF2fBhg3VRtgrRN7TEoU6w.png" /><figcaption>Pain points and joys of each step</figcaption></figure><h4>User Scenarios</h4><p>Considering the research, I created 3 possible use cases-</p><ol><li><strong>USE CASE 1</strong>: Discuss and see availability -&gt; schedule -&gt; book a room -&gt; Notify</li><li><strong>USE CASE 2</strong>: Need a room urgently -&gt; Check room -&gt; see people’s availability -&gt; book a room</li><li><strong>USE CASE 3</strong>: Pre-schedule a meeting -&gt; Book a room -&gt; notify</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*luIgJ4RD1b_EJ1-sT8zD8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1o2R6HCKw3lCk5TU5SpjGw.png" /></figure><h3>Ideation and Brain Storming</h3><h3>1. System exploration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQC6vr7_rGzY78yb-tYbdQ.png" /><figcaption>Plugin+App system was best suited</figcaption></figure><p>So, later I switched on to <strong>Plugin+App based system</strong> and try to ease the process of calling the app again and again. The system I have chosen will get all the information of groups and channels in the calendar application to provide a better experience to the employees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kv7SxMLkOwQs5YhccWB2lA.png" /></figure><h4>Problems solved</h4><p><strong>Platform Switching — </strong>The plugin in slack will directly call the app and title along with thread will be linked. (Those platforms who not support plugins can use it as a widget)</p><h4>Assumptions:</h4><ol><li>The companies are using slack and flock where plugins can be integrated.</li><li>Communication is taking place on the companies collaboration platform itself.</li><li>Acme has a dashboard outside every room that displays the booking information for that room and when people book the room they have to check-in.</li></ol><h3>2. Wireframes Ideation</h3><p>I started with ideas in my head and drawn some sketches.</p><h4>1. Home Page</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEfjkzNA56xU-N9Nbru_sw.png" /></figure><h4>2. Schedule meeting</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UM1Rg4Vh0Pczv6rOeW49Xg.png" /></figure><h4>3. Rooms information</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*frjyHX6mz6kLIxnHUjjGoQ.png" /></figure><h3>3. Flow &amp; Visuals</h3><p>For visuals, I tried to keep it clean and easy to use. Also, I have used different colors to denote the actions carefully like for example Going card shown <strong>Green for “Yes”, Red for “No”.</strong></p><ol><li>The following flow is for the use case 1 &amp; 3 i.e <strong>Discuss and see availability -&gt; schedule -&gt; book a room -&gt; Notify</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0FnwOYsMOCQT17ERKNJFjA.png" /></figure><p>2. For Use case 2 the user clicks on <strong>Screen 2 bottom nav — Book a room option. </strong>And he can directly reach<strong> Screen 6 </strong>where he can add time(default current time), No. of participants, and the requirements.</p><h4>Problems solved</h4><ol><li>In case of <strong>urgent booking,</strong> employees can directly book the room by just adding no. of participants and time. (Screen 6)</li><li>Can keep account of who is going in meeting and who isn’t. And can directly know through linked conversation. (Screen 1)</li><li>Adding <strong>multiple people</strong> in a single go is easily possible also their availability is easy to find. (screen 4 &amp; 5)</li><li>If the new employee doesn’t know who to contact he can just find by <strong>designation</strong> or by team channel. (Screen 4)</li><li><strong>Booked room information</strong> is clearly visible so if lesser people take a bigger room or in case of any other problems people can negotiate knowing the booked room information. (Screen 8)</li><li>For a new employee, it is easy to navigate through a <strong>map view </strong>and also find the desired assets. (Screen 9)</li><li>The new employee can easily know <strong>who it is that he is inviting</strong> to the meeting. For this, I have made a feature of a long press on any name of the person within the app. (Employee would get to know about this feature in onboarding.)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iiv7DS7Lm5XuxEJe0BzNLw.png" /></figure><h4>Notifications</h4><p><strong>Push notification</strong> improves the customer touchpoint to make a decision without opening the app. Therefore missed notifications problems can be solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tMlOmiFHXNe8ikarAKqr_g.png" /></figure><p>The following notifications should be given.</p><ol><li>In case of meeting notification. And if you are not going then mention the reason. (not necessary though)</li><li>If multiple meetings are booked at the same time for a single person.</li><li>If a particular meeting is postponed/preponed.</li><li>If the meeting gets canceled. (with a reason)</li><li>If the person was searching for a room is now available.</li><li>Alert notification<strong> before meeting time</strong>(default 10 mins before)</li><li>Alert notification <strong>after meeting time</strong>(default 10 mins) only if the person if not in the booked room.</li></ol><h4>What more I could have done!</h4><p>As I was on the verge of completion, I realize that another aspect to see them solve the problem of scheduling the room is to<strong> give room information and the ability to edit that info. </strong>Basically an admin side to manage the room and additional room info page on the customer side.</p><p>This particular section may contain all the minute information related to rooms like <strong>who has booked, percentage of occupancy, the maximum time for which the room can be booked, and report for missing assets.</strong></p><p>Also, I thought of additional ideas that can be integrated into fruition like upgrading to a better room in case of a momentous vacancy.</p><h4>Lessons learned</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3kWzQUsF4rLjOcQjuaR69Q.png" /><figcaption>Illustrations — <a href="https://blush.design/">https://blush.design/</a> <a href="https://medium.com/u/7f968435c6b9">Pablo Stanley</a></figcaption></figure><h4>Conclusion</h4><p>Initially, I thought why to design a calendar app if you have a google calendar for everything which was really a big question mark for me. Then after talking to people and analyzing the problem I came across many problems that needed to be solved. I have tried my best to give the best experience to the employees of acme.</p><p>Although there may be some problems that are unsolved. As the design is an iterative process and can be improved with changing human behavior.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=108f4321a55f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dealing with the loopholes of quantitative research]]></title>
            <link>https://uxdesign.cc/dealing-with-the-loopholes-of-quantitative-research-c082f2571ab5?source=rss-51c8a7fb438a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c082f2571ab5</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[user-personas]]></category>
            <category><![CDATA[quantitative-research]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Divya Mangal]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 11:02:08 GMT</pubDate>
            <atom:updated>2020-01-15T12:18:48.441Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eKqhVmv06W3StEB9M2brbw.png" /></figure><p>Quantitative Analysis lets us derive important facts from research data, including preference trends, differences between groups, and demographics. Quantitative studies’ great strength is providing data that is descriptive — for example, allowing us to capture a snapshot of a user population who has a specific problem.</p><blockquote>But — —</blockquote><p>We encounter difficulties when it comes to <strong>“WHY”</strong> they have that problem. To overcome this problem, one needs to know all possible “<strong>WHY’s</strong>” before conducting a survey. Let us understand the process through this project.</p><blockquote><strong>We have to redesign the process of the SAC IITR Discussion forum — a single multipurpose platform of IIT Roorkee, for posting problems, having discussions, and declaring announcements from the senate meetings. This system currently had a closed facebook page for the same purpose.</strong></blockquote><p>This project is for the community by the community and therefore required high user involvement. This project allowed me to survey a vast audience and dive into quantitative &amp; qualitative research together.</p><h3>Know your user well</h3><blockquote>Who am I building the product for — — —</blockquote><p>Since we had a wide variety of users studying in IIT Roorkee, ranging from one who doesn’t care about what is wrong, to those who promote wrong. So firstly, we classified our user base into three main categories according to their behavior, to study them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8gR-EGNor7xPYa-t77-nDA.png" /></figure><p>We were mainly building the product for Active and passively active students. Therefore we need to focus on issues that they were experiencing in the current system and later try to solve them.</p><p><strong>Quantitative research is usually done to know the data on existing products and thereby, analyzing the current problems of the users.</strong> Being a student of IIT Roorkee, I had the advantage of experiencing the situations of the above personas myself.</p><p>But, to gain <a href="https://www.researchgate.net/publication/256053334_Qualitative_and_Quantitative_Research_How_to_Choose_the_Best_Design">reliability and validity</a> in the case of our survey, we needed to collect all possible data points/options, our users could think of. To get all the information, we proceeded by talking <strong>(qualitative research)</strong> to some students and General secretaries (Basically the stakeholders).</p><h3>Understanding of System and identifying the right problem</h3><p>Currently, a closed Facebook page existed for posting problems and announcements named as SAC IITR Discussion forum. This Facebook page was to address, discuss, and brainstorm over the issues, grievances, and ideas for the betterment of our institute.</p><blockquote>But, was the purpose actually getting fulfilled?</blockquote><p>After our conversation with stakeholders —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rGm4_ABCTKKe2aWEVWQUgg.png" /></figure><h4>Concerns from stakeholders -</h4><blockquote>High dissatisfaction among students😒</blockquote><ol><li>If the problem is approved, it gets posted, and if disapproved, the admins of the group don’t post that problem. But, they think students need to know why their problem was refused.</li><li>Another primary concern was the announcements of the senate, and other information gets hidden in the current Facebook page due to ample post/discussion shadowing them.</li></ol><p>After talking to General secretaries, we understood the structure of the current system and quite an understanding of what we could improve. But we had to listen to the concerns of the student body also.</p><h3>Making of a survey form</h3><blockquote>Hey! We are working on so n so… Plz take some time out to fill this short form.</blockquote><p>Almost every week, I come across this kind of survey from my social surroundings. And my response to nearly every survey form is the same.</p><blockquote>Reading pointless questions, Repeating the same answers, and going through irrelevant sections.</blockquote><p>The main problem here is — Survey creators often fail to build logic in their form. As the questions get irrelevant, or the flow seems to continue forever, people start to close the tab — leaving without giving any answers at all. Let’s see how we tried to tackle this problem.</p><blockquote>This survey was to understand if the students were aware of the current SAC IITR forum and the process general secretaries follow to solve their problem.</blockquote><p><strong>For making a survey form, you need to psychologically understand your user at every point of their journey as they fill your form.</strong></p><p><strong>1. </strong>Firstly, start with some warm-up questions to calm nerves and explore their interests. The idea is to help the user open up. You’re trying to create a connection so that the person doesn’t feel frustrated and leave the platform directly. Questions could be like -</p><blockquote><strong>Ques 1 :</strong> <strong>What kind of groups are you interested in/associated with </strong>(Ex. Dramatics, Design Studio etc)?</blockquote><blockquote><strong>Ques 2 :</strong> <strong>Acc. to you, what kind of problems exist in these groups?</strong></blockquote><blockquote>A. Improper recruitment process</blockquote><blockquote>B. Work culture</blockquote><blockquote>C. Political issues</blockquote><blockquote>D. Lack of infrastructure</blockquote><blockquote>E. Lack of funds</blockquote><blockquote>F. Other, please specify</blockquote><blockquote><strong>Ques 3 : How much interested are you in electing representatives</strong>(Ex. General secy for Hostel affairs, Technical affairs)?</blockquote><blockquote>Rate 1(Not Interested at all) to 5(Extremely Interested)</blockquote><p><strong>2. </strong>Although quantitative research is not as effective as qualitative research, however, it tells about “<strong>how much</strong>” or “<strong>how many,”</strong> much more accurately because of more extensive sample space.</p><blockquote>But only if you ask the correct question to correct user😌</blockquote><p>The best way to do this is to segregate users based on the behavior of the user, i.e., <strong>Active, Passively active, &amp; Passive, </strong>and dig deeper to know each of their problems. Now, we have to ask the questions which can judge the behavior, like -</p><blockquote><strong>Ques 4: Do you encounter any problem in the campus-life?*</strong></blockquote><blockquote>a. Yes. b. No</blockquote><h4>User with an answer — No</h4><p>The people who don’t encounter any problem are passive and hence least interested in filling the form. To extract information from such kind of user, you have to be precise in selecting the number and type of the questions.</p><h4>User with an answer — Yes</h4><p>The people who encounter problems could be active or passively active. These are your most targeted users who will give you maximum insights. Dig deeper and try to ask open-ended questions. The process is similar to qualitative research — “<a href="https://uxdesign.cc/how-to-conduct-user-interviews-1c06cbe8b341">How to conduct user interviews</a>.” Here you have to cover the following type of questions -</p><ol><li>How and why they use the current system.</li><li>How efficient they consider the current platform.</li><li>What problems they encounter during the process.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Dayh3re1Mr1iAiN4inipw.png" /></figure><h4>Conclusion — Insights</h4><p>We got a total of 282 responses and some very fruitful insights. Here are some major findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*x2hpau3bUiWmQeGRE6jLag.png" /></figure><ol><li>87.5% of people come under Active and Passively active Category.</li><li>But, 7.1% of people are unaware of the SAC discussion forum which is a major concern.</li><li>Most people who have problems either directly contact the respective general secretaries or discuss with their friends.</li><li>People think problems are not getting solved on the forum and many don’t want to reveal their identity — major reasons for not posting problems.</li><li>When asked “Why they think problems are not getting solved” — the major reason was -</li></ol><blockquote>“No closure is provided and even no updates”</blockquote><h4>Summing Up</h4><ol><li><strong>Most of the people fail to take into account all the probable options while they make survey forms. They forget that not every user has the same problem. </strong>For these probable options, you may need to perform some qualitative research with users and stakeholders (one-on-one interviews).</li><li><strong>The second most important weapon is “Logic.”</strong> Logic flows are the bits that wire up a form that makes sense to the users. Thereby making experience smoother for answering relevant questions and skipping over the irrelevant questions to save them time.</li></ol><blockquote>Thank you for reading! Hope you find this article useful😁</blockquote><blockquote>Currently, I am looking for full-time design opportunity. Check out my work at <a href="https://divyamangal.github.io/">Divya Mangal</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c082f2571ab5" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/dealing-with-the-loopholes-of-quantitative-research-c082f2571ab5">Dealing with the loopholes of quantitative research</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Subscription Box for Myntra — A CaseStudy]]></title>
            <link>https://medium.com/usabilitygeek/subscription-box-for-myntra-a-casestudy-615a0e8bbf89?source=rss-51c8a7fb438a------2</link>
            <guid isPermaLink="false">https://medium.com/p/615a0e8bbf89</guid>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Divya Mangal]]></dc:creator>
            <pubDate>Wed, 18 Dec 2019 07:57:23 GMT</pubDate>
            <atom:updated>2020-03-24T10:40:56.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oo0tRIafQnH1YN8PWg0-UQ.png" /></figure><h3>Subscription Box for Myntra — CaseStudy</h3><h4>What if Myntra knows how you want to dress, before you?</h4><h4>Problem statement</h4><p>A surprise box with articles curated by Myntra for clothing and accessories <strong>tailored to a consumer’s preferences,</strong> delivered in a seamless fashion with the added <strong>delight of discovering something new.</strong></p><h4>Introduction</h4><p>Myntra is one of my favorite apps mainly for two reasons “the quality” and “experience they provide from selecting to delivery”(even the returns😋). But I think it is also due to the fact that I am addicted to online shopping and so do many of my female friends.</p><p>Well, I think it will not be wrong to say that basically women have also fueled demand for better mobile apps for clothing and accessories. <strong>Only 22 percent of male respondents frequently do shopping on mobile devices compared to 40 percent of women.</strong> So, noting these facts, I have designed a subscription feature specifically for Women, which could be optimized for others later. Hence, we can roll out the product in parts.</p><h4>Why Subscription?</h4><blockquote>But before that “What is Subscription business?”🤔</blockquote><p>A subscription business is a company that sends you a package, usually once a month, of items they’ve picked out for you.</p><p>The most crucial reason for why companies are opting Subscription business is that retail tastes have changed. It’s not enough anymore just to give consumers what they’re looking for if they know what they want they can get it with a click any time. <strong>To get a consumer excited, you have to offer something they’re not expecting </strong>and subscriptions are an ideal instrument for a surprise.</p><blockquote>Now lets see why would a customer take subscription for clothes?</blockquote><p>Either the customer <strong>doesn’t want to invest time </strong>and take stress on what to wear. Which means the customer needs <strong>“convenience.”</strong></p><p>Or your customer is a <strong>“trendy”</strong> one and wants to remain updated with the latest fashion.</p><blockquote>What is trendy to one,💃🏻 may not be trendy to another?😕</blockquote><p>So the subscription plan revolves around <strong>personalization</strong> giving a pair of clothes according to the Latest trend, type of clothing they like, their body type, weather condition at their location, month, season, etc.</p><h4>Project Goals</h4><ol><li>Create <strong>a premium membership plan for premium users </strong>(because every user may not be willing to pay the initial price) which feels exclusive and classy.</li><li><strong>Customize it for the particular user</strong> and keep updating it according to the latest trend and their changing taste. <strong>(Personalization)</strong></li><li>Build a <strong>feeling of trust</strong> in the user’s mind, that they are getting a quality product and <strong>after assurance, they are paying.</strong></li><li>Making the user <strong>hooked to subscription</strong> such that they can’t deny the box of latest trendy clothes that <strong>exactly fits their body and taste.</strong></li></ol><h4>User Story</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e-aQHWpn1ebjJs-Ae1UzOQ.png" /></figure><h3>Detailed Process &amp; Screens</h3><h4>1. Entry Points</h4><p>Feeling of <strong>curiosity and excitement</strong> created which triggers the user to go and see what’s inside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdGky2sz01LI-ZnAGbtmCg.png" /></figure><h4>2. Main Page</h4><p>Giving a feel of premium subscription and building trust. Reducing complexity for the customer by providing <strong>a step-wise process</strong>. Also, on scrolling, they’ll get to know all other relevant information to better understand the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HhmiMQ0XuitYpwDET0draA.png" /></figure><h4>3. Personalization</h4><p>Profile building in order to personalize their choices. Ask question-related to-</p><ol><li>Measurement (Tell them to leave blank if they are doubtful)</li><li>Sizes they wear from different brands.</li><li>Which part they are comfortable showing off. (4th screen)</li><li>Which <a href="https://www.interaction-design.org/literature/topics/color?ep=ug0">color</a>/texture they avoid.</li><li><strong>Which fabric, brands they prefer. (Basically, Myntra’s all sorting options)</strong></li><li>Styles they prefer (This will change with the latest trend) (5th screen)</li></ol><p>Make them feel you really understand through indirect conversation. (First 3 screens)</p><p>I have also focused on the interaction of users here because this process is little time taking. There are high chances user leaves it in the middle so to avoid that-</p><ol><li>I have used <strong>a Progress bar</strong> which tells how much is left.</li><li>Radio buttons for single correct and checkboxes for “one or more”.</li><li><strong>Tinder-like swipe experience</strong> through which users can tell likes, dislikes, and super likes. (although this interaction can’t be given directly so either an <strong>onboarding </strong>or some like/dislike buttons should be given initially.)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElG1mRMEdFx9TemVW9ImYg.png" /><figcaption>Personalization</figcaption></figure><h4>4. Payment Flow</h4><p>I wanted to ease the mode of payment such that the customer pays only when he keeps a particular item. So, I explored different payment models that could provide a similar experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dnul9BW7mbkV2CR9xicbPA.png" /></figure><p>In the case of <strong>wallet for Myntra Subscription box</strong>, the amount for clothing is quite large and the customer has to <strong>recharge there wallet from time to time.</strong></p><p>If we think about<strong> Netflix like a subscription plan</strong>🤔. Then it would be inconvenient for customers as the <strong>money would get deducted before they get the service</strong>. Also, Myntra has to refund for those the clothes they return.</p><blockquote>So — —</blockquote><p>The payment plan should be such that once the customer decides “<strong>what to keep/return</strong>” payment deduct accordingly. This could be done if we link the user’s bank account.</p><p>But the only problem with that is if the customer tries <strong>any fraudulent activity </strong>after delivery of clothes then Myntra would have to bear the loss.</p><p>In order to solve this, I thought to take a refundable amount from the customer(<strong>Security money</strong>) which will be around 80–90% of box value. <strong>Assuming Myntra can bear that much loss to start this feature.</strong></p><p>You can <strong>set delivery date and time </strong>and accordingly it will come in the following months. <strong>Providing a seamless process and using Myntra’s similar interaction.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qdUhxgtHfDW48rejOX8u3w.png" /></figure><p>This interaction of date choosing is useful here because our customer usually prefers starting dates which can easily be chosen from here.</p><h4>4. After subscription and before the box arrival</h4><p>You cannot see the items of the box before arrival you only know the count of items of clothing and count of accessories. Some details can be seen when your surprise box has been packed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2eb5JB5XawtnBaknRzBhQQ.png" /><figcaption>Before packing &amp; After packing</figcaption></figure><h4>5. After box arrival</h4><p>When the box arrives app asks you “<strong>Do you want to return any item</strong>”. If the customer didn’t reply until 1-week, the money will be deducted automatically from the customer’s account. Later, providing <strong>the latest trends to select a preference for next month.</strong></p><p>Return process works like given below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-lLH2gmRoFafFWTFn6BuWQ.png" /></figure><h4>Key Points:</h4><ol><li>The <a href="https://www.interaction-design.org/literature/topics/user-needs?ep=ug0">user needs</a> to pay only for what they keep and return the rest.</li><li>Cancel membership anytime, and you will get a refund. (Security money)</li><li>I haven’t included <strong>trial kind of version </strong>(although I know people want to try something to feel comfortable to product) but here, the normal audience knows about the quality of Myntra means <strong>no quality check needed</strong>. Secondly, the amount taken is refundable which basically forces the customer to try this.</li><li>I haven’t included for someone else because this is customized for that particular person and according to her <strong>taste, wishlist, previous searches, selected trends. </strong>If we include for someone then there are a lot of problems and wishlist and recent searches can’t be taken into consideration.</li></ol><h4>Prototype</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*rAvI51QzWG6e2kVATeEZ9w.gif" /></figure><h4>Edge Cases</h4><ol><li><strong>Customer who is leaving the Platform- </strong>Suppose a customer is moving to a new place and decides to cancel the subscription. First of all, <strong>ask them why they want to cancel.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LedNACVLJbFOrICEcXbDKA.png" /></figure><p><strong>Give a solution to their problems.</strong> Example: If the person is leaving town tell to change shipping address instead of canceling the subscription. Try to retain the customer.</p><p>If then also they leave,<strong> later tell them what they are missing</strong>. Like, today your surprise gift got this for you. This could be yours if you were still subscribed. This will make them <strong>jealous and trigger</strong> them to subscribe again.</p><p><strong>3. If a person wants to make customize subscription plan because he has more budget</strong> — (Assume more than 8000)</p><p>I haven’t given an option for increasing the <strong>frequency of the box </strong>as I think this would increase operation cost for Myntra for extra for delivery and returns. Instead, I have given options to increase the number of items per box. An extra feature can be provided which asks the user for their budget. If she has a budget greater than Rs8000 she can have a customized plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDRk20BXE6zn7RUXcAR77Q.png" /></figure><p>4. In case the customer doesn’t know the exact measurements of their body. We can make the question optional for them and later in the first subscription box we can provide a measuring tape.</p><blockquote>This can be unique selling point.🤩</blockquote><p>But, for the first package, we can ask them the brand and size they wear.</p><h4>Summing up</h4><p>No matter how many systems exist, there is a way to make yours stand out from the crowd. User experience as your user wants, quality product, easy interaction and pleasant <a href="https://www.interaction-design.org/literature/topics/ui-design?ep=ug0">UI design</a> can be an effective way to engage the user.</p><blockquote>Thank you for reading my case study. Feedback and suggestions are welcomed!</blockquote><blockquote>+1 Clap, +2 Claps, +50 Claps!👏🏻</blockquote><h3>Want to learn more?</h3><p>Want to get an industry-recognized Course Certificate in UX Design, Design Thinking, UI Design, or another related design topic? <a href="https://www.interaction-design.org/courses/?ep=ug0">Online UX course</a>s from the Interaction Design Foundation can provide you with industry-relevant skills to advance your UX career. For example, <a href="https://www.interaction-design.org/courses/design-thinking-the-beginner-s-guide?ep=ug0">Design Thinking</a>, <a href="https://www.interaction-design.org/courses/become-a-ux-designer-from-scratch?ep=ug0">Become a UX Designer from Scratch</a>, <a href="https://www.interaction-design.org/courses/conducting-usability-testing?ep=ug0">Conducting Usability Testing</a> or <a href="https://www.interaction-design.org/courses/user-research-methods-and-best-practices?ep=ug0">User Research — Methods and Best Practices</a> are some of the most popular courses. Good luck on your learning journey!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=615a0e8bbf89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/usabilitygeek/subscription-box-for-myntra-a-casestudy-615a0e8bbf89">Subscription Box for Myntra — A CaseStudy</a> was originally published in <a href="https://medium.com/usabilitygeek">UsabilityGeek</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Conduct User Interviews]]></title>
            <link>https://uxdesign.cc/how-to-conduct-user-interviews-1c06cbe8b341?source=rss-51c8a7fb438a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c06cbe8b341</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Divya Mangal]]></dc:creator>
            <pubDate>Wed, 16 Oct 2019 09:42:03 GMT</pubDate>
            <atom:updated>2019-10-25T12:57:55.927Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to conduct user interviews</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmGC7yy_9xPK1KLJFNROow.png" /></figure><blockquote>I am not an expert on “how to perform User Interviews,” but surely by this time, I have experienced a handful of interviews on varied topics. I am eager to share my knowledge which I have gained from my internship experiences at Ola while working with some great people.</blockquote><p>User interviews are not just another design process; it is about making your design more user-approved. It’s a big and important step that leads and helps you validate the problems. It basically fills the gap between the things you already know and the truth. Additionally, it will help you discover the things about your product that you weren’t even looking for or weren’t even aware of.</p><h4>How Spotify discovered its users&#39; confusion with “ads skip limit”? How Netflix identified the different needs of its customers at a different hour of the day?</h4><p>User interviews were a major step in their journey through which they identified the real problem. So, before starting the design process, it is better to validate the problem.</p><blockquote>“A brilliant solution to the wrong problem can be worse than no solution at all: solve the correct problem.”<strong><br>― Donald A. Norman, The Design of Everyday Things</strong></blockquote><h3>Understanding your user</h3><p>User interview is a way to dive into the life experiences of different users. I think psychology plays a massive role in understanding people. Above the basic needs of your user comes psychological needs that initiate a desire to collaborate, compete, create, and destroy. <strong>To understand the psychological needs of a user, observation is an essential key element.</strong></p><h3>Don’t ask the user directly what they want</h3><p>Generally, users are unaware of what they want or what you are trying to change for them. So, it’s normal if they are unable to tell the problems with the product. In these cases, you need to analyze their situation and find their problems.</p><p>Remember, here, asking direct questions would not help you much.</p><p>In that case, <strong>you need to reframe the questions and depict the situation through which they can relate. You may need to ask them from multiple angles by relating them with different sections of your script.</strong></p><blockquote><strong>Example:</strong></blockquote><blockquote><strong>In IIT Roorkee there is a platform that is developed to post announcements and problems related to the student body and SAC(Student Affairs Council) body. We conducted a survey to know the shortcomings of this platform in order to ease the experience on both sides.</strong></blockquote><blockquote><strong>Instead of asking : “</strong>How can we improve your experience?”</blockquote><blockquote><strong>Ask them :</strong> Do you encounter any problem before posting, while posting or after posting any issue? Are they getting solved? Whom do you contact? How do you contact them?</blockquote><h3>Build a Meaningful questionnaire set</h3><p>Asking just generic stuff wouldn’t lead you anywhere. As people who know similar products would interfere with your process by suggesting features while others who are normal audiences will not be able to detect their problems.</p><p>Before going on a user interview, you must spend enough time to build the questions. Also, be prepared with further conversation in the same context. A<strong>fter each question, ask yourself what can a user possibly answer, and how would their response adds value to your research project. </strong>There is a methodological way to set questions.</p><p>1. First, before starting the actual interview, give an introduction as to why are you here for, what you want from them, what are you going to do with that.</p><p>2. Then, ask about the general demographics and try to build a user persona out of it. Like asking age, education, gender, experience.</p><blockquote>Like in the above example we tried to separate the users by asking:</blockquote><blockquote><strong>Current Year of students and campus groups students are involved in.</strong></blockquote><blockquote><strong>Their interest in electing a correct representative.</strong></blockquote><p>3. Now don’t jump on the topic directly, first try to build conversational questions like: do you know about the product, how do you use it, how often, etc.</p><p>4. Somewhere around here, you would be in a position to tell how serious the interviewee is and how much you need to rephrase and explain to him.</p><p>5. Now dig deeper into your problem and start being specific to the problem. Try to ask Open-ended questions with no or slight probing.</p><h3>Try to ask Open-ended Questions.</h3><p>Forget the information you have before asking the question, try to be as new as possible. The person would make you walk the path that he takes whenever he uses your product.</p><p>Avoid using yes/no questions. Any vague language should be avoided as it would only create confusion in the user’s mind.</p><blockquote><strong>Example:</strong></blockquote><blockquote><strong>Instead of asking : </strong>Do you feel ignored if the problem you posted doesn’t have enough response?</blockquote><blockquote><strong>Reframe as : </strong>How do you feel when the problem you posted didn’t have enough responses?</blockquote><p><strong>Asking open-ended questions would result in expansive responses.</strong> Try not to interrupt in between unless they are going too much off the topic.</p><p>Probing is always harmful to the interview and may affect the answers of the user. However, sometimes, you may have to probe to draw the user back on track.</p><h3>Remember to dig deeper</h3><p>Every question has at least five<strong> “why possibilities”</strong> to go deeper. Keep repeating “why” five times until you understand the nature of the problem and solution to that problem.</p><blockquote><strong>Example:</strong></blockquote><blockquote>How do students generally contact you if they have any problem regarding campus groups.</blockquote><blockquote><strong>— They try to contact me personally.</strong></blockquote><blockquote><strong>Dig Deeper</strong> : Why do they contact you personally instead of posting on the complaint portal.</blockquote><h3>Closure</h3><p>After completing your interview, give a sense of closure to your user. Your abrupt ending may make them feel ignored. Don’t forget to ask them if they want to ask or add something to the discussion.</p><p>And, finally, thank them for their time and contribution to your research. Thereafter, comes research analysis and further documentation. It is necessary as you would give meaningful insights for your product.</p><blockquote>I had a great experience at Ola while working with <a href="https://medium.com/u/70a4442723a9">Kavya</a> and <a href="https://medium.com/u/d00f303b6829">Deepak Jose</a>. The exposure to the field and interviewing Ola partners was indeed a challenge. As all drivers are not well educated and hence mostly unable to tell their problems &amp; needs. For such type of audience, observation is the key.</blockquote><p>Thank You for reading. All types of suggestions are welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c06cbe8b341" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-conduct-user-interviews-1c06cbe8b341">How to Conduct User Interviews</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>