<?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[Design Studio, IIT Roorkee - Medium]]></title>
        <description><![CDATA[We are budding researchers, designers, engineers and architects at IITR working together to combine art, science and technology to create better experiences - Medium]]></description>
        <link>https://medium.com/design-studio-iit-roorkee?source=rss----70fe26422ce---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Design Studio, IIT Roorkee - Medium</title>
            <link>https://medium.com/design-studio-iit-roorkee?source=rss----70fe26422ce---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:56:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/design-studio-iit-roorkee" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A hands-free cooking assistant?]]></title>
            <link>https://medium.com/design-studio-iit-roorkee/a-hands-free-cooking-assistant-daa2fec255d?source=rss----70fe26422ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/daa2fec255d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Utkarsh Gill]]></dc:creator>
            <pubDate>Sat, 22 Feb 2020 10:21:16 GMT</pubDate>
            <atom:updated>2020-02-22T10:21:15.971Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>My mom loves to learn and cook new dishes. She has a good hand over a variety of recipes. “Where did you learn these?”, I asked knowing she never went to a cooking class. She handed me over that old yellow-paged, coverless book. “Mother gave it to me”, she said. “But why read such long texts when you can find these on the internet?”, I asked. “Why to complicate things when I can simply read it?”, she replied.</blockquote><p>Now, my mom is not tech-savvy and she isn’t comfortable with anything that requires more than 3 taps. ‘Complicated’ she calls it and her experience with cooking by following youtube recipes has often resulted in anything but that recipe. Often she didn’t have the exact ingredients and assuming ingredients resulted in something different than what she expected.</p><p>So why this cooking-experience talk suddenly? It all started with a design sprint at <a href="https://medium.com/u/90c6beaa8105">Design Studio</a> IIT Roorkee. Let’s begin.</p><h3><strong>The Design Sprint</strong></h3><p>Design Studio is a group of self-learning designers at IIT Roorkee. I was one of the new recruits of this group and was recently introduced to the world of UI/UX. So after learning the basic UX design process, it was time for our first design sprint.</p><p>These were some broad ideas given to us:</p><ol><li>Car parking</li><li>Musicians hub</li><li>Canteen order</li><li>Truck loader</li><li>Police alert</li><li>Cooking assistant</li></ol><p>Each one of us had to choose any one of the above and research further to decide a reasonable problem statement. I went for the cooking assistant solely for my love of cooking (Yes! I can cook xD).</p><h3><strong>The search for the problem statement</strong></h3><p>What was the need for a cooking assistant? What problem could it solve that the present apps/services/products couldn’t solve? But wait! What exactly were the problems faced while cooking/learning-to-cook?</p><p>It was time to talk to someone who cooks regularly.</p><h3><strong>User Analysis</strong></h3><p>A person who cooks regularly and has tried learning online — My mom, the first person who came to my mind. It was time for a telephonic interview (I live in a hostel at IIT, away from my mom).</p><p>I questioned every aspect of cooking from cooking-time to ingredient-availability. I asked questions like “How many times a week do you try cooking something new?”, “What would you prefer a video tutorial or a textual recipe?” and jotted down every keyword she spoke. I enquired about the pain points while cooking and while using the app. I also asked her about what features would she want if I could make an app/service to assist her with cooking.</p><p>After I had an apt amount of data, I thought maybe interviewing one user wasn’ t enough. So the next person was my friend’s mother. She was a more geeky homemaker and was way more comfortable with handling technology. She had quite contrasting answers on certain questions which made my user analysis more practical.</p><p>After getting the raw data, it was time to arrange and cluster it.</p><h3><strong>Affinity clustering</strong></h3><p>In simple words, affinity clustering is basically segregating the data in meaningful groups. After collecting the data I divided it into 3 groups — user goals, pain points and requested features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JfBSLAu7MDrZOr5xJ1Pdw.png" /><figcaption>Raw data sorted into meaningful clusters (yup, that&#39;s a door! xD)</figcaption></figure><p>Affinity clustering makes it easier to interpret data and helps in the formation of information architecture. Here are the clusters:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2N2Bfkv-L-oH0ok99qTJYg.png" /><figcaption>Clustering makes it easier to visualize the collected data and the problem</figcaption></figure><p>These clusters and the data are cumulatively extracted from the interviews conducted with the two users.</p><p>Now, I finally had a problem statement to work upon:</p><p><em>“Indian housewives generally find cooking with video tutorials/recipe books cumbersome and inefficient. Design a plausible solution to this problem.”</em></p><p>The next step was to look at existing apps/services.</p><h3><strong>Competitive analysis</strong></h3><p>I explored the most popular cooking apps and services available and listed down their features. Then I compared those I thought were really important ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRu-kWu-I1UmF5B0ZDnemA.png" /><figcaption>These included voice assistants and the most popular cooking apps on the Google Play Store</figcaption></figure><p>On analyzing these apps/services, I came to the conclusion that only Alexa is close to solving the problem, but it has database limitations, language issues and affordability in a general Indian household. Hence, there is a need for an efficient product, which solves most of the problems while being within Indian household constraints.</p><p>I felt one of the benefits of competitive analysis was that it gives you a take-off thrust at the problem by giving you already existing features that have been solving individual pain points related to the problem.</p><h3><strong>Feature ideation</strong></h3><p>The next step was to ideate features for the app, based on the clustering which could solve these problems.</p><p>As we were allowed to make reasonable assumptions for the stakeholders, I assumed a company which has all requisites like a chef, cameraman, and people to direct and program recipes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*lHnUegVQonLBD0RSUcQ1oA.png" /><figcaption>Features ideated for the app, some of them inspired the existing apps</figcaption></figure><p>Following the <strong>diamond approach</strong>, after thinking about all possible features, I filtered a bunch of them to deliver an <strong>MVP (Minimal Viable Product)</strong>. In simple terms, the diamond approach refers to successive divergent and convergent thinking i.e. thinking all possibilities then filtering them based on the constraints. Hence these the finalized features were:</p><ol><li>Image-based steps</li><li>Voice control</li><li>Alternate ingredients in the list wherever possible</li><li>Phone backlight override</li><li>Categorization of recipes</li><li>Share recipes</li><li>Export ingredients</li><li>Tags-based search feature</li><li>Servings calculator</li><li>Timer for certain steps</li><li>Language options</li><li>Measurement system toggle</li></ol><p>The next step was to use these features to create information architecture.</p><h3>Information Architecture</h3><p>Information architecture is all about the organization of information in a clear and logical way. Such an organization follows a clear purpose — helping users navigate complex sets of information. It’s analogous to the arrangement of books in a library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGHmWIII8qbVDDpPb-CnVA.png" /><figcaption>Information architecture helps a user navigate through a nexus of information.</figcaption></figure><p>Information architecture helps the user in creating <strong>mental models</strong> which helps the user use a product efficiently. Mental models are the imaginary working models created by the user’s brain on introduction to a novel object. These are made using information from past experiences and consist of <strong>mappings</strong> i.e. the link between a feature/control and its use/effect.</p><p>Now it was time to think of possible use cases.</p><h3>Use cases &amp; user flows</h3><p>Use cases as the name suggests are the possible causes for which an app/website can be used whereas user flows are the possible routes a person can take through the app/website for the corresponding use case.</p><p>So I found 2 major possible use cases:</p><ol><li>Exploring recipes</li><li>Cooking</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NYYXMUKDBsD28RTXXJE6JQ.png" /></figure><p>The save feature can be considered as a sub-case amidst other major use cases.</p><p>I haven’t worked upon edge cases because they are majorly based upon constraints and I assumed the constraints, stakeholders, etc.</p><h3>Wireframes</h3><p>Time for some scribbling and scratching! Wireframes are the first step towards visually representing the solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-mARkTzjzKr7V9tncaHwuA.png" /><figcaption>Landing page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DNz0DhrkjAScqTtcR4LQuQ.png" /><figcaption>Recipe page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CxVaDfi9ZF6NvNIi5c7E6Q.png" /><figcaption>Cooking Interface</figcaption></figure><p>One noteworthy point is — Wireframes need not contain fancy UI, they can but it’s not necessary. It should just reflect the skeleton of the UI.</p><h3>Branding and UI styling</h3><p>Branding is the product’s visual identity, hence it must be done such that it is quite unique and compatible with the product’s emotion.</p><p>I felt yellow (#FFC107) is dominating color in the Indian main course so I chose it as the primary with charcoal black (#3C3C3C) as the secondary color and light grey (#A4A4A4) for tertiary uses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BYNz2JoAuqEZR650KZuc1g.png" /></figure><h3>UI design</h3><p>“Users often perceive aesthetically pleasing design as design that’s more usable”. This is known as the <strong>Aesthetic Usability Effect</strong>. I guess we’ve all experienced it while using a not-so-good-looking product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5Vb6nBqimTl5zNc-lxbsQ.png" /></figure><p>I designed the UI keeping in mind the basic UX laws and have tried to use them wherever possible. UX laws are psychology and design based laws, each one developed and researched by different scientists from varied fields like cognitive science, human-behavior studies and have proven quite functional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mow9TiPayeg72U5caLYF3Q.png" /></figure><p>The navigation bar, for example, is designed according to the <strong>Fitt’s Law </strong>which states, “The time to acquire a target is a function of the distance to and size of the target”. Thumb is the most active part of the human hand while using a phone and the navigation bar lies quite close to the thumb, thus making it easily tappable.</p><p>The navigations button are arranged according to the <strong>Serial Position Effect</strong> which states, “Users have a propensity to best remember the first and last items in a series”. Thus the two most important buttons i.e. Home and Settings are at the ends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8JaIcvVzHMVk663qKRwKQ.png" /></figure><p>The navigation interface at the landing page features a close resemblance with Instagram’s navigation. This further ensures that most of the users would be comfortable as they will be familiar with the interface. This is further supported by <strong>Jakob’s Law </strong>which states, “Use of familiar patterns in design facilitates user experiences”. Although I’m not in complete support with the law as it hinders originality and creativity to some extent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s69_OHNJ873SHEB2yz0utw.png" /></figure><p>The cooking interface is voice-controlled, the users can say basic commands like:</p><ol><li>Stop — to pause/stop the recipe</li><li>Repeat — to repeat the step</li><li>Go — to continue with the recipe</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNdQAEIl5MJ1fhbg7kFIsw.png" /></figure><p>Users can use buttons to navigate through the recipe steps. They are given textual as well as audio instructions with images. They can end the recipe at any time by tapping the cross. The bottom bar shows the progress of the recipe.</p><p>There is a timer for certain steps that need time-dependent execution. The backlight is overridden so it doesn’t turn off while cooking.</p><p>Eureka! Here we have a possible solution to the problem statement, which is a hands-free cooking assistant cum recipe app — <strong>Kookerr. </strong>Why this strange name? Well, the pressure cooker is one of the most used cooking utensils in India, and in Indian slang, it is often spoken as ‘kookerr’.</p><h3><strong>Conclusion</strong></h3><p>Design sprints are fun! and a great way of application-based learning, especially for self-taught designers. While working on this app I interacted with a lot of senior designers &amp; colleagues, read quite a lot of blogs and articles and practiced the complete design process. I wouldn’t have been writing all of this if I had not documented my whole research, that’s how I know the importance of documentation.</p><p>This was my first UI/UX project. Although it was not an ideal one, owing to the liberty of choosing the problem statement and setting up the constraints according to my comfort, it did teach me basic design principles, working according to deadlines and brainstorming (this being my first article, it also taught me writing xD).</p><p>Thanks for reading this far. Suggestions welcomed :)</p><p><em>Practice good design, use a concept.</em></p><p>Peace.</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYxBP_WV7LI6zc-zdUkNqQ.png" /></a></figure><p>📝 Read this story later in <a href="https://blog.usejournal.com/r/?url=https%3A%2F%2Fusejournal.com%2F%3Futm_source%3Dmedium.com%26utm_medium%3Dnoteworthy_blog%26utm_campaign%3Dtech%26utm_content%3Dguest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://blog.usejournal.com/r/?url=https%3A%2F%2Fusejournal.com%2Fnewsletter%2Fnoteworthy-in-tech%2F%3Futm_source%3Dmedium.com%26utm_medium%3Dnoteworthy_blog%26utm_campaign%3Dtech%26utm_content%3Dguest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daa2fec255d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-studio-iit-roorkee/a-hands-free-cooking-assistant-daa2fec255d">A hands-free cooking assistant?</a> was originally published in <a href="https://medium.com/design-studio-iit-roorkee">Design Studio, IIT Roorkee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 24hr UX Challenge]]></title>
            <link>https://medium.com/design-studio-iit-roorkee/the-24hr-ux-challenge-91961a5cb388?source=rss----70fe26422ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/91961a5cb388</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Rakshit Keswani]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 18:06:40 GMT</pubDate>
            <atom:updated>2019-06-24T18:06:39.931Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Designing chat experience</em></p><p>I took up an assignment by a medical website to design a chat experience between a female patient and a male nutritionist where the patient wants to lose body weight and acquire a good physique.</p><p>The Challenges here were:-</p><ol><li>How the patient will explain her situation.</li><li>How the payment will happen for the consultation.</li><li>How the nutritionist will answer and share the diet plan.</li><li>How the patient will follow nutritionist’s instruction and share updates.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*FbP2JWcXohpdFhjn9vcv5g.png" /></figure><h4>The Timeline</h4><p><strong>Saturday (evening)</strong>- Understanding the problem statement and Initial research, followed by ideation and sketching out initial concepts.</p><p><strong>Sunday (Morning)</strong>- Finalizing the ideas and sketching wireframes</p><p><strong>Sunday (Afternoon)</strong>- Prototyping some screens and documenting the work</p><p>To get the Idea clear I started by building a story. I wove a hypothetical story for understanding the problems of the user and tackle the problem better and in a more user-centric way.</p><h4>User Story</h4><p>Aysha is a 19-year-old girl and is concerned about her increasing weight, she is looking for a quick solution for her problem and comes to know about the app. She goes on the app enters symptoms and selects the specialty of doctor she wants treatment from. Aysha is a bit shy and doesn’t open up easily to a stranger.</p><h4>Secondary Research</h4><p>I started by looking experiences of different apps like 1mg, DocApp, Ada that provided similar experience and tried to figure out how users were interacting in each case, I also tried to figure out different payment methods they adopted in their app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oDm6yOS8Islb2mJ-hQMQnQ.png" /></figure><p>Thus after I learnt and understood about the problem, I started to work on tackling the problem.</p><p><strong>Mapping</strong>:- I started to draw a Map, I listed the customers (doctor &amp; Aysha) on the left side and my objectives on the right side and tried to complete the flowchart in between by showing how Aysha will interact with the app.</p><p><strong>HMW</strong>:- I wrote HMW notes (How Might We Notes), These allow me to write one Idea per sticky note so that I can make a stack of all the problems related to Aysha.</p><p><strong>Clustering</strong>:- I organized my HMW notes to different categories of problems. I placed similar Ideas next to one another and Labelled them as they emerged.</p><p><strong>Picking Ideas</strong>:- I picked the set of Ideas that I thought were appropriate and were possible to prototype with the limited time I had.</p><p><strong>Sketching:-</strong> After my decision making was over I took to the step of sketching. In the first 20 min, I wrote down all the things I had to keep in mind and in the next 20 min I jot down all the Ideas I had.</p><p><strong>Crazy 8</strong>:- It’s the method I prefer to get as many as Ideas possible in just 8 Minutes. It allows me to explore all options and get to a solution sketch which I otherwise would have missed out.</p><p>Thus after my Ideas were clear I started making wireframes of my final ideas so that took it to sketch to make some UI.</p><h4>The Golden Path</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqIm6cVM7KXGgSeffkPqlQ.png" /></figure><p>The experience of how nutritionists will answer and share diet plans and how the patient will follow nutritionist’s instructions had to be defined. Thus I started thinking it piecewise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tj5FRglBwv2uMYaBMex1eA.png" /></figure><p><strong>Wireframes</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li6uIKU5Dz_ZZ1xKDWoO0A.png" /></figure><p><strong>Prototyping</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VfufLfdt3SrRJXdEeshWhg.png" /></figure><p><strong>Conclusion</strong></p><p>In this assignment, I learnt about how to make decisions quickly and understand how to search and think of solutions under time constraints. Still, there will always be a scope of improvement in my work and I will definitely love to work on similar projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91961a5cb388" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-studio-iit-roorkee/the-24hr-ux-challenge-91961a5cb388">The 24hr UX Challenge</a> was originally published in <a href="https://medium.com/design-studio-iit-roorkee">Design Studio, IIT Roorkee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tinder — Ice Breaking]]></title>
            <link>https://medium.com/design-studio-iit-roorkee/tinder-ice-breaking-5be604bebd57?source=rss----70fe26422ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/5be604bebd57</guid>
            <category><![CDATA[date]]></category>
            <category><![CDATA[social]]></category>
            <category><![CDATA[dating-app]]></category>
            <category><![CDATA[icebreaking]]></category>
            <category><![CDATA[tinder]]></category>
            <dc:creator><![CDATA[Prasannadeep Das]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 18:00:00 GMT</pubDate>
            <atom:updated>2019-06-24T18:00:00.324Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Tinder — Ice Breaking</strong></h3><p>Ice-breaking on dating apps like Tinder involve initial impression or outside appeal. Introduction of one such feature might help to increase the conversion rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lMLBtl0CP20orL5-2Iz9-g.png" /></figure><p><strong>Challenge</strong></p><p>Ice-breaking on dating apps like Tinder involve initial impression or outside appeal. This may not be in favour of some users and may lead to unnatural conversations. Lack of topics or common interests of the matched individuals may result in less fruitful conversations.</p><p><strong>Abstract</strong></p><p>Tinder is a location-based social search mobile app, generally used as a dating app, that allows users to like (swipe right) or dislike (swipe left) other users, and allows users to chat if both parties liked each other in the app (a “match”). This match-matching process, was what I and a senior of mine, Nikhil Goyal, a business analyst thought of working upon. We found that in India, Tinder having a male dominant user base, the chances of a getting a match was quite low. Plus the factor that guys generally swipe right almost every other girl that turns up in their list, whereas the other way round, girls are generally quite choosy. Thus keeping all these factors in mind we proceeded and came up with 3 solutions and finally narrowed down to one!</p><p><strong>Why Is This A Problem?</strong></p><ul><li>Users on Tinder focus on photos and their attractiveness. A study suggests that females consider 80% of males as below average(median) on the attractiveness scale and only 20% above average. This leads to a high competition in the lower 80% owing to less number of matches.</li><li>Being a chat-based platform a lot of Male users. rely on cheesy pick-up lines and ‘funny’ one-liners as a means of attracting women due to lack of information about common topics. This may result in awkward silences or unnatural chats.</li><li>Users with an abundance of matches (typically, women), tend to be picky in their quest to start up a conversation. Since a male user might fail to start up an interesting conversation, this selection might be based on materialistic factors, such as outright semblance of the said match.</li><li>This ends up only a few attractive men talking to a large number of girls based on their first messages and/or their ‘appealing looks’, leading to dissatisfaction for both male users as well as female users.</li></ul><p><strong>Initial Validation</strong></p><p>Considering all the problems we shortlisted, we thought to have a real-life validation, thus created a single question-based form, targeting the male janta. The question asked was:</p><p><em>“Does ice breaking ( how to start a conversation ) on Tinder makes you think a lot?”</em></p><p>To which, we got 127 responses. The result is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*9aGPnqpdmrT7xH9_rsbgzQ.png" /></figure><p><strong>Approach</strong></p><p>While going through some research papers on dating apps, I got to know that about 50% of the conversations go un-replied. There was another interesting fact that I came across, guys are 5 times more likely to start the conversation than girls. So that’s where we decided that let’s construct something that’s going to aid the guys in starting the conversation, with girls “indirectly” helping them to spark it off.</p><p>The best way to do this was to get data from the girls about what their interests are, what are the topics they like conversing and also through these questions we could get to know about their comfortability. To check the consent we later did another survey in which we asked the female janta a simple question:</p><p><em>“Would you be comfortable sharing a little more information about yourself ( taste in travel, food, etc. ) which may lead to meaningful first messages from the guys?”</em></p><p>To which 47 girls responded. The results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*9L-vci_OQNKgQV7bd1ciDw.png" /><figcaption>81.8% Voted Yes, 18.2% Voted No</figcaption></figure><p>Getting a positive response from the female user base, we sought to take this idea ahead and finally ended up with 3 solutions. During the whole process, we also talked to guys as well as girls individually trying to understand the problem even better and iterating as we proceeded.</p><p><strong>Solution 1</strong></p><p>It has been observed that people with similar interests tend to enjoy a better conversation thus feeling more comfortable. Thus keeping this in mind we sought to find a solution through which people could get to know about the interests of their match and would initiate the conversation.</p><p>Taking reference from music-based apps we thought to provide the users with a set of questions while logging in to get to know about their tastes better. Users will be prompted to select tags of various interest/likes for various criteria. These “Interest tags” would then be displayed on the screen of the user matched with, thus providing topics to start the conversation with.</p><p><strong>Limitations:</strong></p><ul><li>The sign-up procedure becomes lengthy and tiresome.</li><li>The match may not share interests or may share interests which the other person hates.</li><li>People might fake their interests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*O6rOhc-tdi1Ka9vOEP_G3g.png" /></figure><p><strong>Solution 2</strong></p><p>While working on the solutions, we did a few one-on-one discussions with friends living in cities such as Mumbai, Hyderabad &amp; Bengaluru, from where we get to know that girls there generally get 10–12 matches weekly, sometimes the count even reaches 18–20. So comparing guys and choosing whom to talk with becomes a real issue. And they sometimes even end up talking to guys who’re attractive enough but don’t talk sense.</p><p>Thus to tackle this, we thought to stitch a solution where the user, male or female gets a question card as soon as they’re matched. To help initiate the conversation, women will be provided with an option to ask a set of a suggested questionnaire with a newly matched user. The questionnaire would ask for an expressive answer from the user, thus initiating the conversation anyhow!</p><p>Plus, this enables female users to sort males based on their responses before the actual chat begins. This serves as an ice-breaking tool as women initiate the conversation.</p><p><strong>Limitations:</strong></p><ul><li>Based on the number of matches per day, women will have to go through numerous descriptive answers which will be tedious.</li><li>Despite the descriptive feature, the decision to initiate conversation still lies with female users and it is very likely that the ice breaking may not happen, leading to a lower success rate.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*WyEofAJFUM4--v7r-5-LhQ.png" /></figure><p><strong>Solution 3</strong></p><p>The last and the most satisfactory solution that we came up with was a mix of gamification and card based interaction, which Tinder is already well known for. We thought to present information about female users to their male counterparts through an interactive quiz feature.</p><p>A Female user would be asked to provide data inputs regarding the quiz questions about themselves. Male users will be asked to guess answers to these questions once matched. These questions would have only two choices as answers, hence brief. Each response by a male user would prompt him as correct or incorrect. This would enable male users to know more about the female user and thus may help in ice-breaking.</p><p><strong>Limitations:</strong></p><ul><li>It is an additional step, thus the conversion rate might be low.</li><li>Question set might become redundant for the male users if the same question comes up for multiple matches.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Zx-mJpgjzVNMSHBUGz_1rA.png" /></figure><p><strong>Comparison &amp; Conclusion</strong></p><p>Keeping the very first rule of UX of maintaining the flow of the app we’re planning to tweak and comparing the three solutions on the basis of Feasibility, Simplified feature, Resource requires and the consistency of the UI, we came up with the decision that Solution 3 would practically be the best way to incorporate ice-breaking in dating apps such as Tinder.</p><p>The effect of the introduction of our ice breaker feature will be directly on the users, aiming to improve the user experience of the app as a whole. To verify our selection of the solution, we did a few quick user testing through a prototype and 8 out of 10 found it useful and a worthy addition to the existing application.</p><p>Thank You!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5be604bebd57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-studio-iit-roorkee/tinder-ice-breaking-5be604bebd57">Tinder — Ice Breaking</a> was originally published in <a href="https://medium.com/design-studio-iit-roorkee">Design Studio, IIT Roorkee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning WhatsApp]]></title>
            <link>https://medium.com/design-studio-iit-roorkee/redesigning-whatsapp-8e4b84a02644?source=rss----70fe26422ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e4b84a02644</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Komal Maheshwari]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 20:04:33 GMT</pubDate>
            <atom:updated>2020-04-19T14:46:07.394Z</atom:updated>
            <content:encoded><![CDATA[<h4>I learned to blame the app. Instead of taking an app to be written in stone, I started prioritizing the user. That changed everything.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVgiyfLDytVMRetujsXPSw.png" /></figure><h3>Background Story</h3><p>Summer, 2018</p><p>I’d just finished my first year at IIT Roorkee and was looking to give a shot at something new during the break… while randomly chatting with a fifth-year senior, I asked her what her field of professional interest was. She told me that she was a UX designer. This new term piqued my curiosity and I relentlessly started asking her questions. After patiently answering the first few of my questions, this is what she told me:</p><blockquote>‘Try redesigning an app of your choice. Preferrably, an app that you use regularly. Just list down things which you believe might be problematic and try to find an alternate solution. It’ll give you a better introduction to the field than I ever can.’</blockquote><p>I chose <strong>WhatsApp</strong>.</p><p>This blog post seeks to document my journey of the same.</p><p>Before I begin, I want my readers to know that <strong>I’d started out as an absolute beginner</strong>. I learned most of the things I needed to (including relevant software) by reading on the internet and talking to people along the way.</p><p>This was my dive into the pool without a tube. And I learned that there is no better way to learn how to stay afloat than thrashing your arms in every possible direction as you gasp for air.</p><p>Happy reading 😊</p><h3><strong>Getting Started</strong></h3><p>I got started by thoroughly familiarising myself with the app, inside and out. I also read up about it on the web in a bid to understand what makes it tick (This blog by Charles Deets was very helpful:<a href="https://medium.com/facebook-design/one-year-designing-at-whatsapp-c20b4c46bae6"> <strong>One Year Designing at WhatsApp</strong></a>)</p><p>I refrained from searching for potential flaws in the app on purpose, it was something I wanted to figure out on my own.</p><p>Here’s what I gathered:</p><ul><li>WhatsApp is delightfully<strong> simple </strong>to use</li><li>WhatsApp avoids using unnecessary features and that is what makes it so special. Almost anyone can use it. No special skills or education levels needed</li><li>Whenever Whatsapp introduces a new feature, the app doesn’t prompt the user about it. The WhatsApp team designs features which are obviously useful and are extremely intuitive to use. This enables the users to discover them on their own. As Deets writes very crisply in his blog: <strong>“if the feature needs explanation, it&#39;s not ready”</strong>. This basic intuitiveness, I realised, was the core principle that WhatsApp, as a product, stood on.</li></ul><p>This exercise of reading up on the app design and exploring the app on my own helped me understand that <strong>simplicity, utility </strong>and<strong> intuitiveness</strong> were the principles that united the different features of the app and if I wanted to introduce any new changes, I’d have to make sure that they adhered to these basic principles else they wouldn’t be consistent with the rest of the app.</p><h3><strong>Gathering perspectives.</strong></h3><p>Now, I tried listing down things that bothered me… I realised that even though I felt slightly uncomfortable in certain places, it was difficult to verbalize exactly why. That’s when I decided to ask other users.</p><p>I asked a bunch of friends about what annoyed them most as a WhatsApp user. Here is one input I found extremely relevant:</p><blockquote><strong>“Video and voice call buttons are way too easily accessible…I always end up calling people accidentally… It&#39;s embarrassing. Wish it wasn’t this easy to make a call.</strong></blockquote><blockquote><strong>Also, the fact that there’s no way to put a chat completely out of sight apart from blocking the person, kinda irks me. I wish there was a more diplomatic way out so that the messages could reach me but I would not have to know about them unless I actively sought to. That would be the best of both worlds.”</strong></blockquote><blockquote>-Manan Jain, 3rd Year student, IIT Roorkee, avid coder, a friend of the author.</blockquote><p><strong>This was my moment of enlightenment.</strong></p><p>So far I’d simply been a user… there were things that irked me and made me uncomfortable but to me, that was just how it was and I was supposed to deal with it. It had never occurred to me that that there could, in fact, be another way. That by simply repositioning the buttons a little and tweaking the features a bit, I could, in fact, change how users used the app and how it made them feel.</p><p>I realised that the reason behind an accidental WhatsApp call was not always “Gosh, I’m so clumsy!” sometimes it was also “Why on earth is it so easy to make a call on this app? Does the app not recognize that once a call is made, there’s no going back? That it’s always going to be there on record and that this can be awfully damaging in way too many situations?”.</p><blockquote>I learned to blame the app. I learned how to actively observe where i was uncomfortable and try to figure out how minor tweaks could make me more comfortable. Instead of taking an app to be written in stone, I started prioritising myself (the user). That changed everything.</blockquote><h3><strong>The problems and their solutions</strong></h3><p>Now that I’d learned how to identify user problems, I set about doing the same on my own and here’s what I squared in on</p><h3>1. Calls:</h3><p><strong>Problem</strong>: Making calls was way too simple. The buttons were way too accessible. This problem was identified on the basis of the following assumptions,</p><p><strong>Assumption 1: Most users in India own a phone with a small to average size screen.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*XU3RSFh5AqAcXlr2BGxIQg.jpeg" /><figcaption>The call buttons</figcaption></figure><p>As is visible above, the call buttons</p><p>a) lie very close to the drop down menu</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*tDsALlmuIXucr5NurzP26g.png" /><figcaption>Touch zones on an average sized phone screen according to ease of access</figcaption></figure><p>b) lie in the ok zone for most Indian users</p><p><strong>Assumption 2: A significant chunk of the Indian user base is not very comfortable with tech</strong></p><p>Defining the average Indian user, as observed by the author:</p><p>(Please note that this is a very rough and crude division. The Indian user base is very diverse and each of these divisions can be further divided on the basis of region, education levels, occupation, etc)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7WHX06asi4eRvpYZBtQ0g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*iQRr9OnpmiDQdKpnUaeB7w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*QFuL4L4QXR7sW2tWxzIZHQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrGrSFHLvBqROspmwiiFTg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*4fFtFqgt3zucXs17RrHdUg.jpeg" /><figcaption>Illustration courtesy: <strong>Brown Paperbag</strong></figcaption></figure><p>As is conveyed above, the working parent, the homemaker, and the cool grandparent(or most grandparents for that matter) are intimidated by smartphones (or technology in general) by varying degrees. These categories constitute a significant chunk of the userbase.</p><p>Therefore, it’s safe to say that they’d be happier if the chances of accidents are reduced.</p><p><strong>Solution</strong>: Placing ‘call’ as the first option in the three dot menu</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*px6aOt_unoJhAMiOyhgAwA.jpeg" /></figure><p><strong>Thought process:</strong></p><p>In the above solution,</p><ul><li>The call button is not as easily accessible, and yet, since its the first option in the three-dot menu, it’s not very difficult to find either.</li><li><strong>Calling is a deliberate action and the user has no other alternative to making a call</strong>. This fact makes<strong> visibility</strong> a non-issue. Therefore, the increase in the number of steps to make a call will not affect the probability of the feature being used.</li><li>There is a step in between pressing that button and the actual call. This step, where the user chooses what kind of call he wants to make, also <strong>acts as an indirect confirmation that the user actually intends to make the call.</strong></li><li>Chances of accidentally making a call will get significantly reduced.</li></ul><h3><strong>2. Location of the search button</strong>:</h3><p><strong>Problem</strong>: The search button is not very accessible. It appears in the drop-down menu which made it difficult to locate the first few times and even after the user has become used to its location, scrolling always makes for the more intuitive option.</p><p><strong>To gain more insight into this issue I conducted a test</strong>:</p><p><strong>The test</strong>: I met a bunch of unsuspecting people(mom, dad and a couple of classmates) and pretended to search something on a group that we shared and then asked them to search for it because “my network was creating issues”. As they did so, I silently observed.</p><p><strong>Result</strong>: Whenever a person had to search for something in a chat,<strong> they first scrolled</strong> and the idea of using the search option almost always hit them belatedly after they had already become pretty frustrated due to all the unnecessary scrolling.</p><p><strong>Solution:</strong></p><p>New position for the search button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*BlgeZkx1Qok5FB4OIxQtMA.png" /></figure><p><strong>Thought process</strong>:</p><ul><li>Searching is an optional function. One can always scroll instead(in most cases). In order to be truly helpful, <strong>the search button needs more visibility</strong>. It is unable to fully serve it’s purpose because people usually forget that it exists.</li><li><strong>The search button is a low-risk button</strong>. This means that pressing it accidentally doesn’t have any serious consequences as opposed to the call button where another person gets involved in case you end up pressing the button accidentally.</li></ul><h3>3. <strong>Search options</strong>:</h3><p><strong>Problem</strong>:</p><ul><li>The search option is incredibly basic. For example, you can’t search by date or even by the name of a member.</li><li>The relevant results are not displayed together instead they are highlighted and one has to scroll endlessly in order to be able to locate the relevant message.</li><li>The fact that older messages take a little time to load as you scroll up makes the whole ordeal all the more exasperating.</li></ul><p><strong>Solution:</strong></p><p>In order to solve the above I decided to add two new features:</p><ul><li><em>Search by member (group chats only)</em></li><li><em>Search by date (group and individual chats)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tgLU5A8rNCbXF9gJC-sVqg.jpeg" /><figcaption>Switching between the various modes of search</figcaption></figure><p><strong>Search in conversation functions just like the current search does.</strong></p><p>Additionally,</p><p><strong>Search by date</strong>:</p><p>Features:</p><ul><li>Messages can be searched for by the date on which they were sent</li><li>The arrow next to message directs the user to the original conversation(context)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ue8OiENIx03PgFrQdg3z0A.jpeg" /><figcaption>Search by member-flow</figcaption></figure><p><strong>Search by member:</strong></p><p>Features:</p><ul><li>Messages can be searched for by name of the member who sent them</li><li>All messages by the particular member come together(sorted according to date)</li><li>The arrow next to message directs the user to the original conversation(context)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wz3jN6EpWMECDlCIhhb5ag.jpeg" /><figcaption>Search by member-flow</figcaption></figure><h3>4. The absence of a diplomatic alternative to ‘block’:</h3><p><strong>Problem</strong>: Whatsapp has no feature which allows you to completely avoid reading a person’s texts without blocking them. Blocking implies that the messages won’t reach you at all which is great but <strong>sometimes all you want is to not see a certain chat in your inbox every morning but to still receive the texts and access them whenever you want to</strong>.</p><p><strong>Solution:</strong></p><p>the <strong>IGNORE </strong>feature!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*iDKknH49CirerQpyKAhxPg.jpeg" /><figcaption>The ignore feature</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*J_bhBlLHf7xuq-3D5_n7Dw.png" /><figcaption>Accessing ignored chats</figcaption></figure><p><strong>Thought process:</strong></p><p>In the solution proposed above:</p><ul><li>The ignored messages have<strong> zero visibility</strong>. The user, therefore, doesn’t have to encounter these chats unless he actively desires to.</li><li>The user doesn’t need to explicitly block people. <strong>Blocking is generally seen as an extreme measure and people don’t usually wish to resort to it unless their relationship with someone is explicitly sour. This is a more diplomatic way out.</strong></li><li>The user gains greater control over his/her inbox.</li></ul><p>I understand that WhatsApp’s USP lies in the fact that it’s very simple and there is just one inbox where all categories of chats are displayed together. But, I have come to believe that <strong>the user comes first and the product should be centered around the user. I feel that no rule is unbreakable except for one: The user should feel as much in control as possible. </strong>I feel that this feature doesn’t break this one rule<strong>.</strong></p><h3><strong>5. Changes in the drop menu:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*1rxUQenU8yaTqBNbZ04MYQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*6-FwWuZC-KFksHfYrKxxDw.jpeg" /><figcaption>The drop-down menu: before(left) and after(right)</figcaption></figure><p><strong>Thought process:</strong></p><ul><li>I feel the functions in the original drop menu (left screen) are not really important enough to be visible as soon as you open the drop menu. These options are also accessible from other places on the same screen.</li><li>In the proposed solution, <strong>you know all the options</strong> that you have for a particular chat as soon as you open the drop-down menu. You instantly know that you can <strong>mute, ignore, block</strong> or even<strong> report</strong> a chat.</li><li>The chances of actually opening and checking the more option are relatively lower. Therefore, the possibility that a chunk of users might never know that some functions(like a report) exist, is significantly reduced in the proposed solution.</li><li>Also, <strong>wallpaper</strong> should be a part of the settings of the app as a whole and not be an option in every chat window. It is not important enough to be so easily accessible in every window. It&#39;s<strong> more of secondary action, a relatively vain indulgence, as compared to other functions</strong>.</li></ul><h3><strong>Learnings:</strong></h3><ul><li>The younger generation is capable of differentiating between a well-designed app and a badly designed app, whereas the older generation is not. The <strong>older generation is also aware of their unease around technology</strong>. Whenever something goes wrong,<strong> the older generation tends to blame themselves and not technology</strong> and ends up losing confidence, even more, when it comes to using technology. It is<strong> incredibly crucial that apps be as well designed as possible for the older generation to feel comfortable with tech and for them to feel encouraged to use it.</strong></li><li><strong>Empathy is a skill, not an emotion</strong>. To learn it and to be able to do it well, you need to practice it every day. And it is also perhaps one of the most invaluable skills you’ll ever learn.</li><li><strong>Things which seem the simplest were the toughest to build</strong>. It’s easy to complicate things. To simplify takes tons of effort and patience.</li><li>I’ve started appreciating the fact that the smallest of things taken someone’s thought and effort to come into existence.</li></ul><p>Thank You for reading. All suggestions and constructive criticisms are welcome.</p><p>If you liked the article, please let me know by pressing on the clap button below.</p><p>P.S. You can<strong> clap 50 times </strong>on Medium! Just long press that little icon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e4b84a02644" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-studio-iit-roorkee/redesigning-whatsapp-8e4b84a02644">Redesigning WhatsApp</a> was originally published in <a href="https://medium.com/design-studio-iit-roorkee">Design Studio, IIT Roorkee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dribbble Roorkee Meetup]]></title>
            <link>https://medium.com/design-studio-iit-roorkee/dribbble-roorkee-meetup-b1df33dcde65?source=rss----70fe26422ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/b1df33dcde65</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[unacademy]]></category>
            <category><![CDATA[iit-roorkee]]></category>
            <category><![CDATA[dribbble-meetup]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Lakshya Kumawat]]></dc:creator>
            <pubDate>Mon, 18 Feb 2019 21:37:42 GMT</pubDate>
            <atom:updated>2019-09-26T12:39:48.359Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Being a part of the rapidly growing global designer community is very exhilarating. Sharing our thoughts and ideas with people has given us a great sense of what design means to the industry and how we can grow and co-exist as a professional. Also, we have realized that networking is a key skill to facilitate growth in any community and hence conducting networking events such as a Dribbble Meetup is essential to help a community which is off the map and make them aware of the industry standards.</p><p>Thus, to provide exposure to the designer community at IIT Roorkee and promote the culture of design, we organized the “Roorkee Dribbble Meetup” on February 2nd, 2019. This was the second edition of Dribbble Meetup in Roorkee which was organized by <a href="https://designstudio.cc/">Design Studio</a> in collaboration with <a href="https://www.facebook.com/ecelliitr/">E-Cell IIT Roorkee</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGqFHEOzZ1MEpblzjt1b6Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1d584DUYaDTEj8c3Rptbeg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DYUr3jWiyxTcUsyiX6nkIw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYlZizGRTUvDUzBAbgII-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TBwUbsAkDKlnOQstD2qWEA.jpeg" /><figcaption>Highlights from Dribbble Roorkee Meetup</figcaption></figure><p>This being our second time hosting the event, we wanted to make the event interesting and scale it up but faced a lot of problems in achieving the same. This is a frequent problem faced by many organizers, especially in the meetups organized in India.</p><p>So, I’ve decided to compile all that I have learned from organizing such a meetup into a guide about organizing and managing a Dribbble Meetup of a scale which is similar to the ones organized by corporates.</p><h3>Planning</h3><h4>Phase 1:</h4><p>The first and foremost thing about hosting a meetup outside the U.S. is that you should start planning your meetup at least 2 months prior to the date you decide to organize the event. This is because it takes two months for the Dribbble Swag Kit to reach you after you have applied as the host for the meetup. Within the U.S., it takes around 2 to 3 weeks to reach the organizers. And believe me, one of the most fascinating things about a meetup is its swag kit. It adds to the creative vibes that you would love to have during the event.</p><p>So when you start thinking of hosting a meetup, the first thing you do is log on to “<a href="https://dribbble.com/">dribbble.com</a>” and under the community section select “Host a Meetup”. Fill all the required information and bingo! You are all set with the plan and now should proceed to arrange other logistics. Some of the information asked can be tentative like the number of attendees, et cetera.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HIQJr6WfXjDRGDw_HjqTnQ.png" /></figure><h4>Phase 2:</h4><p>As you know, most of the meetups are intended to socialize and share experiences. So your next move should be to spread the word about your meetup and try to get in RSVPs from the designer community around you. This will help you gain recognition within the community and also would help the dribbble team to ascertain and send the required number of swag kits for the meetup.</p><p>Now, to make the meetup more informative and add some learning value to it, you could also try bringing in some quality designers working in the design teams of good companies and startups. This will be very encouraging for the designers in your area and might as well help you in getting more participation.</p><p>Bringing in a reputed designer is a big challenge but you can expect a good response from many of them. Try connecting with as many as possible and tell them about your event and share stories of designers around you and how the community is fostering in your vicinity. Even if some of them are not available, stay connected to them. This might help you with future events.</p><h4>Phase 3:</h4><p>Now it’s time to start planning the fun events or sessions you want in the meetup. On a general basis, people try to decide a theme and all the events according to that, but this is not compulsory.</p><p>The events should consist of:</p><p><strong><em>Ice Breaking</em></strong>: to get an idea of the people attending the meetup.</p><p><strong><em>Knowledge Transfer Session</em></strong><em>:</em> to let people share their experiences and discuss design practices prevalent in the industry.</p><p><strong><em>Fun Event:</em></strong> to let people socialize and have fun while they tackle a design problem during the event.</p><p>You can add anything else you feel appropriate. But extending the meetup to more than 6 hours is not recommended. After all these events, end the event with a closing note and share the swag kit with the participants.</p><h3>Roorkee Meetup and its events</h3><p>Roorkee Dribbble Meetup 2019 was organized at IIT Roorkee campus in Sattviko Idea Cafe which has got a great ambiance and has the perfect vibe for an event like this. Around 50 people attended and participated in the meetup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*8-DToaENJ5WVaMXEFEbwrQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*f1mIQcJihjsVUF-46I3nEA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*Rx7nsTj7tzeSBpDxqVzzAQ.png" /><figcaption>Sattviko Idea Cafe, IIT Roorkee</figcaption></figure><p>As the keynote speaker for the meetup, we had invited <a href="http://abhinavc.com/"><strong>Mr. Abhinav Chhikara</strong></a>, head of design at Unacademy. As a product designer, he specializes in mobile UI/UX and growth and also has a<a href="https://www.youtube.com/channel/UCOuiO3_-SBxnZ7-zAVSsShw/featured"> youtube channel</a> where he shares content related to design and his experiences in the industry.</p><p>The meetup started by introducing the speaker to all the designers followed by a talk from Abhinav. He talked about:</p><blockquote>His story of going from an engineer to a professional designer.</blockquote><blockquote>Future of design in startups.</blockquote><blockquote>What’s the next big computing platform?</blockquote><blockquote>What happens when we hit the singularity?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pv2s52g_MMd5-GjaWIk6Ag.jpeg" /><figcaption>Talk by Mr.Abhinav Chhikara</figcaption></figure><p>The talk was very engaging and insightful. It not only covered the stuff we regularly hear as designers but also a lot of new things which caught the fantasy of all those present.</p><p>Then we started with our Ice breaking session, which was divided into 2 parts. <strong><em>Team Distribution and Pictionary.</em></strong></p><p>The theme we had was an amalgamation of fiction and design. The teams were named as House Montserrat, House Poppins etc., a blend of fonts and the T.V. series “Game of Thrones”. The participants were divided into 8 teams consisting of around 7 members each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrWje-vtB2jH400gIN5T_Q.png" /><figcaption>Team Names</figcaption></figure><p>After the teams were formed, we started with the Pictionary part of the Ice-breaking session. Each team had to send one volunteer who would pick one chit, read the word written on it and try to make his/her team members guess that word by drawing something on the board. These prompts were the terminologies of design which are essential for every designer to understand. For example Navigation bar, Mockup, Responsive etc. The constraint was that they had only 2 minutes to explain the maximum number of words to their team and guess them right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7rxlzZJ2H0ppK1R9G__ig.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ABjXJ93yF0WDFqI0w9-Mg.jpeg" /><figcaption>Teams taking part in Pictionary</figcaption></figure><p>The session was fun and served well as an ice-breaker for the participants. The maximum number of words were guessed right by “House Poppins” in which they guessed 5 words in 2 minutes.</p><p>The last event which was planned to let the participants socialize and network amongst each other while working on a design challenge. The challenge was to think over products that were twisted in some way or the other and then to make a presentable outcome of whatever they had come up within the given time of one and a half hour. Some examples of the options provided were <strong><em>Myntra for Minions, Airbnb for Ghosts, SBI for Squirrels</em></strong> etc.</p><p>During their 90 minutes of activity, many members of the teams took out some time to interact with the speaker and get answers to their questions related to design, career opportunities and how to assure incessant growth in the field. Abhinav responded well to their questions and was really open to talking about the core principles that they should inculcate in them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*29mGOp3hFbpmfWar98BnKw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ShQdFpqwkpWOMjhEhSqbYg.jpeg" /><figcaption>Designers Interacting with Abhinav</figcaption></figure><p>All the teams did well in pondering over their ideas and had really interesting and creative solutions to present. They had unique solutions to the problems and their presentations were quite intriguing.</p><p>After all the presentations, the final results were announced and the winning team was “House Montserrat”. Their topic was “ SBI for Squirrels” and their solution was very well planned, designed and presented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QPqwCJjHkcukl3ADKN5hxg.jpeg" /><figcaption>Winning team ‘House Montserrat’ presenting their solution. Team members: <a href="https://medium.com/u/a18c09fafef">kshitiz kashyap</a>, <a href="https://medium.com/u/954ea1d122c0">Utkarsh Gill</a>, <a href="https://medium.com/u/ea04ded6d970">Akshay Kamath</a>, <a href="https://medium.com/u/30d04a5a9360">Anchit Shukla</a>, <a href="https://medium.com/u/e756ab6372c4">Vaibhav Rawat</a> and</figcaption></figure><p>Concluding the event, the winning team was rewarded and the participants in the meetup received some exciting goodies from the swag kit. Everyone got to tinker over great ideas and network with other designers present at the event. Each participant took back something with them which was worth their time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2A0LHvDkP8alivA1eSmteg.jpeg" /><figcaption>Dribbble Swag Kit</figcaption></figure><p>I got the chance to escort Abhinav and bid him farewell with a token of love. I took his suggestions on how we can improve at organizing such events in the future and also how to improve the design culture on our campus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEZxoevP-VNkA2c-Y3nI9Q.png" /><figcaption>Presenting token of love</figcaption></figure><p>I hope we keep on having more such interesting events and also expect to see more people in the third edition of Roorkee Dribbble Meetup.</p><p>PS: Thanks <a href="https://medium.com/u/54453ac21977">Ishir Chatnani</a> for helping me in editing the blog and <a href="https://medium.com/u/30d04a5a9360">Anchit Shukla</a> and <a href="https://medium.com/u/9f10af29807b">Jayant Mishra</a> for your suggestions and helping in organizing the event.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1df33dcde65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-studio-iit-roorkee/dribbble-roorkee-meetup-b1df33dcde65">Dribbble Roorkee Meetup</a> was originally published in <a href="https://medium.com/design-studio-iit-roorkee">Design Studio, IIT Roorkee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>