<?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 Nipun Vashistha on Medium]]></title>
        <description><![CDATA[Stories by Nipun Vashistha on Medium]]></description>
        <link>https://medium.com/@nipunvashistha?source=rss-6b7f082fadfe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Wb8k9RlsT0IiLjCk.</url>
            <title>Stories by Nipun Vashistha on Medium</title>
            <link>https://medium.com/@nipunvashistha?source=rss-6b7f082fadfe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:45:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nipunvashistha/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[Designing ‘Rick n Pod’ in a Sprint]]></title>
            <link>https://uxplanet.org/designing-rick-n-pod-in-a-sprint-1c9b57a73031?source=rss-6b7f082fadfe------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c9b57a73031</guid>
            <category><![CDATA[industrial-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[sprint]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Nipun Vashistha]]></dc:creator>
            <pubDate>Mon, 26 Nov 2018 08:12:10 GMT</pubDate>
            <atom:updated>2025-01-08T12:32:43.504Z</atom:updated>
            <content:encoded><![CDATA[<h4>Design Sprint</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/0*VULIeDhXPtMs197-" /><figcaption>Great job with the logo, <a href="https://medium.com/u/48000e143639">Anshul</a>.</figcaption></figure><p><em>A design sprint was conducted among the students of IIT Roorkee with the goal to improve the primary mode of travel in the campus — e-rickshaws. The overall experience of travelling in an e-rickshaw on the campus has many problems associated with it. Three teams were created for the Sprint to identify and solve these problems. After brainstorming and designing for 48 hours, the teams were able to come up with unique solutions to solve the identified problems. According to Google Design, a Sprint is generally conducted for three/five days, we tried to complete the sprint in only two days. With this article, we aim to give a brief review of the design process and explain one of the three proposed solutions.</em></p><p>Team: <a href="https://medium.com/u/6b7f082fadfe">Nipun Vashistha</a>, <a href="https://medium.com/u/4b48182a2a65">Lakshya Kumawat</a>, <a href="https://medium.com/u/358c4f43fda4">Samar Singh Karnawat</a>, <a href="https://medium.com/u/48000e143639">Anshul Tembhurne</a>, <a href="https://medium.com/u/c3ae99095f73">Naveen Dara</a>, <a href="https://medium.com/u/d9dd05c035e2">Ayushi Patel</a></p><h4>What is a Design Sprint?</h4><p>Some of the readers may not be aware of the term Design Sprint and can have many questions about it. Like,</p><blockquote>How is it different from a normal design process?<br>What is the need to do a sprint?<br>What to expect after a design sprint is done? etc.</blockquote><p>According to Google Ventures, Sprint is a five-day process to answer critical business questions through design, prototyping and testing ideas with customers. It basically shortcuts the endless-debates and compresses a month-long process into a single week or shorter. Generally, a five-step process is followed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/0*eEq4z7EyUFPybgQv" /></figure><p>The sprint is started by a <strong>Sprint Master</strong>, who gives a brief overview of the problem to all the participants. This briefing is an important first step as the participants need to have the complete knowledge of all the pain points of the users, associated technology, business goals, and anything that is relevant to the given problem. After this ‘<strong>Lightning Session’</strong>, the teams move on to the <strong>HMW session</strong>.</p><h4>1. HMW Session</h4><p>HMW (“How Might We”), a note making method, which is done to identify all the opportunities associated with the pain-points. Basically, every participant notes opportunities on sticky notes and paste it on a canvas for the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wpDZFz-fC1l1MAFTHKWn2g.png" /><figcaption>HMW Session</figcaption></figure><p>The opportunities are framed in the form of questions which starts with “How Might We”. For example, an opportunity might be framed as <em>‘How Might We reduce the overall waiting period for a person trying to find an e-rickshaw?’</em>. This activity is aimed at diverging as much possible and to prevent arriving at any kind of premature solutions.</p><p><em>E-rickshaws are the most frequently used form of the daily commute in IIT Roorkee campus and since all the sprint participants were students of the university itself, we already had numerous problems in our minds and after talking to the drivers we got to know the problems that they faced on a daily basis too. The university has a set of registered e-ricks, and only these e-ricks are allowed to drive in the campus. In general, people use these rickshaws to go to lecture halls, activity centres etc. which are all in a 365-acre area.</em></p><p>At the end of this session, we had a sufficient number of opportunities and a common understanding among the team members on what exactly are we looking to solve.</p><h4>2. Affinity Clustering and User Journey Mapping</h4><p>Affinity Mapping is a method to categorize the notes that were created in the HMW sessions according to similar themes. This categorization helps you answer questions like which sectors of the system has what problems in it, what is the number of problems in a particular category, which category should be given importance etc. It basically broadens the perspective of the whole team and pushes them to think of the pain-points from different angles.</p><p>We clustered our HMW notes in two ways. First was according to the journey phase of a rider <em>(Deciding, Onboarding, The Ride, Completion Phase, Post-Completion Phase etc.)</em>. The second was on the basis of themes such as <em>Payments, Availability, Time, Convenience, Misc etc.</em></p><p>User Journey Map was created and at the same time, we started to come up with the potential solutions for the problems associated with each step of the rider and driver journeys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yMEWU1oFsBVuaw9a" /><figcaption>A not so fancy User Journey Map</figcaption></figure><h4>3. Vision Statement and Potential Solutions</h4><p>Once you have the set of important problems you want to solve and a golden path. It is important to set a vision statement for the team and the solution. It helps to spend time on only the things which are relevant.</p><blockquote>“Create an ecosystem where the driver and the rider are on the same grounds”</blockquote><p>After setting up a vision statement, we were done with the Defining phase of the sprint. After countless discussions on the potential solutions, we finally decided to create an ecosystem for the riders and drivers which would basically make both parties aware of their locations and maintain a balanced supply to demand ratio of e-rickshaws in the campus.</p><p>We opted for a solution which wasn’t too mobile-app centric and was more tangible in improving the journey, majorly because an e-rickshaw journey is very spontaneous and on an average takes barely 5–7 minutes for the whole journey. We did not, hence, want users to take steps that would increase the overall journey time. We wanted to incorporate our solution into their lives without changing their daily routine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/0*JUAP0pKjyXhISQs6" /><figcaption>The whole system consisted of these three major components</figcaption></figure><p>After reviewing and voting on all possible solutions, we selected our golden path and started working on it. By analysing the entire campus map and the population density we chose 7 hotspots to set up pod stations for the drivers to charge their e-ricks (an incentive for the drivers to increase supply), and for the riders to track and create a request to e-ricks (Requests would be received by the drivers in a proximity of 200 meters, once an e-rick arrives in a range of 100m from the pod, the request would die out automatically).</p><p>For the drivers, an interface shall be installed in the e-rick by which they can update their availability status and also receive the requests generated from pods.</p><p>An app can be provided for the user through which they can track the location of e-ricks. It will also provide information about all the drivers so that user can contact them for booking an e-rick during the night. The feature of sending a request is not provided in the app to avoid unnecessary spamming by the riders/students.</p><h4>4. Sketching out solutions</h4><p>After we had the set of modules that we wanted to create in our hands, we moved onto the sketching part. The approach that we followed here was to get as many as possible sketches in a limited time.</p><p>We divided our time into three sessions of 30 minutes (Sketching, 15 minutes + Deciding, 15 minutes) for three modules. Every team member was given strict 15 minutes to sketch out their ideas on a piece of paper, by the end of 15 minutes we had six different sketches of a single module and finally created a single one taking inspiration from each one of them. That way we were able to see numerous sketches of the solutions in a limited time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eOFVRcdmW0uf1i1uuyl4_A.png" /></figure><h4>5. Prototyping</h4><p>It was time to convert the wireframes we created into UI and prototypes. For interface design and prototyping we used Figma since it is a collaborative tool and saves a lot of time when working in a team. For 3-D modelling, we used Cinema 4D.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z41XSzo78_YUgMcwQKK_Xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R9m7AXyo1oI5Flof1L-qCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3B_y2ePxibjXoqxMnGQljA.png" /><figcaption><a href="https://medium.com/u/c3ae99095f73">Naveen</a> and <a href="https://medium.com/u/4b48182a2a65">Lakshya</a> literally went to measure scope of the area to create these amazing 3D models.</figcaption></figure><h4>Review and conclusion</h4><p>After 48 hours of continuous discussions over infinite use-cases and possibilities, in end of the sprint, the three teams were ready with their products. Best part was that every solution was unique in itself, they all were adding value to the lives of riders and drivers from a different angle. Validation and feedback are two of the most important steps in any design process. All three of the solutions were presented to all the participants as a constructive feedback session. Obviously, every solution had its set of flaws and pros, but we hope to pick out the right stuff and get something implemented out of them in the future. Nevertheless, this activity really helped us to generate empathy for the drivers and riders who travel everyday in e-rickshaws in the campus.</p><p>Shoot any feedback you have!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*10FuNKK04NCtIFoVJ-2RMw.jpeg" /><figcaption>Team Rick n Poddy</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c9b57a73031" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/designing-rick-n-pod-in-a-sprint-1c9b57a73031">Designing ‘Rick n Pod’ in a Sprint</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we revamped our Team Page]]></title>
            <link>https://medium.com/sdslabs/how-we-revamped-our-team-page-17e7ea29d73?source=rss-6b7f082fadfe------2</link>
            <guid isPermaLink="false">https://medium.com/p/17e7ea29d73</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Nipun Vashistha]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 23:34:42 GMT</pubDate>
            <atom:updated>2018-09-05T12:25:43.462Z</atom:updated>
            <content:encoded><![CDATA[<h4>Never forget your core</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gTzpT8MeB2DUuCMvi_5eKg.png" /></figure><p><em>Those of you not knowing, SDSLabs stands for </em><strong><em>Software Development Section Laboratories</em></strong><em>. We are a student run technical group.</em></p><p><em>Recently, I redesigned our team page to give it an experience and represent the organisation’s core more clearly. In this article I have tried to maintain parallels between designing any product in general and the idea behind this redesign.</em></p><p>We at SDSLabs, since our inception, have constantly tried to innovate and come up with ideas that could make lives of students at IITR easy, and we have come a long way since the beginning. But there is always one thing that has remained constant throughout the journey, <strong>the people.</strong> The amazing amalgamation of <strong>designers</strong> and <strong>developers</strong> in the lab has always been reflected in the products we have delivered.</p><h4>Why do we need a team page?</h4><ol><li><strong>Team pages helps to build trust with your audience</strong></li></ol><p>For any organisation, building a personal connection with the audience is very important. A team page adds a human touch to the organisation, enabling the user to associate people to an organisation. The user, then, does not feel that he is simply interacting with lines of code. And when the audience is mainly college students, who always strive for a personal relationship instead of a professional one, it is highly beneficial to add these steps towards a mutually trusting relationship.</p><p>2. <strong>Team is the most integral part of an organisation</strong></p><p>Any organization is run by its people. This makes it important to give them due credit. However, most organizations are about the products they build. If their products die, the organisation dies. SDSLabs, on the other hand, is all about the people behind it. We do not tell the world how good our products are, but how good our people are to have been capable of creating those. This makes having a team page a priority.</p><h4>But why redesign if it already exists?</h4><p>We already have a team page. It shows our members, give their details, links to their social profiles. It serves its purpose well. So why did we need a redesign?<br>For SDSLabs, its core value lies within its team, the designers and developers, who work together to ideate and build new products. Moreover, the creation of a strong alumni base over time, who are now working with some of the major corporations around the world, necessitates giving them due focus.</p><p>So, to represent our core values and the structure of our team in a very clear manner, and adding an experience to it for the users visiting it, we needed a redesign.</p><h3>How we did it</h3><blockquote>No design is absolutely perfect.</blockquote><p>Every product that designers design has to meet some user goals and must solve, as much possible, the problems that users might face. For this, it must be ensured that every design task goes through certain steps for the best possible form of product to get shipped, which is called a Design Process. At SDSLabs too, every product goes through a standard design process, which might vary sometimes according to kind of product we are shipping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*G5pbNWRTCXykkpE493N9ig.png" /><figcaption>Design Process at SDSLabs</figcaption></figure><blockquote><strong><em>Discover</em></strong></blockquote><blockquote><strong><em>Define</em></strong></blockquote><blockquote><strong><em>Ideate</em></strong></blockquote><blockquote><strong><em>Ship</em></strong></blockquote><blockquote><strong><em>Iterate and find problems</em></strong></blockquote><p>These five steps are what defines our design process. We research and discover, define the features and conceptualize everything, ideate, and find the best possible design solutions, ship our product within our team to gather feedback, iterate on it and find more problems with the current design, and we keep iterating and shipping till we get the best possible and feasible solution to the design task.</p><h4>Discovery</h4><p>In UX design, discovery or research is the first step towards solving any relevant problem or narrowing down to the right problem. A designer’s job is to understand the users, understand the organisation you’re working for, in order to create something. There are many methods of design research; it mostly depends on the the product you are working on to decide which research methods you should opt for or which ones should be prioritised.</p><p><strong>Primary</strong> and <strong>Secondary</strong> research methods are useful to create something from scratch, whereas <strong>Evaluative</strong> and <strong>Exploratory</strong> research methods are used to ensure the usability of a product. Primary research is concerned with understanding your user with different methods to further make mental and conceptual models. Secondary research methods are about gathering information from various sources to support the context behind your design and the choices you made.</p><p>In this redesign, we needed to find the problems in the old team page, and to think of any additional features we could introduce or redundant ones we could remove.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3erbQdQrIBRunNr_nndMxg.jpeg" /><figcaption>Old Team Page of SDSLabs</figcaption></figure><p>The old team page consisted of a tile arrangement of the member profiles, whose order used to change every time you revisited the site. A major problem with this team page was that it did not show the structure of our team in the correct way. The role of a person could not be inferred without significant effort that involved visiting individual profiles. The alumni, which are still an integral part of our organisation, were missing too. The name of each member, and links to their social media profiles were displayed on hovering, but they were not prominent enough. So we listed down what do we need in our new redesign of the team page. We needed a team page that could:</p><ol><li>Represent our core, our team structure, correctly.</li><li>Differentiate between the developers and designers, yet binding them.</li><li>Show profiles of our alumni base, where they are located, and what they are doing after passing out of college.</li><li>Be more interactive for the visiting users.</li><li>Show names and social media profiles prominently enough.</li></ol><h4>Define</h4><p>After noting down what we wanted with our page, we needed to define things conceptually. We needed to structure exactly what components we required in the page.</p><p>List of the main components:</p><ol><li>A landing page, defining the structure of the organisation</li><li>Separate sections for designer and developer member profiles</li><li>A section displaying how the alumni are located globally</li><li>A dedicated alumni member profile page</li></ol><h4>Shipping and Iterating</h4><p>As stated previously, “No design is absolutely perfect.”. Now, how do we reach the best of our product? We take constructive feedback and iterate.</p><p>Effective feedback, both positive and negative, is one of the most essential and underrated parts of designing any product. It is important for humans to know our mistakes and, in response, to change. It helps us to be a better designer and to create better products.</p><p>After the designs were completed, we posted the initial iterations on our internal network to both designers and developers, to gather feedback and find what problems does the current design have, and to rule out any complications that might come up during the development phase of the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hhmZptHmqSElh4dkG1g9xw.png" /><figcaption>Initial Iterations</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsDfsh_u9MyxI8V5a8FdUA.png" /></figure><h4>Final Designs and Prototype</h4><p>After multiple iterations and design meetings, it took us a month to finally deploy this new team page.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2FDefiniteMatureBlackbird&amp;url=https%3A%2F%2Fgfycat.com%2FDefiniteMatureBlackbird&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FDefiniteMatureBlackbird-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="1006" height="566" frameborder="0" scrolling="no"><a href="https://medium.com/media/9907923dcf69df01f8ab3d3bba23a7c0/href">https://medium.com/media/9907923dcf69df01f8ab3d3bba23a7c0/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17e7ea29d73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sdslabs/how-we-revamped-our-team-page-17e7ea29d73">How we revamped our Team Page</a> was originally published in <a href="https://medium.com/sdslabs">SDSLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Careers Page at Bewakoof.com]]></title>
            <link>https://uxplanet.org/designing-careers-page-at-bewakoof-com-1af76f98ed83?source=rss-6b7f082fadfe------2</link>
            <guid isPermaLink="false">https://medium.com/p/1af76f98ed83</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Nipun Vashistha]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 08:53:52 GMT</pubDate>
            <atom:updated>2018-09-03T20:05:26.852Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learnings as a Product Design intern</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VrKUT7O2Ju7HwJ-nRg9m_w.png" /></figure><p><em>In the Summer of 2018, I did a Product Design internship at Bewakoof.com, which is a home-grown contemporary fashion brand based out of Mumbai. As an intern, designing Career Page was my first out of three projects I did at Bewakoof, which I was supposed to manage and get shipped working alongside my Product Manager. I have tried to elaborate my learnings as a product designer and what it takes to ship an ancillary page for a company.<br>Breaking into the product design world as a self-taught designer is hard, because the field is relatively new and there are a few resources to learn for curious students. But eventually, I fell in love with the problem-solving, the complexity, the collaboration with product managers and engineers and other teams to build something from nothing, and consequentially the project ended up being a great learning experience.</em></p><p>For me, it was not just working at a <em>digitally-native vertical brand (DNVB)</em>, it was more like working at a fast paced lean working environment where problems were solved by cross functioning teams. No problem which was to be solved was too trivial or too big, it was just the matter of analysing and prioritising the real problem at the moment. Many problems are left untouched when you are working at a company, it is not because those are fake problems, it is because the first question to ask is, <em>is this a problem worth solving?</em></p><p>So how do we know which is a real problem?</p><p>As Julie Zhuo, VP Design at Facebook puts it very beautifully. We need to have a qualitative or quantitative evidence for the problem we are trying to solve and then we should move on to asking if this is really worth it? Because all of us have limited time, money, energy, and resources to solve a problem in a particular business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDZpYocBaDiDckgPx2vAWg.png" /><figcaption>Thank you, Julie, for breaking this down to me.</figcaption></figure><h4>The Problem Statement</h4><p>After various discussions and findings I realised that our problem statement is a multi-fold statement. We are kind of using the opposite approach to problem solving, we created a hypothesis that solution to the multiple problems we are facing can be solved by redesigning our Careers Page. We might have been wrong at that time, we might have been totally correct. <strong>Lean UX</strong> approach always starts with <strong>Benefit Hypothesis</strong>, accepting the answer without validating it first, and it then moves through a continuous exploration cycle. In the process we found out that the major problems we are facing are,</p><ol><li>Very low percentage conversion rate from the existing career portal.</li><li>Rare to find quality applicants which are right match for the company.</li><li>Applicant data collected by HR is very discrete.</li><li>Low responsive nature of the current portal. <em>(90% of my audience used mobiles)</em></li></ol><p>After successfully and hopefully identifying the problems we were finally ready to kick off the project. To solve any problem you first ask what the problem is, then find out who are you solving it for, then discuss on what the probable solutions are, and finally if you are done with all your assumptions and research, how are you actually going to measure the success of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDBE2AKwNphqS7Zs7KAKyQ.png" /><figcaption>Project flow can vary depending on the type and the scale of project</figcaption></figure><h4>Who are we solving it for</h4><p>One of the earliest, most immediate takeaways from user research that helped us to identify and narrow down our audience was that most of the people who are willing to work at Bewakoof were those who were already aware of what kind of company Bewakoof is, and most of them were frequent users of Bewakoof and similar websites. That helped us identify the intents of our audience better.</p><p>Our audience might have different intents when they come to visit the Careers Page:</p><ol><li>Searching for a first time job</li><li>Switching from one company to another</li><li>Switching between his/her current field of interest</li><li>Fashion enthusiasts or explorers who are fascinated with work culture and want to join irrespective of the area of interest</li></ol><p>Not all companies need to build complex personas, when you are working in agile, the deadlines dictates that we focus on <strong>20% of efforts</strong> which <strong>produce 80% of the valuable outputs</strong>. What is more important is to build an understanding among the team of your user rather than focusing on documents.</p><p>After gathering all the research we were able to create User Personas to help us empathize<em> </em>with the needs and preferences of our major user groups:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ic_-lsMQoIx4dg6o4hrUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jFZDItDIM88V2orznoQJCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVtdP3yscPi9LugOnqRf0g.png" /></figure><p>After I narrowed my audience into these three focus groups, I was under the impression that my work is done. But as I discussed this with my product manager we got into a very interesting argument on whether we should take design decisions according to the needs of <em>Rohit</em> or we should cater more to <em>Ramneesh</em>. I was arguing that we should think about <em>Rohit </em>first, as a person applying at a company like Bewakoof would be young and more of an explorer, but my manager had contrasting views on this matter that we should design for <em>Ramneesh</em> first. When I asked why, he told me <em>because the data says so. <br></em>Which led me to think about another ongoing debate in the industry on whether or not should designers know about data. To put in better words, should a company follow data centered design or a human centered design approach. There could be three approaches to data-centered design:</p><ol><li><strong>Data Driven :</strong> Taking all your design decisions according to the data.</li><li><strong>Data Informed :</strong> Taking only yes/no decisions with help of data just to find out if you are going in the right direction or not.</li><li><strong>Data Aware :</strong> Being aware of the kind of data you’ll be able to collect through the design.</li></ol><p>It mostly depends what kind of organisation you are working for, but it is always a mixture of these three approaches. So we checked the data (we were using Google Analytics and Tableau for data analytics) and found out that most of the people applying at Bewakoof through the portal are more like <em>Rajneesh.</em></p><h4>Creating flows and iterating</h4><p>I will not go into much detail on the detailed user flows involving every single step of a user’s journey because that would be unnecessary. But typically our application funnel looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBdm5QaIiySD2erl7G1s7A.png" /><figcaption>Application Funnel</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nscdnnZmcURaMwBEUVvs8w.png" /><figcaption>Complete flow</figcaption></figure><p>After understanding the typical user flows we were able to create information architecture and wireframes for our UI designs. While the creating the UIs, it was important to follow the current branding language of the company. Most of the branding pages at Bewakoof were designed by balanced use of typography, white space, and pictures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jtz02VY95rcXFoDyytZfkA.png" /><figcaption>Initial wireframes and explorations</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rmT5CDHyuFowJiM7ANZ-A.png" /><figcaption>Some of the initial UI iterations for web</figcaption></figure><p>One of the three fundamental ideas of <strong>Lean UX</strong> is to work in an <strong>agile strategy</strong>, whose nature is to work in rapid, iterative cycles and Lean UX mimics these cycles to ensure that data generated can be used in each <strong>iteration</strong>. These initial designs were now ready to continuously iterated upon.</p><p>At Bewakoof, we give a lot of effort to <strong>usability evaluation</strong> and iterating on our designs until we are able to create designs which are properly tested and optimised according to business and user goals. In usability evaluation, users are given a set of task to complete, the moderator observes each participant’s actions, and on the basis of the findings gathered through this exercise, it is made sure that the new design is is intuitive to use and provides a positive user experience. The aim of the usability evaluation is to ensure any potential issues are highlighted and fixed before the product is launched.</p><p>I created two very different use cases to cover both kind of sections that my portal is going to have:</p><p><em>Use Case 1 : You are a Data Scientist who is looking for a job change. You know a little bit about Bewakoof. Your goal is to find a relevant job opening and apply for the job.</em></p><p><em>Use Case 2 : You were going through our t-shirts and accidentally landed on our careers page. Now you try to explore and find out if the webpage interests you.</em></p><p>After many rounds of user testing and finding usability problems we were finally able to put an end to our design process. But as a product designer my job was not over, it was my responsibility to keep interacting and solving any problem with the tech, photography and content team to create an overall positive experience for the user. And finally we were able to create something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sp3fGPEikYi2rf5KIO0DSA.png" /><figcaption>Final version of designs</figcaption></figure><h4>Concluding it</h4><p>After three weeks of brainstorming, creating and prototyping, we managed to produce a new portal which increased the number of applicants applying to work at the company, solved the problem of discrete data management by categorizing and sending grouped mails through back-end to HRs. The new designs were highly responsive for all our platforms, and there definitely was an improvement in usability of the portal as compared to the older version.</p><p><em>Ofcourse this is not the best process or the best designs. Designers are a constantly evolving species and rely a lot on feedbacks. Feel free to send me any thoughts.</em></p><p><em>Follow me for more case studies and experiences. Or follow me on </em><a href="https://dribbble.com/nipunvashistha"><em>Dribbble</em></a><em> for project briefs.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1af76f98ed83" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/designing-careers-page-at-bewakoof-com-1af76f98ed83">Designing Careers Page at Bewakoof.com</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>