<?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 Neel Lakhwani on Medium]]></title>
        <description><![CDATA[Stories by Neel Lakhwani on Medium]]></description>
        <link>https://medium.com/@neellakhwani?source=rss-73fa3a28d737------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UN5rjHtTt4-GLJf9jM61-A.jpeg</url>
            <title>Stories by Neel Lakhwani on Medium</title>
            <link>https://medium.com/@neellakhwani?source=rss-73fa3a28d737------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:49:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@neellakhwani/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[Revolutionizing Cipher Docs: A Ground-Up Redesign Case Study]]></title>
            <link>https://medium.com/design-bootcamp/revolutionizing-cipher-docs-a-ground-up-redesign-case-study-8d7944a0d990?source=rss-73fa3a28d737------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d7944a0d990</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Neel Lakhwani]]></dc:creator>
            <pubDate>Fri, 12 May 2023 09:40:26 GMT</pubDate>
            <atom:updated>2023-06-26T14:17:29.607Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wSmeMB9mMEu8HeJ1f3NxIw.gif" /></figure><p>I joined Zeta in August 2021 and had the opportunity to work on Cipher Docs, one of my first projects. Initially, we focused on enhancing the article consumption experience. In March 2022, I had the chance to work on this project again and embarked on a complete revamp of the documentation portal from the ground up.</p><p>Throughout the project, I collaborated with my colleagues Subhasis Bhattacharjee and Kishore Vidyasagar. We formed a great team and had a lot of fun working together on this project!</p><h3>What is Cipher Docs?</h3><p>Cipher docs’ primary purpose is to enable developers and administrators to implement and configure Cipher’s services for their organization. It is a one-stop-shop solution for all the information one might need, ranging from implementation guides to the glossary.</p><h3>What is Cipher and who uses Cipher Docs?</h3><p>Cipher is Zeta’s offering that addresses all of its clients’ authentication and authorization requirements. It facilitates the setup and configuration of login credentials and role-based access control (RBAC) for users, as well as payment verification methods for card products via Authentication Center — which is the GUI tool that caters to these requirements. Cipher encompasses three offerings: Cipher ACS, Cipher CIAM, and Cipher EIAM.</p><p>We’re catering to 2 personas — <br><strong>1. Developers<br></strong>They use Cipher Docs to implement Authentication (AuthN) and Authorization (AuthZ) services using Authentication Center</p><p><strong>2. Administrators<br></strong>They use Cipher Docs to configure Authentication and Authorization services using Authentication Center</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Y_gPGWxZYAwJw8Okr-7Hg.png" /></figure><h3>Why did we revisit Cipher Docs Design?</h3><ol><li><em>The user journey for a user to get to the article relevant to the service they wanted to implement, was too long and required them to make too many clicks</em></li><li><em>The Business Head of Cipher came to us with the requirement to revamp Cipher Docs, since the existing version was confusing for internal Zeta developers</em></li><li><em>The search results on the documentation portal would repeat, weren’t categorised and were haphazardly listed, which ended up confusing the users</em></li><li><em>Security in banking is extremely important, so we wanted a well-designed documentation experience to avoid security breaches</em></li></ol><h3>Understanding the problems in detail</h3><p>In March 2022, we conducted a round of exploratory research in the form of user testing with active users of the Cipher Documentation Portal to gain insights into their problems with the existing version. The following are the insights we gained from these sessions 👇</p><ol><li><em>Users found the top navigation and mega menu unclear, leading them to favour the left navigation instead. Moreover, the extensive information architecture (IA) of the portal resulted in a time-consuming user journey with excessive clicks required to access the relevant article</em></li><li><em>The product descriptions on the landing page lacked sufficient context and failed to assist users in selecting the appropriate product for their specific use case</em></li><li><em>The search results on the portal were disorganized and lacked categorization, causing difficulty for users in determining the relevance of the results to specific products</em></li><li><em>Due to the technical nature of Cipher, users found specific keywords such as Domain ID and Tokens unfamiliar</em></li><li><em>The prerequisites preceding each article lacked comprehensive coverage in terms of the requirements</em></li></ol><h4>Constraints</h4><ol><li><em>The lack of availability of users for Feedback/User Testing (UT) Sessions, the available ones were internal Zeta employees.</em></li><li><em>No users for the admin persona were available within the pool of available internal Zeta employees</em></li></ol><p>We worked our way through these constraints by shortlisting a few power users from the pool of internal Zeta employees who used Cipher Docs and conducting these sessions with them to gain valuable insights.</p><h3>Our Approach to Problem-Solving</h3><p>To tackle the problems we identified in Cipher Docs, we employed a systematic approach to find effective solutions. Here’s how we addressed each challenge:</p><h4>Information Architecture (IA)</h4><p>After conducting feedback sessions and gathering insights, we initiated a complete overhaul of the portal by redefining the information architecture (IA) for Cipher Docs. Our process began with an extensive review of various existing documentation portals, including Chargebee, Freshworks, Razorpay, Stripe, and Figma, for inspiration and best practices.</p><p>We conducted an in-depth analysis of the information architecture (IA) of the aforementioned portals to enhance our initial idea. Based on our findings, we proposed a more streamlined and well-organized IA for the entire portal. The aim was to minimize the user journey from the landing page to a specific article, thereby reducing the number of clicks needed to reach the desired information</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RHXQCLg22Kn2i3pQJScrBQ.jpeg" /><figcaption>Final IA for Cipher Docs</figcaption></figure><h4><strong>Explorations</strong></h4><p>We took two stabs at the IA for Cipher Docs while keeping in mind the depth and the number of clicks it would take the user to reach a specific article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9K-RgaBU702LJiNlsVjHOQ.jpeg" /><figcaption>Exploration #1</figcaption></figure><p>One flaw in the initial approach was that every user, whether returning or new, had to go through the product overview section every time they accessed the portal</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OzyRcfbw7oLGaxtM9LiaxA.jpeg" /><figcaption>Exploration #2</figcaption></figure><p>In the second approach, we encountered some redundancy as the entry point to view persona-specific content was provided in two locations: the landing page and the overview section.</p><h4>Landing Page</h4><p>When designing the landing page, we prioritized two key factors: scalability and adherence to the defined information architecture (IA).</p><p>To address scalability, we considered the potential addition of more products under Cipher’s purview. We ensured that the landing page could accommodate future product expansions seamlessly. <br>To reduce the number of clicks required to access an article, we strictly followed the defined IA. This approach aimed to optimize the user journey and improve overall navigation efficiency.</p><p>In addition, we incorporated tags with commonly used and related keywords within each product section on the landing page. These tags were intended to assist users in quickly identifying the most relevant product for their specific use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XeF1AeoMPjKvTmyPNPbr6w.gif" /><figcaption>Landing Page</figcaption></figure><p>To adhere to the IA, we decided to eliminate the persona-specific entry points from the overview section. Instead, we came up with the idea of placing a section switcher directly on the global header. This switcher would allow users to easily switch between different sections based on their specific needs and personas.</p><ol><li><em>On the left side of the global header, we incorporated the following label: “Cipher CIAM (Overview/For Persona 1/For Persona 2)” based on the selection made by the user. This ensured clear navigation and allowed users to switch between different sections, including the overview and persona-specific content.</em></li><li><em>Based on the section selected by the user, the content and menu items in the global header and primary nav bar were dynamically updated. This would help in providing users with a streamlined experience, enabling them to easily find the information they were looking for.</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQKgukvc_Q78COs1fx1Gdw.gif" /><figcaption>Persona Switcher</figcaption></figure><p>After finalizing the information architecture, we proceeded to the next stage, which involved the redesign of the portal according to the defined structure, while taking into account all the other insights we had collected.</p><h4>Search Experience</h4><p>The search experience for Cipher Docs was flawed as the results lacked proper categorization and failed to provide additional information beyond the article title, URL, and a brief excerpt. Moreover, despite having dedicated sections for each product, the categorization system did not effectively serve its purpose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cGl1ye2Zivx9xOqZuG0SGQ.jpeg" /><figcaption>Existing Search Results</figcaption></figure><h4>How did we fix it?</h4><p>To enhance the search experience in Cipher Docs, we introduced filters on the search page. These filters allowed users to narrow down their search results and quickly find the desired articles after conducting a single keyword search.</p><p>During our analysis of search results, we categorized them into distinct groups and gained a deeper understanding of their content. Through this exercise, we identified three potential identifiers that could assist users in selecting from the search results: [Product Name], [Role/Persona], and [Content Type].</p><p>With this insight, we redesigned the search experience and improved the presentation of results by incorporating these three identifiers as tags. We removed the article URL from the results and implemented filters to help users sort through the search results more effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzNgixqDJK5fhDffvb1T7g.gif" /><figcaption>Enhanced Search Experience</figcaption></figure><h4>Primary Side Nav Bar</h4><p>The primary side nav bar was enhanced in 2 aspects — visual and functional.</p><p><strong>Visual Aspect</strong><br>For the visual bit, we gathered a bunch of references and explored them until we narrowed it down to one approach.</p><p><strong>Functional Aspect</strong><br>We added a filter capability to the navigation bar, enabling users to find relevant articles and categories based on keywords without searching the entire portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kWW4EkTUV3GOUZbiAxi-lQ.gif" /><figcaption>Primary Side Nav with localised filtration</figcaption></figure><h4>Explorations</h4><p>We did a few visual explorations for the primary sidebar, this is what they looked like 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDBUz9jLgZU60QocjXvTNw.jpeg" /><figcaption>Explorations for the primary side nav bar</figcaption></figure><h3>Content Framework</h3><p>Once we had all the insights collated, we created a content framework for the content team to follow and bring consistency throughout all articles across all products. It helps decide which out of the 5 W’s (What, Why, When, Where, Who) should be answered at which level of the article. Additionally, we also defined how each component should be used, for example — links and components for notes, tips and examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UfPE277Fp4xh2UQ6NJpUGA.jpeg" /><figcaption>Additional Components Introduced along with the Content Framework</figcaption></figure><h3>Second Round of User Testing</h3><p>After the redesign, we conducted user testing sessions with 7 participants to validate the changes. Based on their feedback, we made the following improvements:</p><ol><li><em>Simplified and clarified category and article titles for better user understanding.</em></li><li><em>Ensured consistent usage of Cipher-specific terms to eliminate confusion.</em></li><li><em>Incorporated tab-based navigation on the landing page for easier access to specific sections.</em></li><li><em>Revised glossary definitions to use user-friendly language.</em></li><li><em>Enhanced visual emphasis for highlighted glossary terms.</em></li></ol><p>After making the required design changes based on user feedback, we handed over the updated designs for development. Following two rounds of usability testing and multiple iterations, we proudly present the new and improved <a href="https://cipher.zetaapps.in/">Cipher Docs</a>.</p><p>Special thanks to all the folks who participated in our UT sessions and provided us with valuable feedback and insights, as well as the PMs and developers without whom this project wouldn’t have been possible!</p><p><em>Hi, my name is Neel and I like to solve problems with design. I am currently looking for freelance projects, you can view more of my work on </em><a href="https://neellakhwani.com/"><em>my website</em></a><em>. If you’d like to get in touch, send me an email at </em><a href="/service/mailto:hello@neellakhwani.com"><em>hello@neellakhwani.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d7944a0d990" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/revolutionizing-cipher-docs-a-ground-up-redesign-case-study-8d7944a0d990">Revolutionizing Cipher Docs: A Ground-Up Redesign Case Study</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[Mindhouse: Designing a digital mindfulness experience during a pandemic]]></title>
            <link>https://medium.com/design-bootcamp/mindhouse-designing-a-digital-mindfulness-experience-during-a-pandemic-4ed0986a4a3c?source=rss-73fa3a28d737------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ed0986a4a3c</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Neel Lakhwani]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 13:43:30 GMT</pubDate>
            <atom:updated>2021-06-20T09:36:40.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9-crk6QHY0hP8_Yj_VBUA.png" /></figure><p>The summer of 2020 was a tumultuous time for the world. The COVID-19 pandemic had brought about uncertainty, fear and isolation, and I had just finished the last few months of my undergrad degree in design while attending classes virtually. I was starting to look for product design positions, and when I came across an opportunity at <a href="http://www.mindhouse.com/">Mindhouse</a>, I was immediately interested in their goal of providing a way for people to practice mindfulness from their homes.</p><p>I talked to Ashish, the design lead at Mindhouse and started as a Product Design Intern during the last week of June 2020. After 6 months as an intern, I joined the startup full time for an additional 6 months, and the following is some of the work I did during that time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2SrYT4YBvETVqD4lVLDR-A.jpeg" /><figcaption>Joining day—my first day working with Mindhouse</figcaption></figure><h4><strong>About Mindhouse</strong></h4><p>Mindhouse started as a Meditation and Yoga studio in Gurgaon. Once the pandemic hit, they stopped conducting face-to-face sessions, and their plans to revamp the app (which was initially used to book and manage studio sessions) got accelerated. Today, Mindhouse is a product first organisation, building a platform to provide services across 4 verticals: Mental Health, Chronic Ailment, Everyday Wellness, and Women’s Health.</p><p>With the pandemic raging worldwide, mental health became an important part of everyone’s day to day life and getting the opportunity to design a user’s experience while they attempt to look after their mental well-being was an extraordinary journey.</p><p><strong>Redesigning the profile page</strong><br>My first task, and subsequent solve, was to redesign the profile page, helping users build a weekly meditation practice.</p><p>Since we were redesigning and not actually starting from scratch, we started by analysing the existing profile page to understand the current layout.</p><p>Following is the old profile page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tnvwoeotuRqDGnhJM2VvOw.png" /><figcaption>Old Profile Page (September 2020)</figcaption></figure><p>The way the information was laid out, made the page seem very cluttered, overwhelming and confusing.</p><p>Once analyzed, we decided to -</p><ol><li>Combine the class history instead of splitting it into two categories — classes attended (in-person studio classes) and anytime sessions (recorded sessions on the app)</li><li>Move the “Edit Profile” and “Edit Goals” options to the settings section</li><li>Remove the “Book Class Now” button, since in-person classes were no longer being held</li><li>Visually enhance the profile page &amp; fix the information hierarchy</li><li>Add a weekly minutes KPI (Key Performance Index) on the home and profile page</li></ol><p>The biggest challenge here was figuring out what the Weekly KPI + the graphs should be like, and whether or not they’d help nudge the users to build a meditation habit.</p><p><em>Mindhouse recommends you meditate at 140 minutes a week — the scientifically proven time you need to practice to achieve your desired goals, whether it’s improved sleep, increased productivity or a relaxed mind.</em></p><p>The next step was creating mockups on Balsamiq to better understand the new information architecture along with the flows for weekly meditation targets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qOfl74tuDJdd4Nc-Mp4Lng.png" /><figcaption>Balsamiq Mockups for the Homepage KPI, Profile page redesign, session contribution on completion and hitting the set weekly target</figcaption></figure><p>Then we moved onto taking a stab at making the high fidelity versions for these mockups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdogDMncj-6UO106AuAdmA.png" /><figcaption>Profile Page Redesign and Introduction of the Weekly MeditationTarget</figcaption></figure><p><strong>Redesigning the Do Now section</strong></p><p>More than a UI problem — the Do Now section redesign was an information architecture problem. The tracks were haphazardly listed and not categorised, which made the entire section tough to navigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGsKQ03eaPXg3vjfMgT5bQ.png" /><figcaption>Old Do Now screens</figcaption></figure><p>The old Do Now section had the following issues —</p><ol><li>The content was categorised, but not from a user’s perspective. This made it difficult for a user to understand what a specific album or course consisted of and how it would help them. It didn&#39;t solve for “how to choose” and “how to use”.</li><li>Another major issue here was the copywriting — it wasn’t communicating the purpose of the content to the user.</li><li>The visual style of the cards wasn’t consistent, which made it tough to distinguish between the tool types each album consisted of.</li><li>The arrangement of the buttons on a track tile made the reminder and favourite options seem more important than the primary action — which was playing the track.</li></ol><p>We started by breaking down the taxonomy for all the content within the Do Now section, to figure out a better way to classify the content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BfQb7hfoc07DmTgf9yOm3g.png" /><figcaption>Taxonomy for tracks in the Do Now section</figcaption></figure><p>We listed down all the possible facets for classifying and grouping the content and then moved on to figuring out a better information architecture that would help to make this section of the app more delightful and consumable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6VXOUwng3GKKHh1RJsppA.png" /><figcaption>New Information Architecture for the Do Now section</figcaption></figure><p>After wrapping up the problem with the information architecture, we started exploring different visual styles for the section. We started out with paper mockups and eventually created high fidelity screens. We broke down the UI into smaller pieces, such as— headers, sections, album cards, track cards, track listing, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pRnANTsyZVq_hT0VIwMivg.png" /><figcaption>Do Now Visual Explorations</figcaption></figure><p>After a bunch of explorations, we decided on the final version for each element and put them all together to compose the new Do Now section.</p><p>This is what it looked like 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O0QlWvUzr6mKoqspo4CsRQ.png" /><figcaption>Do Now Redesign — Visual Elements and Final Screens</figcaption></figure><p><strong>Book Tab — Slot based class selection</strong></p><p>Due to a large number of classes (approx 70 per day), currently, it was hard for the users to know the class they were booking.</p><p>Each course has different types, which are available in two languages (Hindi and English). In total there were about 70 different classes in a single day on the app — scheduled for different times during the day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o4ZThaXvR9R0YekxJ9IiXQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GAqdTixzJc5m2GoLsYnUcg.png" /><figcaption>A tally of the number of classes scheduled for the different course types in a day + Old slot based selection</figcaption></figure><p>This flow enabled the user to book classes but didn’t tell them what language the class they were booking, was in. Further, the slot listing was unnecessarily long with 70 slots in a 3x3 grid.</p><p>To solve the problem of knowing exactly what class the user was booking, we decided to give an option to pick the language before booking. Doing this would actively filter the available time slots, and only list the ones available for the chosen language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VKVrELIZRAjK6pFHlLNpmQ.png" /><figcaption>New slot-based selection UI</figcaption></figure><p><strong>Personal Coach<br></strong>We had plans to roll out a “<a href="https://www.mindhouse.com/request-a-callback/">Personal Coach</a>” feature, which would let the users engage with a Mindhouse coach to customize their wellness plan.</p><p>This service offers both — free and paid versions. The free version is accessible to anyone who has the Mindhouse app on their phone, from the “Coach” tab.</p><p>The differences between the two are as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H8ZFatgd79JxRLaJW4eRgQ.png" /><figcaption>Free vs Paid Personal Coach service</figcaption></figure><p>After getting the business requirements for the feature, and before making the screens, we planned out what the screens for both versions would consist of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xmmHyOPj6VgGfpMeMEbPew.png" /><figcaption>Flows for free and paid versions of the app screen</figcaption></figure><p>Once we had the “what” figured out, we started exploring the “how” — as in how the content needs to be presented visually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w35_Eq8jeAogLwXjKHprjQ.png" /><figcaption>Illustrations + UI Explorations for Personal Coach</figcaption></figure><p>After a bunch of explorations, we finalised the illustrations that worked best for our service and decided on the screens.</p><p>This is what the final screens looked like 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bLfHL6jr_EeCK8SeIzj2g.png" /><figcaption>Final UI for Personal Coach</figcaption></figure><p><strong>New Onboarding for the App<br></strong>In March, we added new content to the app and divided it into 4 categories (Women’s Health, Everyday Wellness, Chronic Ailments, and Mental Health), each with several subcategories. Every user was allowed to select one major category and up to two subcategories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BbYZOfC7DUqUmxj3SXYBiQ.png" /><figcaption>Explorations for app onboarding</figcaption></figure><p>This is what the final onboarding looked like 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zCwlLCkgEA2kQEtd6ESqw.png" /><figcaption>Final onboarding for the new Mindhouse app</figcaption></figure><p><strong>Website Redesign</strong></p><p>The Mindhouse website redesign was primarily a visual revamp of the old pages along with creating high-conversion landing pages to facilitate the launch of new services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U2SSBDoeo4wctTXPvGhTUQ.png" /><figcaption>Mindhouse Website — Final Webpages</figcaption></figure><p><strong>Social Media Collaterals</strong></p><p>I also worked on some marketing collaterals to run as advertisements, to promote our live interactive classes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NcvaQysRQ9n-_n1PZepE8A.png" /><figcaption>Social Media Advertisements for live interactive classes</figcaption></figure><p><em>Hi, my name is Neel and I like to solve problems with design. I am currently looking for a full-time role, you can view more of my work on </em><a href="https://neellakhwani.com/"><em>my website</em></a><em>. If you’d like to get in touch, send me an email at </em><a href="/service/mailto:hello@neellakhwani.com"><em>hello@neellakhwani.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ed0986a4a3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/mindhouse-designing-a-digital-mindfulness-experience-during-a-pandemic-4ed0986a4a3c">Mindhouse: Designing a digital mindfulness experience during a pandemic</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[Designing the National Zoological Park experience]]></title>
            <link>https://neellakhwani.medium.com/national-zoological-park-mobile-app-1840cc4f17cb?source=rss-73fa3a28d737------2</link>
            <guid isPermaLink="false">https://medium.com/p/1840cc4f17cb</guid>
            <category><![CDATA[design-projecs]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[communication-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[national-zoological-park]]></category>
            <dc:creator><![CDATA[Neel Lakhwani]]></dc:creator>
            <pubDate>Mon, 14 May 2018 17:21:25 GMT</pubDate>
            <atom:updated>2021-06-10T06:48:22.305Z</atom:updated>
            <content:encoded><![CDATA[<h4>An app for the New Delhi Zoo.</h4><blockquote>My name is Neel Lakhwani, and I am a Communication Design student at Pearl Academy, Naraina. This project was my foundation year end design project. If you liked my work, you can see more at <a href="http://neellakhwani.com/">neellakhwani.com</a>.</blockquote><p>For our final project, the students formed teams of up to 5 people across various design disciplines. Each team was assigned a place in Delhi, where they conducted field research to identify problems, analyze them, and then come up with design solutions.</p><h3>The Field Visit</h3><p>My team was assigned the National Zoological Park at Pragati Maidan, and we visited the park on 1 April, 2018.</p><h4>Ticket Counter</h4><p>My team and I reached at about 1:30 pm on a Sunday, and found long queues at each of the 10 ticket counters. Each of us took a different line in the hopes that we could get the tickets faster, but it still took us about 35 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOozFK1wrKZ8_cGbEeDE4w.jpeg" /><figcaption>Lines for entry ticket</figcaption></figure><h4>Trolley Counter</h4><p>Once we finally managed to get the tickets and entered the zoo, we came across a second counter. Visitors can either walk around the nearly 71 hectare area of the zoo, or buy tickets for the <em>Battery Operated Trolley (B.O.T) </em>which runs every few minutes and provides a quicker way to get around the zoo. Buying tickets for the BOT took us another 20 minutes — at this point we had spent almost an hour standing in lines, and it was not a great start to our zoo experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0yXSdhbVgWHSp4p7N7bbqA.jpeg" /><figcaption>Line for the Battery Operated Trolley (B.O.T)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-UOJPtvJefDUMv2tsSpg1Q.jpeg" /><figcaption>The Battery Operated Trolley</figcaption></figure><h4>Signage</h4><p>We eventually got on the trolley and started moving towards the animal enclosures. We noticed that the zoo uses signage in English and Hindi to help people navigate through the various sections. However, these were only directional, and did not provide information about distances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EAn44lD28_k9KsxBM5OuKw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NuUJ9QhPlOAjW2P63lFchg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z1Chxe2nNOt_SuLTRAMtFQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YP20KkJyMn3HxERWiHHmuw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jzuZysOJ_SdRYztn-MCqqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gIez4EYLtv1Zj2yPpfEqXw.jpeg" /><figcaption>Signage</figcaption></figure><p>Furthermore, the zoo provides the visitors with benches and canteens every now and then in order to give them a place to sit and enjoy some cold beverages if they are tired.</p><h3>Problems Identified</h3><ol><li><strong>Long lines for tickets<br></strong>They have ten counters for ticketing yet it takes a long time to get to the counter since they occasionally shut a counter and ask everyone to shift to the next one. Online ticketing could also help reduce the load on the physical counters.</li><li><strong>Separate counter for the battery operated trolley (B.O.T) ticket<br></strong>After entering, there is a separate counter for the B.O.T tickets, which has another long queue. The counters could easily be merged into one, with two kinds of tickets — either with or without the trolley access.</li><li><strong>Directional signs<br></strong>The current wayfinding system at the zoo points in the general direction of the different sections of the zoo and doesn’t tell you how far a specific enclosure is either in terms of distance or time by foot or trolley.</li><li><strong>Information outside the enclosures<br></strong>The information outside the enclosures is written only in English and Hindi. However, we noticed a lot of people who could not read either of the two languages and might want to read in a language that they are comfortable with.</li><li><strong>Updates about the zoo<br></strong>The general public doesn’t get any updates about the events or developments at the zoo unless its something like a man falling into the tiger enclosure.</li></ol><h3><strong>Further Research</strong></h3><p>I conducted a survey to get to know about people’s experience at the zoo, and the problems that they went through.</p><p>Have you been to the National Zoological Park?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/1*VWMMeYc_Cp21_wn3ZB-hQA.png" /></figure><p>Rate your visit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*Vb7BSjhceuRgYhykh4dZ3w.png" /></figure><p>Write a brief note about your overall experience, do elaborate on any inconveniences or incidents that you faced or went though</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*CsYRjym6jxMP8Ixz74vu4g.png" /></figure><p>I considered two possible ways to implement my solutions — digital touchscreens and wayfinding system close to each enclosure and a mobile application. I considered the pros and cons of both, but due to the difficulties of maintaining digital touchscreens in the zoo, letting people use their own devices made more sense and thus I decided to go with designing the application.</p><h4>The Solution</h4><p>I believe that making a mobile application for the National Zoological Park will help solve all of the above-mentioned problems and will improve the overall experience of the visitor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*M49xG8Pk2i77xUTW7lPeiQ.png" /></figure><p><em>Here is the prototype of the app</em></p><p><a href="https://invis.io/JFINE8P4ABT">Click here to view the project `National Zoological Park`</a></p><h4>What I learned</h4><p>The aim of the project was to help students understand that design isn’t always something that looks good or attractive, it is something that is well planned, well researched and helps solve a problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1840cc4f17cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>