<?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 Ayaneshu Bhardwaj on Medium]]></title>
        <description><![CDATA[Stories by Ayaneshu Bhardwaj on Medium]]></description>
        <link>https://medium.com/@ayaneshu?source=rss-15627566f41------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MKVrQCnv5QBBf-eNBJEfGw.jpeg</url>
            <title>Stories by Ayaneshu Bhardwaj on Medium</title>
            <link>https://medium.com/@ayaneshu?source=rss-15627566f41------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:06:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayaneshu/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[AI Tryouts — Tech Interview Practice]]></title>
            <link>https://ayaneshu.medium.com/ai-tryouts-tech-interview-practice-4de3a0f828e4?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/4de3a0f828e4</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Tue, 19 Dec 2023 13:57:46 GMT</pubDate>
            <atom:updated>2023-12-19T13:57:46.000Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI Tryouts — Tech Interview Practice</h3><h4>This article focuses on one such initiative, the development of an AI-powered tool designed for interview practice called — AI Tryouts.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuPXQ9V0xC1xKmuE8f2Ycg.jpeg" /></figure><h4>Overview</h4><p>Newton School is an ed-tech platform, building a futuristic online university to provide a highly immersive and interactive learning path to millions of students and enable them to tap into new-age tech opportunities.</p><p>I led the complete design process for AI Tryouts, one of our public products — a crucial element for testing AI capabilities in tech interview preparation. Moreover, leverage tryouts to attract and acquire new users.</p><p>Following its launch in June 2023, within four months over <strong>28,000 users signed up</strong> on the product. <strong>Got over 6,000 unique question submissions</strong>, with <strong>over 200 users completing all the questions</strong> and earning certificates.</p><h4>Exploring AI Products</h4><p>Following the release of Chat GPT, our team at Newton began exploring ways to assist users in integrating this technology. In the ed-tech space, a significant challenge was scalability, as tutors had to be human, and students relied on subjective feedback, often dependent on the tutor’s experience. The introduction of AI opened up new possibilities, offering students the opportunity for immediate feedback when incorporated into their workflows.</p><p>As a team, we explored areas where we could support students in their preparation. This article focuses on one such initiative, the development of an AI-powered tool called “AI Tryouts”, designed for interview practice.</p><h4>Problem</h4><p>An interview is a one-on-one verbal conversation that assesses various aspects of a candidate. In a tech interview, where questions are highly technical, the interviewee must articulate their answers accurately and speak with confidence to impress the interviewer.</p><p>Final-year engineering students and individuals transitioning to tech careers often struggled with confidence in their answers and faced challenges in articulating their answers effectively and even paid for interview practice, encountering subjective feedback with delayed responses based on the mock interviewer’s experience and schedule.</p><h4>Solution</h4><p>We developed an AI-powered online tool for tech interview practice, featuring a repository of questions asked in various companies. Users can verbally answer these questions and receive instant feedback. The tool evaluates their responses based on multiple parameters and provides feedback on their answer delivery along with suggestions for improvement.</p><h4>User Flow</h4><p>Users arrive at Tryouts through various channels, including ads and different mediums. Consequently, distinct entry flows are designed to cater to the diverse ways users access the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nM60ha7Yj2yMYjQIYRRPZw.jpeg" /><figcaption>User Flow</figcaption></figure><h4>The Landing Page</h4><p>I opted for a 2-column layout for the landing page of Tryouts, catering to both signed-in and non-signed-in users.</p><p>On the left, the hero section provides a brief description of the product offering, while on the right, users can find the selectable modules to practice questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zqTAY4uCPlCzklPYxbv61w.jpeg" /><figcaption>Landing Page for Tryouts on Web and Mobile</figcaption></figure><p>This layout was chosen as our target audience typically doesn’t scroll through the product extensively. Placing actionable elements in the first fold minimizes friction, making it easier for users to engage with the product.</p><h4>Module Page</h4><p>The module page features a list of questions within the module, providing users with the option to search for specific questions and filter them based on the topics they want to practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtA6seFKNGvWiE-uMpyobg.jpeg" /><figcaption>Landing Page for Tryouts on Web and Mobile</figcaption></figure><h4>Answering a Question</h4><p>Once the user selects a question, they are prompted to provide a verbal answer and grant microphone permissions for Tryouts. After recording their response, a transcript is generated. Users have the ability to make minor edits to the transcript and re-record their answer if they are unsatisfied.</p><p>Upon submission, the AI processes the response and provides feedback.</p><p>You can experience a demo yourself by following the link provided just below the case study title or take a look at the video below.</p><p>Try solving a question on<strong> </strong><a href="https://my.newtonschool.co/tryouts"><strong>AI Tryouts</strong></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZ73gS6XFiPM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZ73gS6XFiPM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZ73gS6XFiPM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4b5e541951dccfce6baa909ead6df63/href">https://medium.com/media/f4b5e541951dccfce6baa909ead6df63/href</a></iframe><h3>Impact</h3><p>Following its launch in June 2023, within four months:</p><ol><li>Over <strong>28,000 users signed up</strong> on the product.</li><li>We got<strong> over 6,000 </strong>unique question submissions.</li><li><strong>Over 200 users </strong>completing all the questions and earning certificates.</li></ol><h3>Scope for future versions</h3><ol><li>Currently, users are required to navigate back to the module page to select another question. However, we aim to enhance the user experience by enabling seamless navigation of questions and modules directly within the question page. This improvement is anticipated to further reduce friction in the user journey.</li><li>Users currently lack visibility into their previous attempts for a question. We plan to introduce a repository within the question attempts section, enabling users to review their previous answers and learn from their mistakes.</li><li>Looking ahead, our vision includes allowing users to select topics and difficulty levels, with a set of chosen questions grouped and presented as an interview.</li><li>As AI capabilities continue to advance, the future vision is to create an experience similar to an online interview, where users engage in conversational interaction with an AI interviewer, eliminating the need for manual question selection. <em>(This idea is still very far fetched)</em></li></ol><h3>Final Thoughts</h3><p>Navigating tight timelines presented a unique challenge for this project. Collaborating closely with my Product Manager, we aimed to deliver Tryouts within an ambitious 2–3 day window. The collaboration involved scoping out some features to effectively ship the product while leaving room for future enhancements, all while ensuring the overall integrity of user flows.</p><p>Experiencing the adrenaline rush of shipping within such a crisp deadline was a novel challenge for me. It highlighted the importance of efficient collaboration, prioritization, and making strategic decisions to meet project goals.</p><p>Thank you for reading this far✌🏻.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4de3a0f828e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Platform Navigation for Newton School]]></title>
            <link>https://ayaneshu.medium.com/improving-platform-navigation-for-newton-school-94aaab0763d5?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/94aaab0763d5</guid>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-flow]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Sun, 17 Dec 2023 11:43:42 GMT</pubDate>
            <atom:updated>2023-12-17T11:43:42.689Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EXyewObcQ7r49dnhqIZAPg.jpeg" /></figure><h3>Context</h3><p>Newton School is an Indian ed-tech startup that focuses on building a futuristic online university. Their goal is to offer a highly immersive and interactive learning path to millions of students, enabling them to tap into new-age tech opportunities. They achieve this by offering paid tech courses and providing free products for coding and interview practice for public use.</p><p>In my role, I initiated and led a comprehensive redesign of the entire product’s navigation, addressing a crucial element that was causing user friction at various stages.</p><p>After the launch of the new navigation across the product, there was a <strong>cumulative increase of 21% in discoverability and a 50% increase in footfall on public products. Also a staggering 30% decrease in drop-offs for the courses.</strong></p><h4>My Role</h4><p>Lead Designer — Feature Scoping, Research, Interaction Design, Prototyping, UI Design</p><h4>Team</h4><p>Vishwajeet Singh — Product Designer<br>Parv, Product Manager<br>Aman, Frontend Engineer<br>Swapnil Negi, Backend Engineer</p><h4>Timeline</h4><p>2 Months, <strong>Launched in August 2023</strong></p><h3>What exactly was the problem</h3><p>Concerns arose within the product teams as retrofitting new features into the existing information architecture became challenging with the growing complexities of features over time.</p><p>The team shared a consensus that a different product structure, both in terms of UI and backend, would enhance the impact of new features by allowing them to be positioned more strategically — an opportunity constrained by the current product structure.</p><p>Analysing the data and use calling revealed that users using the product were experiencing navigation-related challenges, often exiting their intended user flows due to mis-taps and dropping out of their courses.</p><h4>How our users were suffering</h4><p>With a substantial enrolment of over 2000 students spanning various courses, the context revolves around the challenges faced by users in effectively utilizing the product.</p><ol><li><strong>Navigation Challenges:</strong> Users found it challenging to navigate the product efficiently, hindering their overall user experience.</li><li><strong>Accidental Exits:</strong> Accidental clicks were a recurring issue, causing users to inadvertently exit their courses while actively involved in assignments or lecture sessions.</li><li><strong>Alternative Measures:</strong> In response to these challenges, <strong>many users opted for browser bookmarks</strong> and navigation as a workaround. However, this solution had a detrimental effect on the product’s overall usability and reliability.</li></ol><figure><img alt="Old Header used on the Newton School Platform" src="https://cdn-images-1.medium.com/max/1024/1*ki5YfRUUqVqvid23tqzWAA.jpeg" /><figcaption>Problems with the old Navigation</figcaption></figure><h4>How public products were affected because of poor navigation</h4><p>Newton School had developed five public products to cater to various needs, but they faced the issue of being largely undiscovered. Both enrolled and not enrolled, encountered when arriving at Newton’s platform through Google search:</p><ol><li><strong>Lack of Visibility:</strong> The convoluted navigation system rendered the five public products largely undiscovered, impacting their visibility on the platform.</li><li><strong>Restricted Awareness: </strong>Users, upon arriving via Google search, were confined to the specific product they initially sought. This limitation hindered their awareness of the broader range of offerings designed to meet diverse needs.</li><li><strong>Missed Opportunities:</strong> The existing navigation structure restricted users from exploring additional products that could potentially address other educational requirements, thereby missing out on valuable opportunities.</li></ol><h3>Finding Partners within the Organisation</h3><p>Up until now, all tasks were handled internally by the design team. It became crucial to garner support from stakeholders in the product and tech teams to bring this project to fruition.</p><p>When the design team presented them with data and user insights, they were convinced of the project’s value. However, a significant challenge surfaced — the project had yet to align with the organization’s business goals. At this point, I realized I had been solely focused on addressing user problems, overlooking the alignment with broader business objectives. Parv, the Project Manager at Newton School, brought this to my attention and assisted me in identifying the essential business goals that would pave the way for the successful implementation of this project.</p><h3>Aligning the Project with Business Goals</h3><p>Newton School aims to capitalise on the untapped potential of its 30,000 monthly coding contest participants who are eager to up-skill and seek mentorship. Despite their active participation, these users remain unaware of Newton’s comprehensive offerings, including AI Products, Paid Courses, and Free Courses.</p><h4>Objectives</h4><ol><li><strong>Enhanced Awareness:</strong> Increase awareness among the existing pool of 30,000 coding contest participants regarding Newton School’s extensive offerings, fostering a better understanding of available AI Products, Paid Courses, and Free Courses.</li><li><strong>Utilise Public Products as Acquisition Channels:</strong> Transform public products into effective acquisition channels to attract and engage users, encouraging them to explore additional offerings and services provided by Newton School.</li><li><strong>Revenue Growth: </strong>Anticipate a subsequent increase in revenue by leveraging the visibility and engagement generated through public products turned acquisition channels. This strategic approach aims to convert users into paying customers, thereby contributing to the overall financial success of Newton School.</li></ol><h3>Solution</h3><p>With these insights into the problems, we started our research, analysing other competitors and continuously talking to the users.</p><h4>Research</h4><p>Started the competitive benchmarking process to identify current gaps in Newton School’s user experience. Upon examining various competitors, I categorised them into the following segments:</p><figure><img alt="Image of Competitive Benchmarking done for designing the new header" src="https://cdn-images-1.medium.com/max/1024/1*FTVaR9XUfOzIhIhK7BO00A.jpeg" /><figcaption>Competitive Benchmarking</figcaption></figure><h4>User Calling and Idea Testing</h4><p>Over the course of a couple of months, I engaged with various users through calls to gain an understanding of their problems. Once I gathered concrete insights, I tested several ideas with the users and collected their feedback.</p><h4><strong>Insights</strong></h4><ul><li>Three out of four platforms feature a two-level navigation system comprising a <strong>primary top navigation and a secondary side navigation</strong>.</li><li>The top navigation includes globally relevant elements for switching between the courses, profile, gamification tokens, and Refer a Friend.</li><li>The left navigation primarily focuses on content within the courses.</li><li>The differentiation between L1 and L2 levels holds particular importance in Alma Better, Figma, and Jira, as it enhances content hierarchy recognition and intuitiveness.</li><li>Users encountered significant friction when attempting common tasks such as completing assignments or revising lectures.</li></ul><h3>Separating the Headers</h3><p>Following the research, <strong>we determined to implement contextual headers.</strong> This involves distinct headers for different contexts, including:</p><ol><li>Global navigation</li><li>Course-specific header</li><li>And a separate header for focused activities such as solving an assignment or watching a lecture.</li></ol><h4>Improvements in the Global Navigation</h4><ol><li>Introducing a UI element in the header, replacing the logo on the left. From which the users can switch between their enrolled courses and also find public products called “Switcher”</li><li>Putting the public products in the correct hierarchy in the header</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HSDdljVqYk5BF4soaqDeNA.jpeg" /><figcaption>Variants of Global Header</figcaption></figure><h4>Improvements in Course Header</h4><p>On average, a paid user at Newton School typically enrols in three courses: one paid and two free courses. To facilitate seamless navigation and prevent unintentional exits from the course, I replaced the Newton School logo with the Switcher, allowing users to switch between courses at their discretion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ctdzJ17XY5HFPtJig9vidA.jpeg" /><figcaption>Course Header</figcaption></figure><h4>The Switcher</h4><p>This new element, inspired by Figma’s profile switcher, displays all the courses a user has registered for. It also provides an option to navigate to any public product from a course, enhancing user flexibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*efWvAtdPP5Onp7aUotX7fQ.jpeg" /><figcaption>Switcher and it’s functionalities</figcaption></figure><h4>Task Specific Header</h4><p>Vishwajeet led the design for task-specific headers, focusing on major user tasks such as solving assignments, contests, quizzes, and revising lectures.</p><p>During a user’s engagement in a task, the aim is to simplify their navigation within the solving flow and prevent any unintentional exits from the task.</p><p>Two variants were designed and implemented for these specific purposes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wr5HSayiQxAf87Jc1khwEQ.jpeg" /><figcaption>IDE Header</figcaption></figure><blockquote>Currently, this task specific header is exclusively live for an experimental course named “EDGE,” an AI-assisted course that I will cover in another case study.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GD14VFTQ-RWtkZRyn_zRfw.jpeg" /><figcaption>Sidenav during tasks</figcaption></figure><h3>Impact and Matrices</h3><p>The overall impact of this project is broadly divided into three parts:</p><h4>Public Products</h4><ol><li><strong>3x increase</strong> in visits on Today’s</li><li><strong>73% increase</strong> in visits to AI tryouts</li></ol><h4>Course Navigation</h4><ol><li><strong>30% decrease</strong> in users exiting the course</li><li><strong>Users solve twice as many questions</strong> in one session in EDGE as compared to other courses.</li></ol><h4>Growth &amp; Revenue</h4><p>By increasing the visibility of our public products, we successfully converted four non-paying users into enrolled users, <strong>generating a revenue of approximately 10 lakhs</strong></p><h3>Learnings and Takeaways</h3><ol><li>While leading a design-centric project, gathering partners from the product and tech teams proved challenging. However, aligning more people toward the same goal significantly facilitated the task.</li><li>Redesigning the navigation for the entire product posed a unique challenge, considering a substantial user base already accustomed to the existing interface. Recognizing the potential disruption, I learned to version my design changes (not covered in this case study) to ensure a seamless transition for users.</li><li>Given the project’s scale, comprehensive documentation was imperative, covering initial insights, research findings, feature scoping, and maintaining a release log. Although challenging, collaborating with peers enabled us to achieve this extensive documentation.</li><li>Our research and discussions revealed the clear and crucial need for these changes, as they had a significant impact on key metrics.</li></ol><h4>Closing Notes</h4><p>Thank you for sticking around till the end. This project at Newton School ranks among the larger ones I’ve undertaken, and it has been a tremendous learning experience for me. I’ve grown in various aspects, from collaboration to execution.</p><p><strong>It required approximately 9 months of effort</strong> to persuade stakeholders and successfully launch the project. Designing in a Series B startup, I discovered, requires a significant amount of alignment — <strong>about 30% was the actual design work, while the remaining 70% involved discussions with stakeholders, convincing the founders, and coordinating with other teams.</strong> In the end, everyone, including myself, was delighted to see a positive outcome, making a meaningful impact at Newton School, even if it’s just a small dent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94aaab0763d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Toggle Dropdown — Experimental UI Component]]></title>
            <link>https://ayaneshu.medium.com/toggle-dropdown-experimental-ui-component-da9e9d9ff856?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/da9e9d9ff856</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[components]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Thu, 12 Jan 2023 13:08:58 GMT</pubDate>
            <atom:updated>2023-01-12T13:09:50.376Z</atom:updated>
            <content:encoded><![CDATA[<h3>Toggle Dropdown — Experimental UI Component</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6n3ugYgh55JhNp2A0XVTNA.png" /></figure><p>I may have bent some rules, but the end result was an innovative component for a design project on which <a href="https://twitter.com/jayjay_sama">Jasjeet</a> has been working on. Follow along as I unveil my creative process and the final designs for the component.</p><h3>Context</h3><p>We were building a leaderboard for the students enrolled in a course at Newton School. Students are ranked on the basis of proactiveness during the course, which is measured by the number of lectures attended, assignments, contests, and quizzes solved.</p><p>There are 2 types of leaderboards: a Monthly Leaderboard, where you get the ranking of the students for a particular month, and an All-Time Leaderboard, which is the summation of monthly scores of a student.</p><h3>Problem</h3><p>We needed a UI component to switch between the Monthly leaderboards and the All-Time Leaderboard.</p><h3>Solutions we tried out</h3><p><strong>Solution 1<br></strong>A Dropdown to switch between all-time and all monthly leaderboards. This solution was violating the hierarchy of all-time and monthly leaderboards, showing them in the same dropdown brings them on the same level of hierarchy and decreasing discoverability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*foyrV8lW51Qf9xIQruWkoQ.png" /></figure><p><strong>Solution 2<br></strong>A Tab group, All-Time Tab and a Monthly Tab with a dropdown. The problem with this solution was that the dropdown will only appear if the monthly tab is selected, this affects the discoverability of monthly leaderboards and the solution becomes less intuitive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*nnrqbeziuIkQgNAdi9-TQA.png" /></figure><p><strong>Solution 3 (Finalised approach)<br></strong>This is what I call a “Toggle Dropdown.” It’s a simple toggle between All-time and Monthly leaderboards. In the monthly leaderboard toggle, you also have a dropdown to select leaderboards of different months as shown below in the mockup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*3NbvtYyWwPRFuuf6q5yjcg.png" /></figure><p>To validate the final solution, I made a quick prototype and asked a couple of users to navigate between all-time and monthly leaderboards. And people were able to do so without any friction.</p><h4>Play around with the component here</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FjHeh9Rz5VQ62lbHBWhmuZg%2FToggle-Dropdown---Twitter-Mockups%3Fpage-id%3D1%3A330%26node-id%3D1%3A588%26viewport%3D-39%2C327%2C0.59%26scaling%3Dmin-zoom%26starting-point-node-id%3D1%3A588&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FjHeh9Rz5VQ62lbHBWhmuZg%2FToggle-Dropdown---Twitter-Mockups%3Fpage-id%3D1%3A330%26node-id%3D1%3A588%26viewport%3D-39%2C327%2C0.59%26scaling%3Dmin-zoom%26starting-point-node-id%3D1%3A588&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F8dd94474-e1b8-4e21-9ac3-1a10f2534b5b%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/bfb77d52c8d46e0078805dc03f74fb4b/href">https://medium.com/media/bfb77d52c8d46e0078805dc03f74fb4b/href</a></iframe><h3>Conclusion</h3><p>With the launch of this feature and toggle dropdown component, users now have the freedom to seamlessly explore the leaderboards on their own without any education. It&#39;s a definite win for me and a reminder that thinking outside the box can lead to innovation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da9e9d9ff856" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Music on Whatsapp]]></title>
            <link>https://medium.com/design-bootcamp/music-on-whatsapp-design-sprint-2020-f426104011ca?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/f426104011ca</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[whatsapp]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Sun, 10 Jan 2021 15:15:59 GMT</pubDate>
            <atom:updated>2021-01-13T07:38:47.701Z</atom:updated>
            <content:encoded><![CDATA[<h4>Design Sprint 2020</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RNb_0VfApUrNn_jyHm2arg.png" /><figcaption>Character inspired by <a href="https://www.instagram.com/ketnipz/">ketnipz</a></figcaption></figure><blockquote><strong>“If the feature needs an explanation, it’s not ready.”</strong></blockquote><p>Due to COVID-19 🦠 Pandemic, a nationwide lockdown was imposed, and we all were locked in our homes. It’s been a few months, and now we are missing those parties and late-night music sessions with our friends. Fighting over the volume 🎤, arguing over who plays the next track 🎸, suggesting songs, skipping to your favorite part, and singing together is something we all crave to experience with our friends, once again.</p><p>Everyone has grown comfortable in their own spaces, and the initial thrill of the imposed lockdown is not there anymore. Those long video calls 📱 with friends have now become irritating, and the motivation to be creative and efficient has diminished. But technological advancements 🪄 have helped us cope with this current situation till now and are continuously improving to fulfill user necessities.</p><h3>Context 🥸</h3><p>This is the documentation of a 12-day design sprint held by Design Studio, IIT Roorkee during the lockdown, <strong>April 2020 </strong><em>(before Facebook introduced Rooms)</em>. Here, we took up a problem statement and split ourselves into 4 teams <em>(Team names - Shree, Sanjay, Leela, Bhansali)</em> of 5-6 members, including students from 2nd-year to 4th-year.</p><p>We,<strong> Team Leela</strong>, collaborated virtually and provided a tangible solution for the given problem statement. We decided to follow the method described in <strong>“Sprint” by Jake Knapp</strong>. We did this simply because it was our first virtual sprint, so a tried and tested method helped us streamline the process.</p><h3>My Role 🤓</h3><ul><li>I helped in preparing the user interview questionnaire.</li><li><strong>User interviews —</strong> Every member talked to the target audience for the problem statement, learned about their problems, solution suggestions, and collected valuable insights.</li><li><strong>Competitive Analysis —</strong> Everyone in the team looked for two competitors and wrote down all the features that could be included in the solution.</li><li>I, along with a 4th-year student, finalized the user journey for the solution.</li><li>Wireframed and prototyped the solution.</li></ul><h3>Problem Statement for the Sprint 🤔</h3><p>Listening to music together with our loved ones is truly a precious experience, but unfortunately, amidst this global pandemic, we are stuck in our homes, and we all know that sharing Spotify/YouTube links isn’t enough.</p><p>The problem statement was to ideate a digital solution that helps the users recreate a similar experience of listening to music and communicating in a room full of people while staying at their homes, while clearly mentioning all assumptions.</p><blockquote>🛎🛎🛎🛎The Design Sprint Begins🛎🛎🛎🛎</blockquote><h3>Setting a long-term Goal 😏</h3><p>It’s crucial to know how everybody in the team has interpreted the problem statement. To bring everyone on the same page, a small exercise was conducted, and everyone was asked to write down 5 goals they wanted to achieve at the end of this sprint. Then, everyone was given 5 votes to vote for the most appropriate goal(s). By majority, 2 goals were shortlisted, which were combined to form the Long-term goal that we wanted to achieve:</p><blockquote><strong>“Enable the users to stream music together and allow them to communicate </strong>simultaneously<strong>.”</strong></blockquote><p>💡<strong><em>Pro Tip</em></strong><em> — We used </em><a href="https://miro.com/"><em>Miro</em></a><em> for all collaboration exercises, but now I’ll suggest using </em><a href="https://whimsical.com/"><em>Whimsical</em></a><em> because it’s faster, snappier and works smoothly even on low-speed internet.</em></p><h3>Defining a Target Audience 👥</h3><p>For limiting the scope of the solution, We decided to solve only for young adults.</p><p><strong>17–25-Year-Old</strong> — Young adults party a lot, and this lockdown 2020 has deprived them severely of peers and social interactions. They are tech-savvy and always willing to explore new things.</p><h3>Talking to Peers 🗣</h3><p>We prepared a questionnaire for the user interviews, which included the following questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*slY8iWe1qcjhWUsd4vEf1Q.png" /><figcaption>Questionnaire for the interviews</figcaption></figure><p>Everyone in the team talked to their friends, wrote down the users&#39; pain points and suggestions. We consolidated our interview data and gathered the following insights:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7SEEapTabKzw4xkC4GpdTA.png" /></figure><p>💡<strong><em>Pro Tip</em></strong><em> — Make the interviewee comfortable and avoid asking leading questions at the beginning of the interview. Slip your questions into the conversation and let them come up with the problems they are facing. Sometimes, users suggest outstanding solution concepts that can later be used in the solution after proper validation.</em></p><h3>Looking out for existing competitors 👀</h3><p>We decided to do another quick 1-day exercise and look out for existing products to solve this problem. Everyone was asked to write down the pros and cons of each product and present it in the next standup.</p><p>Here are the results of the competitive analysis:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d79OTD9AII_0JU-k91DFNA.png" /></figure><h4>Insights</h4><ol><li>The most <strong>common way of communication</strong> in all the platforms was exchanging <strong>text messages </strong>across that platform.</li><li>Many platforms <strong>streamed music and videos from third party software</strong>; majorly youtube and Spotify for songs.</li><li>Popular platforms <strong>preferred multiple contributors to the playlist</strong> instead of a single DJ dictating the whole party.</li></ol><p>💡<strong><em>Pro Tip</em></strong><em> — As a beginner, it’s very tempting to replicate existing designs and flows and be done with it, but as a designer, it is our responsibility to take a step back, refer to our goals and motives for the project, consult our teammates and course correct our processes.</em></p><h3>Sketching out possible solutions 🤯</h3><p>After a quick competitive analysis, everyone was asked to <strong>sketch solutions in the form of user journeys or pen-paper wireframe flows.</strong> It was a simple 6-hour task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVt2S-_dwHbiOqERBZPK1g.png" /></figure><p>Again, everyone was given 5 votes to vote the most logical and favorite flows they see fit. The top 2 flows were selected, and a more refined flow was developed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D1lW_uhWDc5MHAlHrCOuaA.png" /><figcaption>Ideated User Journey</figcaption></figure><h3>Curious Case—The Eureka moment 🧐</h3><p>After the final flow was made, we observed that this whole time:</p><blockquote><strong>“</strong>We were primarily trying to solve c<strong>ommunication and then trying to integrate a music co-listening experience to that.</strong>“</blockquote><p>We are trying to digitally recreate that nostalgic experience of listening to music in a room with a bunch of friends and enjoying the fun time together.</p><p>We thought, “Why not integrate a music sharing and listening experience in an already existing communication platform?” Upon researching, we found out that there were 3 major platforms that people preferred:</p><ol><li>Whatsapp</li><li>Instagram</li><li>Facebook</li></ol><p>Our target audience preferred group chatting and video calls on WhatsApp instead of doing so on Instagram or Facebook. Hence, we validated our assumption and found some statistics supporting the same:</p><ol><li><strong>One billion groups</strong> are in use on WhatsApp. <br><em>There won’t be any hassle of creating a new group every time someone needs to start a music party.<br>Onboarding friends in a party will be straightforward, as users do not have to switch between different platforms.</em></li><li>There are over <strong>340 million WhatsApp users in India</strong> alone and <strong>over 2 billion worldwide</strong>.</li></ol><p><strong>Hence, we concluded to develop a feature that provides a music co-listening experience in Whatsapp</strong>. This will also be solving the problem, including switching between apps, sharing an invite link on a communication platform, or calling someone up for a virtual party.</p><h3>Solutioning 😎</h3><blockquote>“WhatsApp approaches problems in a practical way. We try to design and build features that are obviously useful. <strong>If the feature needs an explanation, it’s not ready.</strong>”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJisu9eoFZE8HoFeqJrMqw.png" /></figure><blockquote>NOTE: This solution is for Whatsapp Groups only.</blockquote><h4>A few assumptions we made while designing</h4><ol><li>Songs can be streamed on WhatsApp using a Youtube API.</li><li>Every user has a google/youtube account and youtube installed.</li><li>Whatsapp calls and video calls will be disabled for the people attending the party.</li></ol><blockquote>Say heyyyy…say hoooo, let’s start the party!!!</blockquote><h3>Creating a Party 🎸</h3><p>Imagine that room full of friends, vibing on the songs played by those in-house DJs with everyone suggesting their favorite songs.</p><p>We recreated that similar scenario on WhatsApp. So, when a person creates a party in a group, he/she becomes the <strong>DJ who can add/remove songs from the playlist. Others, who join the party, will join as attendees and will only be able to vote on the songs.</strong></p><p>The group’s chatting interface splits into 2 parts:</p><ol><li><strong>Chat — </strong>This is the usual chatting interface containing all the text, images, videos, etc.</li><li><strong>Party — </strong>This section contains all the songs being played and the music player as well.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fowj3cQtxXg4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dowj3cQtxXg4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fowj3cQtxXg4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7404e99979c30bad89b20300d2ad7ba/href">https://medium.com/media/a7404e99979c30bad89b20300d2ad7ba/href</a></iframe><p>For sorting the Playlist, there is an <strong>UPVOTE</strong> option. Everyone in the party will be able to vote on the song they want to listen to. The most upvoted song reaches the top of the queue and will be played next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z-ALhdZqZ7QFccjQSxfWPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tVs4llUyRfslCWaeUJda9Q.png" /><figcaption>Different UI states of the song card</figcaption></figure><p>A DJ can add more DJs to contribute to the playlist and the vibe🤘🏻.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnTUoAnX6o9o%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnTUoAnX6o9o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnTUoAnX6o9o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f6e7d29671a8094f9325f74ca1b4ab6/href">https://medium.com/media/1f6e7d29671a8094f9325f74ca1b4ab6/href</a></iframe><p>A DJ can remove the songs by:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5PYcNQpRDF8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5PYcNQpRDF8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F5PYcNQpRDF8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9709d8c0ed8a6fda9b968d79461815e7/href">https://medium.com/media/9709d8c0ed8a6fda9b968d79461815e7/href</a></iframe><h3>Joining a Party 🎉</h3><p>You can join the party from the chat itself.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FS56DmtThiY8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DS56DmtThiY8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FS56DmtThiY8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/33192606ae3ea3f12c1fed826dfa205e/href">https://medium.com/media/33192606ae3ea3f12c1fed826dfa205e/href</a></iframe><p>The play/pause and skip songs button will be <strong>disabled for the attendee</strong>, as this is a real-time experience, and <strong>only the DJ can play/pause or skip the song.</strong></p><p><strong>Reason </strong>— These access rights for the DJ and the attendee are similar to that of Admin and Group members, respectively, to avoid nuisance in the party and destruction of the vibe🤘🏻.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VctfVvJawSFga-MOize7RQ.png" /></figure><h3>When does a Party end</h3><ul><li>As soon as the last member exits the party room, the party ends automatically.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yqZJJ2Z7CNkyYItT9WD1aA.png" /></figure><ul><li>When all the songs in the playlist are finished, and the DJs are not adding more songs, the party ends after a timer of 5 minutes. <em>(We were not able to validate the time after which the party ends.)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qd55Bm56zLE9yNvYsQLv_g.png" /></figure><h3>Communication during a Party</h3><p>We restricted ourselves to text chats only and avoided video calls and phone calls as WhatsApp restrict the number of video call/call attendees to only 8. Another reason for the same is to handle the volume of individual members and their music, similar to discord.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFT_-kcGBPHQJDrPP0DquA.png" /></figure><blockquote>We restricted ourselves because we aimed to deliver a minimal function solution that allows the users to communicate and does not hamper the music co-listening experience at the same time.</blockquote><h3>Explorations</h3><ol><li><strong>The position of the Music Party icon on the app</strong></li></ol><p><strong>Final Position </strong>— We decided to place it in the pin bottom sheet.</p><p><strong>Reason </strong>— Whatsapp is a communication platform, and the pin bottom sheet has the plugins for the chat, so the hierarchy of music party fits this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eb_NfrDBXxvOoPDsGosOXQ.png" /><figcaption>Probable positions to start a party</figcaption></figure><p>2. <strong>Party Room — Position of the party room as a tab or within the chat.</strong></p><p><strong>Final Position</strong> — We decided to create a separate tab for the music playlist.</p><p><strong>Reason</strong> — We chose to go with separate tabs because it eases the switching between the Chat and Party so that one can simultaneously text and vote on different songs seamlessly. In this way, we were able to simplify the overall design for the music listening experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*06emQ0lQD1SV6d3VJVaTgg.png" /><figcaption>Probable position of party Tab</figcaption></figure><blockquote>A validation to our solution is when Facebook introduced rooms for all the platforms; Instagram, Whatsapp and Facebook.</blockquote><p>This Design Sprint happened before my internships at <a href="http://vernacular.ai/">Vernacular.ai</a> and <a href="http://procol.in/">Procol</a> in this lockdown. I’ve gained a total of 9 months of industry experience and have a more definite idea of how products actually function. So, now that I’m documenting this project, after the introduction of <strong>Facebook Rooms </strong>and using apps like <strong>Discord</strong> to it’s fullest, I got a chance to take a look at it from a fresh point of view, and I realized that:</p><h3>Future Scope</h3><ul><li>Video calls can be incorporated into the music co-listening experience during a party with an option to control each individual’s volume separately.</li><li>There can be more ways to add songs to the playlist (directly from the chat, perhaps). So, suggesting and adding songs to the playlist can be improved upon in the next versions of the solution.</li></ul><h3>Where will my solution fail</h3><p>The current voting mechanism might be confusing for first-time users. So it also joins the list of features that can be improved upon in the next versions of the solution.</p><h3>What more this solution is serving</h3><p>This feature can also accommodate the larger and more diverse userbase, with the increased number of participants up to 256 people in a Whatsapp group. There can be many edge cases that need to be solved, but I think this solution covers a major chunk of the userbase and their needs.</p><h3>Success Metric</h3><ol><li>Number of unique users accepting the invite to join the Party</li><li>Number of Parties created</li><li>Total Session Time</li><li>Number of Upvotes in a session</li><li>Number of songs added in a session</li></ol><h3>Concluding Thoughts🤠</h3><p>I feel that we, as a team, did an outstanding job in reaching the final solution. There were many ups and downs during the whole sprint, and the process was not as smooth as it appears in this article 🙃 , but overall this sprint was a great learning experience. We rejected a lot of good ideas during the process and adopted various methods, and modified the existing processes mentioned in <strong>“Sprint”</strong> according to our needs to streamline the whole collaboration experience.</p><p>I agree with the fact that “there is always a better solution than the existing one,” and so does this solution as well <strong><em>(Facebook introducing rooms)</em></strong>. But I’m delighted with the effort that the whole team put into this sprint to provide a satisfactory and well-thought solution in the given time-frame.</p><p><em>Thank you so much for reading. Suggestions are always welcomed! If you want to chat or feel like doing random design jams, music jams, or photography talks, feel free to ping me on </em><a href="https://www.linkedin.com/in/ayaneshu-bhardwaj-73525917b/"><em>Linkedin</em></a><em> or DM me on </em><a href="https://www.instagram.com/ayaneshu/"><em>Instagram</em></a><em>.</em></p><p><em>You can also mail me at </em><a href="http://ayaneshu@gmail.com/"><em>ayaneshu@gmail.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f426104011ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/music-on-whatsapp-design-sprint-2020-f426104011ca">Case study: Music on Whatsapp</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: The voicebot mechanic]]></title>
            <link>https://medium.com/design-bootcamp/a-voicebot-or-a-chatbot-or-maybe-the-best-of-both-ux-case-study-a0382d7c881?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0382d7c881</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Fri, 14 Aug 2020 10:59:08 GMT</pubDate>
            <atom:updated>2021-01-14T00:54:01.893Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong><em>Brief:</em></strong> This is a UX Case study of a project which I completed as part of a 6-day design sprint during my internship at <a href="http://vernacular.ai/">Vernacular.ai</a>, where I was asked to deliver a digital solution to speed up the process for testing voicebots.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42lrlywFf1vE2yr_GTIhnQ.png" /></figure><h3>Context</h3><p>Vernacular.ai is an Indian AI-First SaaS startup with two products, VIVA (Vernacular Intelligent Voice Assistant) and VASR (Vernacular Automatic Speech Recognition), both being used together for automating call-centers for their clients. Vernacular’s mission is <strong>to transform the customer experience with Voice AI.</strong></p><blockquote>They believe that values shape the culture of the company and the cultural fit always comes before the skill sets.</blockquote><p><strong>The Console </strong>is a one place solution for creating conversational flows, monitoring, and collecting data for improving the voice bots. It is basically a web-based tool used by Vernacular.ai’s team. A small change in the Voice bots ML model can lead to multiple outcomes, so testing becomes an essential practice that needs to be followed to keep everything intact and working.</p><h4>What are Voicebots?</h4><p>Voice bots are software powered by artificial intelligence (AI) that allows a caller to navigate an interactive voice response (IVR) system with their voice, generally using natural language. Callers don’t have to listen to menus and press corresponding numbers on their keypads. They speak to the IVR in a simplified simulation of a call with a live operator.</p><p>At Vernacular, the <strong>call flow or particular conversation states </strong>was tested by making a call on a number assigned to a specific voice bot. Around 80–100 calls were done per day by a single caller, which averaged around 58sec per call. Then the faulty calls were reported via tracking the call on another interface, called <strong>Call Reporting </strong><em>(We’ll talk about in another article)</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LttQogzQJyV-od3DLWypEA.png" /><figcaption>Process of testing a voice bot</figcaption></figure><h3>The Design Process</h3><p>Amit Manchanda (aka Manchi) and I took part in a 6 days sprint to complete the design for this project. The process we followed is as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*feaEAYutujBJ20w8zZgFtg.png" /></figure><p><strong><em>Now Let’s dive into the Process!!!</em></strong></p><h3>Identifying Problems</h3><p>The current process was very tedious and time-consuming. Voice Bots required regular testing because even simple and small changes in the ML model can sometimes lead to catastrophic failures<em>(Butterfly effect)</em>. So, a caller made about 80–100 calls per day. The process needed urgent simplification because there were new conversational flows built very frequently for different clients(organizations), and the efficiency of testing the calls and reporting the faulty ones was declining.</p><p>So, the major problems identified were:</p><ol><li><strong>High Frequency of calls-</strong> While testing for one particular conversation state, the caller had to call again and again and perform the same steps every time to reach that state and check it.</li><li>The Call-duration was long <em>(Avg. 120 sec).</em></li></ol><h3>Specifying Goals</h3><ol><li>To remove telephony dependency.</li><li>Faster testing and data generation.</li><li>And reporting all the faulty conversation turns during the call.</li></ol><h3>Proposed Solution</h3><p>Create a web-based service within Console that can mimic the calling experience and increases the flexibility for testing the call flow and a particular conversational turn repeatedly within one call.</p><h3>Job Stories</h3><p>As the product was for internal use only, so the users were well within reach. But we decided to make <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27">Job Stories</a> instead of making User personas and user stories because this was faster and for the sake of exploring more into <a href="https://uxdesign.cc/8-things-to-use-in-jobs-to-be-done-framework-for-product-development-4ae7c6f3c30b">Jobs Theory</a>. And what could be better than using this in a sprint and testing the pros and cons for the same!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s6xcjr8LjN793oWq.png" /><figcaption>A Job Story Format</figcaption></figure><ol><li><strong><em>When</em></strong> I make a call, <strong><em>I want to</em></strong> loop into one conversational state <strong><em>so I can</em></strong> test it repeatedly.</li><li><strong><em>When</em></strong> I make a call, <strong><em>I want to</em></strong> loop into one conversational state <strong><em>so I can</em></strong> report the incorrect intents predicted by the ASR(Automatic Speech Recognization).</li><li><strong><em>When</em></strong> I’ve answered the voice bot, <strong><em>I want to</em></strong> know the predicted intent <strong><em>so I can</em></strong> report that conversational term there and then if it is faulty.</li><li><strong><em>When</em></strong> I make a call, <strong><em>I want to</em></strong> select the language and version for the voice bot so that<strong><em> I can</em></strong> conduct more tests.</li></ol><p>These were the 4 Job Stories we listed to ideate the features for the MVP version.</p><blockquote>“Let’s not turn this into a chatbot.”</blockquote><h3>The Important Decision</h3><p>We decided <strong>not to use text input</strong> to communicate with the voice bot on the interface because then eventually it would have become a chatbot, which we never intended. So, we decided to take <strong>voice as an input </strong>from the user and read the bot’s output. The bot’s output will be primarily textual, but there is an option to play the prompt as well.</p><p>Reasons for doing this was:</p><ol><li>We wanted to mimic the on-call experience using an interface.</li><li>If we would have enabled the text input option, we would have assumed that the ASR was working perfectly and no improvements were needed there.</li></ol><p>This decision helped us in creating a new and faster experience, where the user could speak the queries and read the bot’s prompt.</p><p><strong><em>This was the decision that helped us bringing the average call duration from 120sec to 90sec per call.</em></strong></p><h3>Ideation and Validation</h3><p>Manchi and I came up with the solution during brainstorming sessions but at the same time, we have doubts about the functionality and feasibility of the solution. So we approached the engineering team and discussed the solution with them; after their approval, we started with the wireframing for the MVP version.</p><h3>User Journey</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ERnG_XrhdBPc5WppAG5jww.png" /><figcaption>General User Journey on the Sub-Testing Interface</figcaption></figure><h3>Prototype</h3><p>Due to time constraints and code limitations, not much emphasis was given on the UI, which surely needs to improve, but the Sub-Testing service has become functional. And this MVP version was shipped for people to use, test, and give feedback for reducing even more friction in the process.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYXLuFz4-ORM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYXLuFz4-ORM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYXLuFz4-ORM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4adfe43f1beb5fbd632312ae12794e78/href">https://medium.com/media/4adfe43f1beb5fbd632312ae12794e78/href</a></iframe><h3><strong>So, What changed?</strong></h3><p>We got a really good response after we did the demo for the MVP version of the Sub-Testing interface and people within the team, who used to regularly test voice bots, started using this service present within Console immediately after it became functional.</p><p>Some stats we collected:</p><ul><li>We managed to reduce the avg. call time from 58sec to 33sec.</li><li>We saved up to 1 hour per day for the people who tested the voice bots, so now they can utilize this extra time to be more productive.</li><li>And the rate of data generation and collection improved significantly.</li></ul><h3>Learnings</h3><ul><li>We got a hands-on experience using Job Stories.</li><li>Being a UX designer, you want to provide the best experience to the user, but sometimes making the product functional and running becomes a priority. So, few compromises need to be made to provide the deliverables, and that’s what Product Design is all about.</li><li>It was a new experience designing for an AI-based startup because I needed to take into account the uncertainty of what the voice bot predicted, the outcomes differ every time even for the same input.</li></ul><p>Also, working closely with <a href="https://www.linkedin.com/in/a2tm7a/">Amit Manchanda</a> (Associate Product Manager at Vernacular.ai) was an excellent experience. I have enhanced myself in understanding the broad spectrum of design, thinking about the limitations, and asking the right questions.</p><p><em>Thank you so much for reading. Suggestions are always welcomed! If you wanna chat or feel like doing random design jams, feel free to ping me on Facebook or DM me on Instagram @ayaneshu</em></p><p><em>You can also mail me at ayaneshu@gmail.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0382d7c881" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-voicebot-or-a-chatbot-or-maybe-the-best-of-both-ux-case-study-a0382d7c881">Case study: The voicebot mechanic</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Vernacular.ai is Selling…]]></title>
            <link>https://ayaneshu.medium.com/experience-vernacular-ai-is-selling-af9c6be056d0?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/af9c6be056d0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[internship-experience]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Thu, 13 Aug 2020 15:48:12 GMT</pubDate>
            <atom:updated>2020-08-13T15:48:12.436Z</atom:updated>
            <content:encoded><![CDATA[<h3>Experience Vernacular.ai is selling…</h3><h4>First work from home experience as a Product Design intern</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FzU7J2Ec3co7soxpPUnRIw.jpeg" /></figure><h3>Preface📦</h3><p>In the scenario of 2020, where everyone is discovering new ways to deal with the lockdown and trying to improve themselves, I got an opportunity to virtually intern at <a href="http://vernacular.ai/">Vernacular.ai</a> as a Product Designer.</p><p>This article sums up my journey as an intern, including the perks of working from home, challenges I faced during the internship, the team culture, my routine, and my learnings.</p><p>So let’s begin…</p><h3>My Virtual Intro👨‍💻</h3><p>Vernacular.ai is an AI-First SaaS startup with two products, VIVA (Vernacular Intelligent Voice Assistant) and VASR (Vernacular Automatic Speech Recognition), both being used together for automating call-centers for their clients.</p><p>I joined Vernacular for a 3 months internship in May 2020 as the team’s 33rd member. After a few onboarding sessions, I understood the basics, got comfortable with the people, and settled down with a routine.</p><p>For the first couple of weeks, I learned the basics of Machine Learning — which was damn exciting, to get familiar with the jargon used within teams, and gradually began contributing to various projects. Here, I majorly worked on the Product called <strong>Console</strong>, which is a web-based tool used internally to maintain and train Organization(Client) specific Voice-bots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewHkQ-oAaaXWUliQ1UG71A.jpeg" /><figcaption>Team Meetings on Zoom</figcaption></figure><p>I felt a lot of responsibility on my shoulders as I knew that I was the only designer in the team. But still, I tried to live up to the expectations and deliver what was asked of me. The ownership startled me at first, as the changes I was going to suggest or make were to get implemented, and a lot of people within the team would be using those interfaces, but I took up the challenge.</p><h3>Weekly Routine⌛</h3><p>My day started with a daily Product Team Sync-up at 11 am and marking my presence for the day on a Slack channel called “check-in✅.” In the sync-up, everyone gave updates on what they had done a day before and tasks they would do that day. After the updates, if there was anything to be discussed, it was done there in the sync-up only.</p><p>Being stuck at home, it was easy to lose track of time…and even days (believe me!!!), so my reporting manager, <a href="https://www.linkedin.com/in/pravj/">PravJ</a>, asked me to fill up a Daily Journal, in which I mentioned all the things I did a day before. It was a good exercise as it helped me and PravJ to keep track of my work and progress. I’ll also recommend this to everybody reading this article, in general.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GiMasHkphLWM9ek4k4T4cA.jpeg" /></figure><p>There were a few sessions that were fixed for particular days and times:</p><h4>Monday🤯</h4><p><strong>Team meeting 👥(1 pm)</strong> — A meeting for all the members, with different teams delivering team reports and introducing new joiners. While others on the video call waited for people to join, there was a brief and friendly leg-pulling session every time.</p><h4>Friday😌</h4><p><strong>Cafe Rant 📢(5 pm)</strong> — Ahhaa…this session was fun, people spoke about the problems they faced but in the form of a rant. I usually sat with my guitar and heard people ranting about different issues.</p><p><strong>Product Read 📖(6 pm)</strong> — This was a productive session where people shared what they have read, related to product design/management.</p><h4>Saturday😎</h4><p><strong>Weekly sync-up 💬(1 pm) — </strong>This was a one-on-one session with Pravj. We discussed the blockers I faced during the work, sometimes he took suggestions about streamlining different processes within the organization, and I gave updates on my long-term projects.</p><p><strong>Product releases</strong> were the things I waited for because I got to see my designs functional and being used. A demo of the interface was given by a member of the Product Team to all the people in the organization. Sometimes I worked on Sundays too (few perks of working from home) to complete few pending tasks or extra work that needed to be done from the design end, so that the timeline stayed intact.</p><h3>People &amp; Culture🗿</h3><p>Vernacular is a tech-driven startup that primarily needs to focus on improving the Voice-bots, which is their flagship product. So, not much emphasis was given on design earlier, which was valid in its own ways. But now things have begun to change. Design also became a valuable aspect, not only to increase user efficiency but to provide them with a better experience while using the tool — <strong>Console</strong>.</p><p>Even though this was a virtual internship, I interacted closely with a lot of people. My suggestions were valued, which helped me gain tons of confidence. People here were very talented — many loved gaming, some T.T., and some love playing guitars. Unfortunately, I was not able to interact with them all.</p><p>But there were a few fantastic people I interacted with throughout my internship:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lEL2ojdH9HEND2rlMfejGg.png" /></figure><ul><li>Pravj — He was my reporting manager for the internship and the leader of the Product pack. Few people like to call him the Zen God of the company.</li><li>Manchi — One of the coolest in the organization and always up for fun chats and quality feedbacks.</li><li>Lord Sarin — I worshiped (worked with) him for a month, and he rewarded me when he turned on his Video on the call. I have another tiny wish LORD, Let’s grab a beer when I come to Banglore soon.</li><li>Vipul — He is the instrument shop owner at vernacular and a super talented person.</li><li>Shraddha — Our beloved H.R., dullness stays away from her, but she’s an awful secret-keeper.</li><li>Kanika — I’m sure her teachers always had one complaint about her that she is a super-talkative, hyper-energetic kid.</li><li>Snigdha — She created an aura of being super-serious, but it turned out to be a hoax. She’s a funny person who loves ghewar (Rajasthani Sweet).</li></ul><h3>Cultivating Habits🚜</h3><h4>A. Reading📜</h4><p>Reading has and will always be an essential aspect of personal and professional growth. In the earlier phase of my internship, I read a lot of Machine Learning stuff for efficiently communicating with the team(s). During the day, I took out at least 1 hour for reading various articles and blogs mostly related to tech and design, and I tried to implement the learning in my work.</p><h4>B. Interpersonal Skills🗣️</h4><p>This took a while…but I learned it…phew…. In the beginning, I was a bit hesitant to communicate with others, which limited my interaction within the organization. This happened majorly because <strong>I was not used to talking to a blank screen</strong> ( 😑 P.S.: Corona! I hate you.). I slowly overcame this and started reaching out to people directly. This helped a lot, I made a lot of friends, and in the later phase of my internship performed in front of a crowd of 62 people on a Zoom call🎸.</p><h3>Blockers and Solution ⚠️🧠</h3><p>Undoubtedly, work from home comes with a lot of conveniences. It saves us travel time. We can work within our own comforts of home and can take breaks whenever we like. No rules are applicable. But, it also comes in a package inclusive of some demerits. Disruption of my sleep cycle is just one, to begin with. Limited interaction with peers, lethargy, procrastination, and this list kept on piling up with each passing day. I hadn’t experienced such a prolonged period in this setting. I was new to it but still learned to find my way out from such road blockers in my way of success.</p><p>Here are a few major blockers that tried to drag me away from work but I came back again and again and again<em>(*dramatic music plays🥁)</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c6fiOd0VmpkSfPWo8GzCQQ.jpeg" /><figcaption>Working my way through — doodling things out</figcaption></figure><ul><li><strong>Delay in work because other people were busy🚧</strong> — I mostly worked with a colleague with much experience and in-depth knowledge about the project I was working on. Mostly, he helped me find my way out in times of difficulty and was the one validating decisions for the project. Sometimes, their work would keep them so occupied that I didn’t really get the chance to discuss my progress. It slowed down my project a bit. To find a way out, I tried to figure out things that I could handle on my own and started working on those and also made progress in the long term projects in the meanwhile. This helped me save my time and improved the progress that I made. I also worked on the long-term project and made progress there.</li><li><strong>Being the lone Designer in the organization💂</strong> — Being the lone designer in the company worked as a blocker as well as an opportunity for me to grab. Not being able to consult someone belonging to the design domain, was definitely a blocker for me. This deprived me of necessary and adequate feedback, ways to improve, and a guidance source. To justify how it was an opportunity for me, I took the ownership of demonstrating the whole company various prospects they were missing out on. I had a golden chance to create a whole ecosystem there. To deal with this situation, I used to critique myself a lot, I used to call up various seniors in other organizations to guide my way through it. Such experiences bring great learning, and you tend to grow a lot in the field. Taking ownership isn’t easy, but I managed to pave my way out. My managers were pretty happy with my progress and praised me for the amazing job I was doing.</li></ul><h3>Learnings and Skill Acquisition📚</h3><p>Although there wasn’t a designated Design team as such, this experience helped me immensely to grow as a Product Designer. This happened due to a couple of reasons:</p><ul><li>The people in the Product team helped me get answers to all my questions on the projects I worked, no matter how silly they sounded.</li><li>They course-corrected me whenever I got a bit distracted.</li><li>The interfaces I designed became functional, and people started using them, so I was able to collect data and funnel the information accordingly, to improve the designs further.</li><li>I did not shy away from asking, sometimes I even took the help of my college seniors wherever I got stuck, and they guided me along every time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Taaf9fdN3BVD0UOw94pkEQ.jpeg" /></figure><p>I learned to articulate my thoughts as I was allowed to write <a href="https://medium.com/@uxpin/how-to-write-a-painless-product-requirements-document-508ff6807b4a"><strong>PRDs — Product Requirements Document</strong></a>, for projects I was working on, which were later reviewed and refined by the Product Managers. This was a good exercise because it happened quite often, and as a designer, one must learn to articulate the design decisions and process for other team members to understand.</p><p>I explored a complete new theory called <a href="https://uxdesign.cc/8-things-to-use-in-jobs-to-be-done-framework-for-product-development-4ae7c6f3c30b">Jobs To Be Done (JTBD)</a> <em>[Good article -must read],</em> which was applicable in design and also in other aspects of the business. This theory helped me to look at a product from a completely different angle. There was still a lot to be explored but we, as a team, tried to use this as an experiment and got some pretty good results in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*61GKLWoOAganDgg1pZ2eKg.jpeg" /></figure><p>My work was broadly divided into <strong>Long term and Short term</strong> tasks; The long term tasks comprised of building a design system for Vernacular and re-structuring Console to incorporate new features in it. The short term tasks consisted of designing new services that were in the pipeline and upgrading the current version of existing service with Console.</p><h3>In the End…🛣️</h3><p>There is still a lot to say, but I guess I’ll wind up this article here and say that this internship was a fun experience. I enjoyed working here, learned to handle the pressure of ownership, enjoyed all the fun talks, and everything the company had to offer. However, I wished for an in-office experience and not communicating with people on a black screen.</p><p>I improved a lot, not only in terms of my skills but as a person too. I also learned to discipline myself when no one was checking, and I devised ways to deal with different blockers and even learned a bit of guitar🎸 and singing🎤 along the way.</p><p>A big Thanks to the people at Vernacular.ai for such an amazing experience…🙏🏻🙏🏻🙏🏻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af9c6be056d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading ODIN — Product Design Winter Internship 2019 at Wheelseye]]></title>
            <link>https://ayaneshu.medium.com/upgrading-odin-product-design-winter-internship-2019-at-wheelseye-56176a748e2f?source=rss-15627566f41------2</link>
            <guid isPermaLink="false">https://medium.com/p/56176a748e2f</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ayaneshu Bhardwaj]]></dc:creator>
            <pubDate>Mon, 06 Apr 2020 07:08:35 GMT</pubDate>
            <atom:updated>2020-12-19T17:48:34.526Z</atom:updated>
            <content:encoded><![CDATA[<h3>Upgrading ODIN — The Marketplace Cerebrum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_g3baG5hpvo2FjERFVRR8g.jpeg" /></figure><h3>A Short Brief</h3><p>This article is a UX case study of the improvements made in ODIN, during my seven-week winter internship in product design in 2019 at Wheelseye Technologies.</p><h3>What is Odin?</h3><p>Odin is a web-based portal that is used by the employees of WeFreight, a sub-division of Wheelseye Technologies, that operates its logistics marketplace.</p><p>The logistics industry constitutes four entities; Shipper, Broker, Transporter, Operator. WeFreight acts as a transporter and Odin is a tool that helps to manage the demand and supply by matching the shippers to the operators. There are various teams for logging in demands, assigning vehicles, tracking, and concluding the trips. It has a complete architecture consisting of accounts &amp; profile management, itinerary tracking, and a lot of other services.</p><p>To understand Odin, we need to know about the people involved and the other terms used on a day to day basis to communicate in the logistics industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsvbujIKfy5N2rN-hurjoA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f8-79njiE7U87-960FqEZA.jpeg" /></figure><h3>My Role</h3><p>My contributions were:</p><ol><li>To improve the demand creation format and to make it responsive.</li><li>To make modifications in the operator’s profile.</li><li>And to automate the shipper’s invoice system.</li></ol><h3>1. Demand Creation</h3><p>The shipper provides the requirements and demand, which the employees log into Odin. A truck is assigned to the given supply and is asked to reach the loading point. From there, the goods are loaded, and the trip starts.</p><h4>Problem</h4><p>The earlier version of the “Create Demand” Tab was a form with a variety of entries. (As you can see in the image given below) It was unresponsive and staggered. The structure of the form is not well defined, and similar kinds of entries were not grouped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*to1-ZpZPHyVXOcIdSQaWaw.png" /></figure><h4>Solution</h4><p>The new design of the form is segregated into four parts:</p><ol><li>Demand Information</li><li>Vehicle Information</li><li>Time Stamps</li><li>Shipper’s Requirements</li></ol><p>Grouping similar entries together reduced the cognitive load of the user. It made it easier for them to fill the form, and the design became responsive. Below is the mobile version of the new flow.</p><figure><img alt="Mobile view but this is not the Final User Interface." src="https://cdn-images-1.medium.com/max/1024/1*fqj7KUTGaT066bC_YwXIXA.jpeg" /><figcaption><em>This image shows the mobile responsive view but not the Final UI.</em></figcaption></figure><p>There is a team that logs in the demands into Odin. After they create a demand, they have to do this again using the tab from the hamburger. To eliminate this extra step and complete the flow, I added a “Create New Demand” Button at the end, that allows them to work swiftly.</p><p>Similarly, I changed a few input options as well, like count, vehicle type, tire count, etc. using icons and sliders to make the form more intuitive.</p><h3>2.Operator profile</h3><p>The operator profile contains the essential details of an operator, like type, name, contact number, trip details, account details, etc. This information gets stored in the database and used whenever needed, like mapping the transactions, settling the bills, contacting the drivers, etc.</p><h4>Problem</h4><p>The operator profile lacked a few things that were necessary for verifying an operator that needs to be stored in the database.</p><ol><li>Mode of verifying the operator.</li><li>Distinguishing between settled and unsettled trips.</li><li>Maintaining a proper track record of the accounts.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NbYeulIoflYGPvIJLbiAPw.png" /><figcaption><em>(I do not have the screenshots of the Operator Profile Tab that was there in Dec 2019 as ODIN is being updated on a regular basis.)</em></figcaption></figure><h4>Solution</h4><p>So, upon discussing with my mentor, Vaibhav Rawat, and the finance team, we listed out essential documents that are required to verify the operator, that have to be submitted in pdf format:</p><ol><li>Pan Card</li><li>Aadhar/ Driving License</li><li>TDS declaration form</li><li>A canceled cheque/passbook</li></ol><p>Initially, all trips made by the operator were lumped together under a tab, even when the accounts were settled for the trip. So, the trips were segregated into two tabs, namely “Settled Trips” and “Unsettled Trips.” Once the trip is settled, all transactions for that trip were frozen, i.e., no changes can be made after that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mE9vH9FsOSUsP2oQgcRnAA.png" /></figure><p>Many operators had multiple bank accounts, and transactions had to made accordingly. This is a part of the basic details of an operator, so this account section was placed there in the “Basic Details” Tab.</p><h3>3.Shipper’s Invoice</h3><p>Shipper’s invoice is a commercial document that itemizes and records transactions between the shipper and Wheelseye. It’s a physical document that is generated by the Finance Team.</p><p>Flow for invoice generation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1v29J6TKiDqYLr3gQ0SXqg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PrBd-NE2yMKuXAyhj6S-kQ.jpeg" /></figure><h4>Problem</h4><p>It was all on the papers!!!</p><p>The Finance Team had to work hard to put down all the data on the paper. They devised their methods for keeping track of the invoices generated and discarded. And only a tally of the number of invoices got made in Odin under the suitable status tab, as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PToxAxX7nrRyYBgZt62Ogg.png" /></figure><p>The invoices had a fixed format with a handful of variables, that were all available in Odin’s database. The main problem was that the GSTIN(s) of the shipper was not mapped in ODIN. The finance team kept a record of it separately.</p><p><strong>GSTIN</strong> or Goods and Services Tax Identification Number is a unique 15-digit number given to the dealers registered under the state VAT law by the respective state tax authorities. This number has a fixed address that is provided by the shipper. A shipper can have multiple GSTIN corresponding to the number of warehouses the shipper owns.</p><p>So, few changes have to made in Odin so that Shipper’s Invoice can be automated.</p><h4>Solution</h4><p>There were two significant changes done in the flows!!! (Saved best for the last…hehe)</p><ol><li>From now on, the shippers have to register with Wheelseye giving their GSTIN(s) at the time of onboarding. To manage that, a new tab was created in the Shipper’s Profile, named as “GSTIN” Tab. This tab contained the GSTIN(s), the state, state code, and the corresponding addresses.</li><li>A new unique system-generated number got introduced. This number was similar to Trip ID but unique to every invoice. There was a status for each number, i.e., used or null, to keep track of which numbers got discarded and which got used. By introducing such a number, we can count on all the three cases mentioned above.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*9XNhDArQE13u9cHHKDO_xg.png" /><figcaption>New GST Tab introduced</figcaption></figure><p>There are three types of GSTINs:</p><ol><li>CGST</li><li>SGST</li><li>IGST</li></ol><p>So, if the state codes of Wheelseye Technology and the shipper matches CGST and SGST are added, else only IGST is added in the final amount. This function also got automated as the shippers now provided the GSTIN details.</p><p>So now, to generate an invoice, they only need to fill a small form, as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Vn3bHOBsaAChiIiu33Klg.jpeg" /></figure><h3>Final Thoughts</h3><p>The main aim of making the changes mentioned in this article is to improve Odin’s capacity for handling the number of demands. As scalability is the priority for Wheelseye for the time being. So, as an intern, I never really got the chance for first-hand user-testing. Although one of the considerable advantages was the proximity with the users — The employees, which helped in <strong>quick iterations and better outcomes.</strong></p><p>Overall, this internship was fruitful and helped me grow as a product designer and as a person.</p><p><em>Thank you so much for reading. Suggestions are welcome! :). If you want to chat, feel free to ping me on Facebook or DM me on Instagram @ayaneshu</em></p><p><em>You can also mail me at ayaneshu@gmail.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56176a748e2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>