<?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 Nainika Verma on Medium]]></title>
        <description><![CDATA[Stories by Nainika Verma on Medium]]></description>
        <link>https://medium.com/@Nainika24Verma?source=rss-5489bdbafaa8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bdXIAWWqoqZm7pbXog5KeQ.png</url>
            <title>Stories by Nainika Verma on Medium</title>
            <link>https://medium.com/@Nainika24Verma?source=rss-5489bdbafaa8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:58:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Nainika24Verma/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[The Design Wall]]></title>
            <link>https://medium.com/@Nainika24Verma/the-design-wall-ee8150c6ad3a?source=rss-5489bdbafaa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee8150c6ad3a</guid>
            <category><![CDATA[improve-products]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[feedback-loop]]></category>
            <dc:creator><![CDATA[Nainika Verma]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 07:57:00 GMT</pubDate>
            <atom:updated>2021-05-25T05:37:31.877Z</atom:updated>
            <content:encoded><![CDATA[<h4>Get random feedbacks and improve your products every day.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YXBNyeCRfNLIzOn3-fH4PQ.png" /></figure><p>We designers are always working towards making products and life better. While the whole team works in an agile environment, we keep on evolving the products in every coming day.</p><blockquote>You design, you develop and give birth to a new product or feature every sprint! the moment a product or feature comes into a lifecycle it needs to improve in every stage of its life.</blockquote><p>Solutions can’t be achieved in isolation, and the best ideas will come when leaders join forces to drive progress. A product improves and evolves! to do so the product team works “day and night”, the designers get involved with user testing, user feedback and tracking analytics constantly to improve the product.</p><h4>What we currently follow</h4><p>Since we work towards constant growth of the products, we seek feedback from the stakeholders who know about the users, problems and more from very near. For seeking feedback from the stakeholders we usually do:</p><ol><li>Constant catch up with them over products</li><li>Reviewing the product and pitching some new ideas to them</li><li>Sharing research or observation</li></ol><p>These feedback-seeking processes are good to have but what happens when small idea pops-up in one of the stakeholders mind? what happens when you don’t realise those small gaps in the products?</p><blockquote>To answer these questions, let’s get into the culture shift that has been taking place in the office environment and how we can evolve the feedback system with these culture shift.</blockquote><h3>The culture shift</h3><p>Early days were all about a cabin and the small world inside those cabins. with the slow culture shift we now mostly have the open spaces in the office which promotes the employees to interact more within the different teams, get more involved and together work for a shared goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04cmoqA-gIAesRtxdamq1Q.png" /><figcaption>Early days</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aFFiW_3O1O3GVXwjl_GisA.png" /><figcaption>The slow shift</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yIQwHOWowFcWYazzNKHBAQ.png" /><figcaption>An open culture</figcaption></figure><blockquote>An open office culture helps us all to work more collaboratively towards a shared goal. When it comes to a culture we have evolved to no one can stop us from eliminating even those little hesitation within the employees.</blockquote><h3>Evolving the feedback with culture</h3><p>With the shifting culture, we are now open to all the experiments in the world to make most out of it.</p><h4>The design wall</h4><p>As a part of this experiment, we came up with the concept of design wall which aims towards a better collaboration within the stakeholders to review and provide constant feedback over products.</p><blockquote>The design wall is a space where you put your design print outs (which you can change with every design update), this let the stakeholders visit those designs frequently and give feedback over it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*98usShI6aKmM7RdtRqURjQ.png" /></figure><h3>How does this work?</h3><p>Your ultimate goal is to collaborate with the stakeholders who can provide feedback over the product now and then, it can be a suggestion while walking through the wall or a serious discussion around the designs with multiple stakeholders. To do so you have to focus on the setup, which is the most important part of creating the design wall.</p><h4>The setup</h4><p>As the name suggests The Design <strong>Wall,</strong> here the set up of the wall is very important to think about while planning to create the design wall because that will define the success of your design wall.</p><p>For setting up the design wall you need to:</p><ul><li><strong>Decide the space - </strong>Select the space which is the most accessible by stakeholders so that they can focus on the wall whenever they are free or walking by it.</li><li><strong>Gather the tools -</strong> You need to look for sticky notes, markers, pens etc which allows stakeholders to put the suggestions up in the wall.</li><li><strong>Get the Designs - </strong>Get the printouts of your designs, please note that each screen should be separate print so that you can change the orientation and placement of the screens within the wall. the screens should move freely in your design wall as and when required. The print outs can be coloured (preferred) or black and white (if coloured printouts are not available with you and you need to quickly build or update the design wall)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Viw2L6s8Q6gmeXid3OUa-A.png" /></figure><h4>Post setup</h4><p>Post the setup is the time where your stakeholders are visiting your design wall and giving feedback over the product. When you start getting feedback it will be all worth it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IbZZTkBHnQZtxrx3KSsfXw.png" /></figure><h4>Tips on building the design wall</h4><p>While setting up the design wall your aim is always to set up the wall in a way to get the most feedback on regular basis without scheduling any meeting or doing email shoutouts, the small tips from my experience of setting up the design wall are:</p><p>💡 <strong>Be quick</strong> while getting the design up on the wall, don’t focus on how neat the printouts have to be or not limit yourself if you don’t have coloured print outs available. Treat it as an MVP at first and evolve the design wall slowly.</p><p>💡 <strong>Know your stakeholders</strong>, Focus on where your stakeholders are having maximum movement on the floor, whether it’s near a coffee machine or near the conference room (or inside the conference room). Remember your main aim is to make them have a random or focused conversation over the product.</p><p>💡 <strong>Let the flow be visible</strong>, don’t miss out on the flow of your designs or how the screens are interacting with each other. You don’t want the discussions or ideas coming out from the stakeholders to get blocked due to such reasons.</p><p>💡 <strong>Maintain the setup</strong>, while you have done all the setup but don’t forget to update the wall as and when the designs are getting updated and make sure that a pack of sticky notes and marker or pen is always available near your design wall so that you can get feedback constantly.</p><h3>Impact of the design wall</h3><p>When post-setup you will start getting feedback over the products you will see that more and more feedback has started coming from different stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xdlH36Gc51ZL2VHSma-Cvg.png" /></figure><p>You may see feedbacks going down at a certain point of time which is fine because whenever you update your design next, this graph will again go up! it’s a loop.</p><blockquote>Gather all the feedback, validate them, discuss them with the stakeholders and update the designs constantly.</blockquote><p>If you like the blog, please give some claps 👏 This will keep me motivated to write more in future. Enjoy building your design wall and gathering feedback, hope this blog was helpful for all looking towards gathering constant feedbacks from the stakeholders of the product.</p><p>📝 Save this story in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_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://usejournal.com/newsletter/noteworthy-in-tech/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee8150c6ad3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UAT — User Acceptance Testing]]></title>
            <link>https://medium.com/design-talkies/uat-user-acceptance-test-b56e0cecd49?source=rss-5489bdbafaa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b56e0cecd49</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Nainika Verma]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 12:27:35 GMT</pubDate>
            <atom:updated>2021-07-22T15:51:41.943Z</atom:updated>
            <content:encoded><![CDATA[<p>Planning a user acceptance test!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FnY48yV7kbOZuiNI1FkT1g.png" /></figure><h3>User Acceptance Test (UAT), Why do we need it?</h3><p>UAT is a technique which helps to evaluate a product by testing it on potential users. This way designers can see if their website or app is usable by the end-users. Usability testing is usually conducted at the UX building stage before a project goes to the development team. It allows changing inefficient solutions to be identified earlier rather than finding them in a complete product.</p><h3>Planning UAT? How &amp; What?</h3><p>UAT planning can be a quite tricky phase since there are several different methods available but it all depends upon who your users are, and whether they are available physically or remotely. There are many online tools available for the same, which you can <a href="https://medium.com/@sarahelson81/top-usability-testing-tools-for-your-website-a743d6039098"><strong>find in this link.</strong></a></p><p>Let me elaborate on the UAT method which worked for our context.</p><h4>1. Gather the participants</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wnd7B4il6amdKYw49Wb9zA.png" /></figure><p>Shortlist your participants well before you start planning for UAT, and inform them in advance about when you plan to conduct the UAT; coordinating between multiple users available can be a big task in itself. Give context to the users, and let them know what you are doing and why you are doing, make them feel that this product is yours and we need them for making it better, make them feel that their satisfaction is an essential part of your product.</p><blockquote>Remember to make them comfortable because the more comfortable participants will be, the better output they can give you, during the session.</blockquote><h4>Some points that you should consider 👇</h4><ol><li>Schedule and block participants time a week before you plan UAT. Ask them about their availability i.e are they available remotely or for one on one sessions. One-on-one sessions are more comfortable and hence preferred; in my case, the participants were only available remotely.</li><li>On average, schedule a session with not more than 5 different users.</li><li>Brief them the intent of the activity but not the activity itself.</li><li>If your participants are available remotely, then you will need to share your desktop/laptop screen with them, during the activity. Ask the participants the platform they are more comfortable with. A few platforms you can use for conducting the remote UAT are Google Hangout, Team Viewer, Skype etc.</li><li>Make sure you aren’t insisting the participants for a platform of your choice over their comfort. Install the platform well before the UAT and acquaint yourself with it, as you don’t want that last moment hassle and waste your time over it while conducting your UAT.</li><li>Remember that the 50mins session with your user is the only shot you have and to get the most of it, avoid every little thing that can create confusion.</li></ol><h4>2. Build your UAT team: A moderator and an observer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KkaasKK6xM68pU2x3y4KIg.png" /></figure><p>A moderator is the one who will drive the whole conversation with the participants and direct the participants to complete the task. An observer is the one who observes the users reactions, actions, pain-points and errors and notes them down for further analysis.</p><p>If you are a team of more than 2 people, take one of them as an observer in your sessions and let them observe your participant’s activity; as a UX designer, one must know how to get into the shoes of the user and feel their pain-points and happy journeys.</p><p>In our case, I had two more UX Designers from Delhivery design team 🙌</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eLrfjorAA6M7Ax1W3Kp7yQ.png" /><figcaption>Moderator and observers in UAT test</figcaption></figure><blockquote>Tips: Include your design team members in your UX activity, because firstly teamwork is always BEST and secondly, learning is a never-ending path and your team members and you can always learn something from each activity, which will make your team strong with the process. 🍭</blockquote><h4>3. Plan the protocols that you need for conducting a UAT — and conquer!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2OXto79YmhxBNo7BuFkj4w.png" /></figure><p>An essential part of the UAT is, you need to be prepared on what you intend to do during the session well before you start about the possible scenarios and the conversation you want to probe and hence the protocol; here is how I prepared myself for the same.</p><p>First of all, you need all the critical flows of your product which you want to test with your audience. As my product was a web panel for enterprise software, it was more UX driven hence I needed to more focus on the functionalities of my product.</p><p>‘How do I make it easy for the participants and for the designer to check on each every flow? here is what I did:</p><p><strong>1) Define scenarios: </strong>I divided each critical task into scenarios as scenarios allow us to get close to the participants daily tasks and make them perform the same more intuitively.</p><p><strong>2) Define multiple flows under a scenario: </strong>For my product, I defined 5 scenarios under which I had one or two flows where each of task flows could allow the participant to achieve the desired task (This will also help with observing, which flow is better for your audience)</p><blockquote>Tip: Do not overburden your participant with too many tasks, keep maximum of 4–5 scenarios so that they don’t feel exhausted and can perform the task with a fresh mind.</blockquote><p><strong>3) Test and observe: </strong>Moderators and observers become extremely important at this point; the moderator puts the participants into different scenarios while conducting a task, the observer assists. I used a scoring method for the different scenarios for my tasks, to evaluate the UAT i.e</p><ul><li><strong>+1:</strong> If the participant achieves the desired task without any help or indication it is positive for your design.</li><li><strong>0:</strong> If the participant achieves the desired task with some help or indication it is a 0 for your design.</li><li><strong>-1:</strong> If the participant is not able to achieve the desired task even with your help or indication it is a -1 for your design.</li><li>I planned to record the above tasks, screen-wise so that I can get to know in detail, which screen or step is a pain-point for the users to achieve the desired task.</li><li>A small remark section should be there so that observer can write down some extra points in case he/she observes anything missing or has a suggestion for example the reason behind not able to complete the particular task.</li></ul><blockquote>Tip: Let the participant speak out his pain-points, try not to interrupt the user in between as it can break his flow and you may end up not getting the reasons behind the pain-points and any logic that user wants to convey for not achieving the same.</blockquote><p><strong>d) Here is how I documented</strong> the above scoring for one scenario, starting by gathering basic knowledge of the participant of the UAT. Use the same document for different scenarios and use physical copies of the same. Make the observer use these copies to pen down all the observations of the user while performing a certain task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSXpfHs3bLhNOhJXMZr0nQ.png" /><figcaption>Protocol template for UAT</figcaption></figure><h4>5. Analyse and fix.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGhxMs3AIDBQf2Ri0eBHiw.png" /></figure><p>Finally! when you are done with all of your UAT sessions, it’s time to infer and analyse and try to solve the pain-points of the users, but how do we do it? How do we know which insights we need to focus more on solving, what are the additional suggestions we could build upon later? How much does the user like your product?</p><p>To answer the above questions, I divided my insights into 4 different parts and put them in each quadrant i.e <strong>User likes, Constructive criticism, Questions and Ideas.</strong></p><blockquote>For the analysis, gather your design team and PMs and discuss each insight. Be ready with a <strong>white board or a glass wall, some sticky notes, markers and your notes/document</strong>✏️</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JyBMAMNHQ1gQMEhu7eL0A.png" /></figure><h4>1) User likes</h4><ul><li>I started with what all users liked in my product (Starting with some motivation); this brings a level of confidence in you, your product and PMs</li><li>Note down the happiest journey of the users and why the participants feel that it is a happy flow for them.</li></ul><h4>2) Constructive Criticism</h4><ul><li>As the name suggests, note down points that users have a view for or there must be some points that your user has suggested at some point to improvise your flow, or where the user doesn’t completely agree with your design.</li></ul><h4>3) Questions</h4><ul><li>Note down all the questions that the user must have asked during the session.</li><li>Remember no question is small, so do not dismiss any question before you put it up on the wall.</li></ul><h4>4) Ideas</h4><ul><li>Take a break, and discuss all the three quadrants (What do the PM feel about these points, what do other designers think about these points, is there any blocker for these points? etc) before coming to this one.</li><li>Once you have discussed all the three quadrants with other designers and PMs, come up with the points that you need to solve now.</li><li>For all the pain-points that emerge, come up with quick fixes or ideas and put them in this quadrant.</li></ul><blockquote>Last Tip: Always keep your PMs , other designers and developers in the loop, during these analysis session, so that you know if these solutions are feasible and if everyone is on the same page.</blockquote><h4>In the end, UAT helped me with testing and coming up with new ideas to improvise my product well before the Development 😃</h4><p>Here is the summarised flow for UAT:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eOE5knYlFuCG7gsaCsL-Q.png" /><figcaption>UAT flowchart and important points</figcaption></figure><p>If you like this post, please give a clap 👏 This will keep me motivated to write more in future also I would like to say thanks to <a href="https://medium.com/u/c877a0f11172">Kshipra Sharma</a> for helping me with the blog. Enjoy testing your product, hope this is useful for all looking to conduct UAT for their products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b56e0cecd49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-talkies/uat-user-acceptance-test-b56e0cecd49">UAT — User Acceptance Testing</a> was originally published in <a href="https://medium.com/design-talkies">Design@Delhivery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Hackathon @Delhivery Where logistics meets design!]]></title>
            <link>https://medium.com/design-talkies/design-hackathon-delhivery-where-logistics-meets-design-d4880d656de9?source=rss-5489bdbafaa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4880d656de9</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[logistics]]></category>
            <category><![CDATA[delivery]]></category>
            <dc:creator><![CDATA[Nainika Verma]]></dc:creator>
            <pubDate>Fri, 11 May 2018 12:05:24 GMT</pubDate>
            <atom:updated>2018-05-17T08:20:09.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5kNjyCyGXTRt2mxie6gyg.jpeg" /></figure><blockquote><a href="https://delhivery1.wordpress.com/about/"><strong>We’re an in-house team of design ninjas at @Delhivery to make seamless products and holistic experiences!</strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUzfea2mWoDaELYFIZXMwA.png" /></figure><h3>Why did we conduct a Design Hackathon?</h3><p>Hackathons are a brilliant way to get teams to quickly come together and collaborate on building solutions. In a small time, teams can get focused work and new ideas on the table. An added element of competition gets the adrenal pumping, and adds a zing factor to everyday office routine.</p><p>At Delhivery, we have multiple internal products (used by our ground staff and client servicing teams) and external products (used by our clients); These products help us do everything, from initiating our point of service to providing an overview of the health of our operations, to tracking our inventory and handing it over to the consignees and for all these products, the most common experience is the Sign Up/ Sign In page.</p><blockquote><strong>Yes, I am talking about Sign In/ Sign Up page because as simple as it sounds and it looks, it is the first experience user make every day while engaging with our products.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CMq9hpPDmOEFXhkU." /><figcaption>“A red “enter” sign in the shape of an arrow with white light bulbs” by <a href="https://unsplash.com/@thedameintl?utm_source=medium&amp;utm_medium=referral">Lisa Walton</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Checklist made before conducting Design Hackathon within the team.</h3><ol><li>Make sure of the space where you are about to conduct hackathon, When it comes to UX designers all they need is a space where they can open there mind and bring the creativity out of them.</li><li>Make sure you have all the stationary that your team will be needing to avoid last moment rush.</li><li>Plan the Hackathon well before like: <strong>What questions may the participants want to ask to complete their work? What are the scope and limitations of the Hackathon? </strong>because trust me if you do not plan it well, it can become very complicated with the above questions.</li><li>Last but not the least, maintain the energy in room for the designers till the end, it will really help 💁</li></ol><h3>Planning the time!</h3><p>Yes, the most important think is how to divide the time for different task as we had a half day and we really wanted to keep it short, short, systematic and productive at the same time.</p><blockquote><strong>Planning is always one of the key element for success!</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G0BpEzoP1N6AZrbQ." /><figcaption>“Busy but orderly workspace with highlighted notes, a set square and a tablet” by <a href="https://unsplash.com/@quesada179?utm_source=medium&amp;utm_medium=referral">Javier Quesada</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Total time for Hackathon was 3 Hours:</h4><p>First 15 Mins is for briefing of the hackathon i.e Why, What and How? and Dividing the team (In our case we divided into 2 team of 3 people each) where we took 2.5 Hours to accomplish the problem solving with desired end result and last 15 mins to discuss the end result of each team (This time may vary as we had only 2 team)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gvOHXzXDzj-O2zu0YSpKhQ.jpeg" /><figcaption>Team A (Asif, Anulal and Kshipra)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ou1-snAcBGB3sFbjmkwH_Q.jpeg" /><figcaption>Team B (Avisek, Kanupriya and Nainika)</figcaption></figure><h3>The Outcome!</h3><p>We decided that at the end of 2.5 hours we will be coming up with the solution in a form of high fidelity invision prototype, yessss! because we love invision ❤ But actually it’s not only that we just love it but digital prototypes are the best way to experience a product of how it should finally be, without any help of code.</p><p><strong>(</strong><a href="https://blog.prototypr.io/14-prototyping-tools-how-each-can-be-used-1c804fab33a6"><strong>Here is the link to some of the prototype tools that you can go with</strong></a><strong>) Enjoy!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ajEwfYOqRiRMGlv1VagZxA.jpeg" /></figure><h3>Last 15 mins discussion, all fully enthusiastic to present our final results!</h3><p>In this last 15 mins, each team presented the invision prototype link to the each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqj_KdtWHpGS1owShRrBuA.jpeg" /></figure><h3>You can view our final outcomes here:</h3><ol><li>Team A Invision Link: <a href="https://projects.invisionapp.com/share/T2I8QAYPUZN#/screens">https://invis.io/T2I8QAYPUZN</a></li><li>Team B Invision Link: <a href="https://projects.invisionapp.com/share/Y6I9RVBDBMH#/screens">https://invis.io/Y6I9RVBDBMH</a></li></ol><h3>Now The Decision Time</h3><p>As we finished with the design, our next big thing was how to decide on the winners??? We thought of getting into a platform where everyone who works closely with the design team within the organisation like project managers, developers, operations team could cast their vote.</p><p>Well we are lucky enough to have workplace by Facebook ❤</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*ARJIFbVXiKBpltqNg-_30g.png" /></figure><blockquote>As <a href="https://medium.com/u/c548fe6bc926">Workplace by Facebook</a> says :Build a connected culture with familiar tools to help everyone turn ideas into action.</blockquote><p>This helps our idea of getting the votes turn into action with live counts going on and the sense of excitement was high throughout the days of vote.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eed8j9V5S64PzOIxZ6EIcA.png" /></figure><h3>Putting an end to the vote!</h3><p>Now that we are very near to the end of voting, here are few points that we need to consider while counting the votes coming up with what is best among the two:</p><p>The vote that is coming in is from different stakeholder such as project managers, developers, operations team and everyone have their own view behind giving the vote, like Developer might see that which design is easy to develop while project manages might see which one is more visually balanced but a UX designer also counts the usability of the product too and that is what our last 15 min discussion was all about.</p><p>So counting all these scenarios we decide to choose the one design out of two and used that Sign In/Sign Up page across all our products.</p><h3>Why do we need to do this among team?</h3><p>Hackathon creates a sense of confidence that each and every team member can perform a certain task within a time frame which actually boost our energy towards doing so.</p><p>and we actually see the results coming in from our each team member, the excitement, the energy and the quick ideas and it’s implementation made us believe that anything is possible the only thing we need is the motivation and dedication towards any task.</p><p>Since this was the simple flow of Sign In/ Sign Up which requires short time frame, I will surely share another blog where we will be doing it for much complex products and use case for which the time, the activity and the decision making might change, till then keep reading my other blogs 🍃</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>I hope this blog helps you in conducting hackathon, If you liked my blog please keep clapping 👇 and share the blog, This will motivate me in writing more in future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4880d656de9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-talkies/design-hackathon-delhivery-where-logistics-meets-design-d4880d656de9">Design Hackathon @Delhivery Where logistics meets design!</a> was originally published in <a href="https://medium.com/design-talkies">Design@Delhivery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>