<?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[BlackBuck Design - Medium]]></title>
        <description><![CDATA[Simplifying and humanising design for the Indian trucking industry - Medium]]></description>
        <link>https://medium.com/blackbuck-design?source=rss----c872c2d218b6---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>BlackBuck Design - Medium</title>
            <link>https://medium.com/blackbuck-design?source=rss----c872c2d218b6---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:03:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/blackbuck-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How BlackBuck GPS helps in Calculating the Fuel Consumption of a Truck]]></title>
            <link>https://medium.com/blackbuck-design/how-blackbuck-gps-helps-in-tracking-the-fuel-consumption-of-a-truck-3e4db9e19b80?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/3e4db9e19b80</guid>
            <category><![CDATA[logistics]]></category>
            <category><![CDATA[fuel-tracking]]></category>
            <category><![CDATA[fuel-consumption]]></category>
            <dc:creator><![CDATA[Rishabh Kumar]]></dc:creator>
            <pubDate>Wed, 28 Aug 2024 09:19:21 GMT</pubDate>
            <atom:updated>2024-08-28T09:19:21.131Z</atom:updated>
            <content:encoded><![CDATA[<h4>Fuel Tracker User Experience Design: Part 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJ6u9Wed5B11yywF8aZHLQ.png" /></figure><h3><strong>Introduction</strong></h3><p>Fuel Tracking &amp; Fuel Monitoring is an important aspect in any transporter’s work line. According to a report from FleetX (2023), Fuel expenses account for nearly 45% of the total fleet cost. Traditionally fuel tracking and monitoring is done by Fleet Owners (FOs) through manual methods of checking odometer readings after a trip, checking with drivers for fuel expenses, keeping records of past fuel consumption on known routes, etc.</p><h4><strong>Fuel Sensors: The digital method of fuel tracking</strong></h4><p>Fuel Sensor is a cylindrical device that is installed into the fuel tank of a vehicle. It works by using electrochemistry, where two electrodes are immersed in the fuel and a potential difference is generated based on the fuel’s concentration. The electrical signal is then converted into an analog or digital value, which can be interpreted by a fuel management system. This device, used along with a GPS device, thus gives accurate data of fuel consumption with mileage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lf6AmQL_OWDZaGTs" /></figure><p>This digital integration enables the user to remotely track fuel consumption, giving the user real time data of fuel consumption, current fuel level and any abnormal increase or decrease in fuel level.</p><p>A typical fuel sensor costs somewhere between ₹15–20k, making it a considerable investment for our average fleet owner.</p><h4><strong>BlackBuck’s Venture into Fuel Sensors</strong></h4><p>Having a large user base of transporters and truck owners, BlackBuck decided to give fuel sensor data services to its customers as a new add-on feature. However, due to the fuel sensor device’s significant cost and sophisticated installation procedures, it was decided to <strong>first check out the demand for digital fuel tracking in its current user base</strong> before heavily investing into it.</p><p>This was done by <strong>introducing a manual fuel tracking widget into the truck details page of the GPS App of BlackBuck</strong>, where the <strong>user has to enter the mileage manually to track fuel consumption</strong>, based on the distance the truck has traveled. A similar kind of experience was also being provided by its competitor WheelsEye, which also provides fuel tracking services without the need of a fuel sensor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MIDs1Vy422_oLye3" /></figure><p>Hence, the approach was to first match what the competitor is offering and then later on to improvise on the experience, using results gathered from its initial adoption.</p><p>This approach was termed <strong>Phase I of the fuel sensor user experience, which will be discussed in detail in this part of the blog series</strong>.</p><p><strong>BlackBuck GPS App</strong> was chosen as the apt place to show fuel consumption as GPS already gives measured distance travelled by the truck which can further be multiplied with mileage set to give fuel consumed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rFM1GKt6FIMILh8Ph6l-Ug.png" /><figcaption>BlackBuck’s Fuel Tracker (without using fuel sensor) Approach</figcaption></figure><h3><strong>Phase I — Fuel Calculator Widget in Truck Details Page</strong></h3><p>This was an experimental phase to test out our user’s willingness to know fuel consumption data.</p><ul><li>The objective of this phase was to check out how many users willingly enter their truck’s mileage to know their fuel consumption</li><li>The initial expected adoption rate was set to at least 30% within 1 month (i.e more than 30% users should choose to manually enter mileage), considering it as a new feature and user getting a small learning curve for the feature adoption.</li><li>If the response is as expected, further investment will be initiated on the prospect of actual hardware integration and its user experience</li><li>If the conversion is less than 30%, fuel tracker shall be limited to Phase I only.</li></ul><h4>User Research for Fuel Tracker</h4><p>Before getting into the design aspect, an <strong>Qualitative User Research</strong> was done <strong>via telephonic interviews</strong> with 10 different users of BlackBuck. The basic questions asked by us were mostly in line with ‘when and how the transporters track their fuel expenditures’. Given below are the inferences derived from the interview feedbacks:-</p><ul><li>Transporters mostly have a good idea of how much average their vehicle is giving</li><li>The fuel expenses tracking frequency depends on the size of fleet the transporter has. For a large fleet, fuel reporting and calculations are done once or twice a month. For a small fleet, it might be every second day</li><li>Transporters tend to distribute fuel expenses according to the route they have planned. In case it’s not possible, the tracking is done via odometer reading after the truck has come back after a haul</li><li>Buffer fuel is also taken care of in case of emergencies</li><li>Almost all transporters show some level of interest in fuel tracking devices and softwares. However, most are hesitant to invest due to high cost of fuel tracking devices</li></ul><h4><strong>Fuel Tracker Widget UI Design Iterations</strong></h4><p>Several iterations were made for the fuel calculator widget that was to be inserted into the truck details page as well as for the mileage setting feature to start tracking fuel consumption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VgMDo_dCNm1P4Stqfcd1yg.png" /><figcaption>Iterations made for Fuel Tracker Widget</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YuUOERXGagjCcGhxh2DmLg.png" /><figcaption>Iterations made for mileage setting feature</figcaption></figure><h3><strong>Phase I: Final Design</strong></h3><p>The fuel tracker widget was then finally integrated into the GPS truck details page of BlackBuck, with first time landing experience accounted for and also with the inclusion of past fuel consumption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LIB_2cK718jak4BWGoY9yw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohWjg1Vi8psrTyLcgYEuvw.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Ff5r44NT6dUE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Df5r44NT6dUE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Ff5r44NT6dUE%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/04c55ce6dda27417feaffe886b6f5976/href">https://medium.com/media/04c55ce6dda27417feaffe886b6f5976/href</a></iframe><h4><strong>Impact of Phase I</strong></h4><p>The initial adoption of the fuel calculator showed great promise, with over 2<strong>5% GPS users setting up mileage to view fuel consumption within 2–3 weeks of the widget launch</strong>. This concluded the widget design as a successful venture as going by the analysed rate of adoption, expectation of over 30% adoption rate within 1 month was very much probable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A9--JqgW4WZch8up0Y6eTQ.png" /><figcaption>Analysis Metrics after 2–3 weeks of Widget Launch</figcaption></figure><p>These users who set their mileage were later shortlisted as potential buyers for fuel sensor devices. BlackBuck sales team then pitched the prospect of fuel sensor purchase and installation to these users through phone calls and WhatsApp campaigns, which showed a decent willingness to get the fuel sensor installed, if it is offered at a lower cost that whats available locally.</p><p>This prompted the product team to take <strong>further action on setting up an integrated system for fuel tracking involving actual fuel sensor hardware installation and subsequently its user experience on app</strong>.</p><p>This move was termed <strong>Phase II</strong>, <strong>which will be discussed in detail in Part 2 of this blog series</strong>. So stay tuned for part 2. Cheers! if you have read this far.</p><h4>Acknowledgement</h4><p>Big thanks to Utkarsha Chandra, my Product Manager for her help and contribution to this blog, as well as to this whole project. She was one of the main advisors and facilitators during the project. Thank you very much for providing the user-based data and research wrt this blog.</p><p>Another big thanks to <a href="https://medium.com/u/63dc821dee26?source=post_page-----1e38a3fb14d7--------------------------------">Mayur Devatwal</a>, my Design Head, to help me structure this blog. He was also one of the main advisors during the project. Thanks for your guidance and support.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e4db9e19b80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/how-blackbuck-gps-helps-in-tracking-the-fuel-consumption-of-a-truck-3e4db9e19b80">How BlackBuck GPS helps in Calculating the Fuel Consumption of a Truck</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How BlackBuck integrated real-time Fuel Tracking with its GPS]]></title>
            <link>https://medium.com/blackbuck-design/how-blackbuck-integrated-real-time-fuel-tracking-with-its-gps-408ea00c94dc?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/408ea00c94dc</guid>
            <dc:creator><![CDATA[Rishabh Kumar]]></dc:creator>
            <pubDate>Wed, 28 Aug 2024 09:17:05 GMT</pubDate>
            <atom:updated>2024-09-02T05:06:49.661Z</atom:updated>
            <content:encoded><![CDATA[<h4>BlackBuck Fuel Sensor User Experience Design: Part 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoeOIDtZSTCQsrjhKQzyTQ.png" /></figure><h3>Introduction</h3><p>The previous part of this blog series discussed about what a Fuel Sensor is, what BlackBuck did as Phase I (Fuel Calculator Widget introduction in GPS flow) to understand how many users are willing to see fuel consumption digitally and are likely to buy a Fuel Sensor.</p><p><em>For better context, you can access Part 1 of this blog series </em><a href="https://medium.com/@rishabhkumar.uday/how-blackbuck-gps-helps-in-tracking-the-fuel-consumption-of-a-truck-3e4db9e19b80"><strong><em>here</em></strong></a><em>. A quick skim will suffice.</em></p><p>The Phase I of introducing a Fuel Calculator Widget in BlackBuck GPS yielded promising results, with as many as 12k+ out of 50k users manually setting mileage to track fuel consumption.</p><p>This provided valuable insights into the potential use case for Fuel Sensors and helped shape BlackBuck’s broader target and strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nabBHEb0kmevidVEFlmKqg.png" /></figure><p>Now the objective was to build a proper feature that would cater to the real-time fuel tracking needs of BlackBuck’s user base. This Blog will discuss in detail about how it was achieved.</p><h3>Phase II Start — BlackBuck+Vamosys</h3><p>In February 2024, BlackBuck partnered with Vamosys, a fuel sensor distributor, to sell and install fuel sensors to its user base. Vamosys provided its app and distribution network, while BlackBuck offered access to its network of truck owners as potential buyer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgYLnAR5oJUCHFhA_a2BBw.png" /><figcaption>Vamosys App Main Screens</figcaption></figure><p>This partnership provided an initial user base of truck owners with activated fuel sensors on their trucks.</p><h3>User Research &amp; Competitor Benchmarking for Fuel Sensor</h3><p>BlackBuck approached around 50 of such truck owners to understand:-</p><ul><li>Why users use Fuel Sensor</li><li>How has the current solution helped them</li><li>What are the issues they face with the current solution</li></ul><p>Thus, user research (done via telephonic interviews) and simultaneously, other apps’ benchmarking was also initiated to gain insights wrt the above points.</p><h4>User Interviews — Round 1</h4><p>Post the telephonic interviews, key questions were asked to users around the above three points and then inferences were derived from thier feedbacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evrdVrQWAiVgiS4u9Rs-NA.png" /></figure><p>These insights helped us get a clarity on what features should be present prominently within the fuel tracking experience for the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZDU5wOTpcN9Wi7AKzAYLw.png" /></figure><h4>Competitor Benchmarking</h4><p>Benchmarking was conducted with four other apps to compare key features for user fuel tracking needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7Y0erdEsUFQAei_ZuyNuA.png" /></figure><p>From the benchmarking, it was known that most of the competitors were covering the key areas addressing to the users fuel tracking needs.</p><p>However, the cluttered UI for FOs was a common issue across most apps, identified as a key area for improvement. Another overlooked area was viewing past fuel trends and graphs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b3fnpE3Jd1C1FZWqvn5esA.png" /><figcaption>Vamosys Flow for Graph View</figcaption></figure><blockquote>Past Fuel trends in competitor apps were not shown in an easily consumable fashion for truck owners, with the visuals provided looking complicated for our user base</blockquote><h4>User Interviews — Round 2</h4><p>To validate this fuel trend problem found, another set of interviews were done to find out answers related to graph view of fuel tracking info.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3iJOc5B7T5TvIDxGlbUGgQ.png" /></figure><p>These insights, hence helped us in validating the areas where we can give an improvised experience from our competitors</p><blockquote>All the necessary Fuel Tracking details should be given to the user in a clean, simple and easily consumable fashion along with the basic Fuel Tracking detail provision. The gateway to the past trends itself shall also be easily discoverable.</blockquote><h3>Step towards Final Design</h3><p>With the clarity gained on what to design, a user flow was made with the key pages involved and the changes that will be getting implemented within those pages</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnMiApOg2OrZ635B32bBtQ.png" /></figure><p>Following the user flow, design iterations were made on each main component to proceed with the final design</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwdJ0s_QFu2M9tvn6LAacA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rHweZ_leRO2kCbLe8RpY3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63o83W-O4XRKjt2PEPzygQ.png" /></figure><h3>Final Design</h3><p>Finally, all the final iterations were assembled together in a singular flow</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HM6d5L__qevUY48-krj1Sw.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9k1DpyF-K44%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9k1DpyF-K44&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9k1DpyF-K44%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/846de6dc638bed092c42947ad702eddd/href">https://medium.com/media/846de6dc638bed092c42947ad702eddd/href</a></iframe><h3>Final Results &amp; Conclusion</h3><p>The Fuel Sensor experience has seen strong adoption since its launch in late May 2024, with <strong>153 devices activated and 166 new orders confirmed by July, and an installation rate of 3.89/day in June-July</strong>.</p><p>This success is attributed to the app’s user-friendly design and the real-time fuel data provided, which has boosted customer trust and increased sales. This project also highlights the importance of a well-designed <strong>installation and repair process</strong>, to be <strong>discussed further in Part 3 of this blog series</strong>.</p><p>Overall, this project demonstrated the impact of data-driven UX design in driving revenue and provided valuable UX/UI insights.</p><h3>User Feedbacks and Future Scope</h3><p>One month after the new design release, we surveyed 20+ active Fuel Sensor users to gauge their perceptions.</p><ul><li>The primary focus was on feedback regarding the sensor’s accuracy in detecting fuel levels, refuelling, and fuel theft.</li><li>Secondary feedback covered notification timings, graph usage, and suggestions for improvements.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EICRRh_EOMEXBpbOCNBTZQ.png" /></figure><h3>Acknowledgement</h3><p>I wholeheartedly thank my Product Manager in charge of this project, <strong>Utkarsha Chandra</strong>, for her visionary guidance and expertise on this project.</p><p>A big thanks to my fellow Designer, <strong>Abhishek Sharma</strong>, for the efforts made on the design and research on this project.</p><p>Big thanks to our UX Researcher <strong>Geethanjali R &amp; Roma Mandpe</strong>, for their expert communication in conducting interviews &amp; their help in insight generation post interviews.</p><p>Finally, I would like to thank my Product Category Head,<strong> Karteek Narumanchi</strong> for his key guidance on this project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=408ea00c94dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/how-blackbuck-integrated-real-time-fuel-tracking-with-its-gps-408ea00c94dc">How BlackBuck integrated real-time Fuel Tracking with its GPS</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identifying the needs of BlackBuck’s unique user base]]></title>
            <link>https://medium.com/blackbuck-design/identifying-the-needs-of-blackbucks-unique-user-base-a4ecb747ad49?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/a4ecb747ad49</guid>
            <category><![CDATA[ux-research-method]]></category>
            <category><![CDATA[digitization]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[trucking]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Greeshma Rawat]]></dc:creator>
            <pubDate>Thu, 20 Apr 2023 05:31:27 GMT</pubDate>
            <atom:updated>2023-04-22T08:54:47.425Z</atom:updated>
            <content:encoded><![CDATA[<p>How BlackBuck conducts user research and testing to build better products</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BujXXnITIdHC1fzQZXNqYA.png" /></figure><h3>User Research and its importance</h3><p>User research is essential to building a better product because it provides insights into the needs, preferences, and behaviours of the people who will be using the product. The goal of user research is to gather insights that can inform the design and development of products or services that better meet users’ needs.</p><p>There are various user research methods, including qualitative and quantitative approaches. Qualitative methods, such as interviews, focus groups, observations, and usability testing, aim to understand the subjective experiences and perspectives of users. Quantitative methods like surveys and analytics aim to gather numerical data to measure user behaviours and attitudes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lri0IfXEBIAmTO0A9rfLcQ.jpeg" /><figcaption><em>At BlackBuck, user interviews, usability testing and field studies are conducted for qualitative studies.</em></figcaption></figure><p>The insights gained from user research can inform various aspects of product development, including product strategy, design decisions, feature prioritization, and marketing messaging. By incorporating user feedback and insights into the development process, businesses can create products and services that better meet the needs of their target users, leading to higher user satisfaction and improved business outcomes.</p><p>Overall, user research is essential to building a better product that meets the needs of its users. By understanding user needs, creating a user-centred design, testing assumptions, improving usability, and reducing development costs, user research can help ensure a product’s success.</p><h3>Qualitative Research</h3><p>When conducting user research and usability testing, there are a variety of qualitative methods available that can provide valuable insights into the needs, behaviours, and attitudes of users ( as mentioned in the image below).</p><p>The next obvious question is — which method to use. Well, it’s important to experiment with different methods to determine which ones work best for your objectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQcvS8jm9_BNtgtYuJrDdA.jpeg" /><figcaption><em>The before and after steps are equally crucial for successful research.</em></figcaption></figure><h3>Research challenges with truckers in India</h3><p>As a trucking marketplace in India, BlackBuck aims to understand the needs and expectations of its target audience to provide a seamless user experience. However, the target audience may not be very educated, which poses a challenge for user research and usability testing. Many methods of traditional research don’t work with our users. Some crucial problems we face during our research -</p><ul><li>We cannot fix appointments with them for one-on-one interviews or telephone interviews.</li><li>We cannot expect a dedicated amount of time even if we meet them.</li><li>Telephone interviews are cold calls — whoever answers and is willing to talk.</li><li>The interviews are (almost) always interrupted — they get a call, start talking to someone else or pick up another task.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wvAQrjaPUsOarf4Sl2hdAQ.jpeg" /><figcaption><em>Most truck owners are still getting used to the digitisation of their businesses. Therefore, asking them for feedback on a digital product can be tricky.</em></figcaption></figure><p>Truckers in India have a unique lifestyle and work in an industry that operates differently from traditional 9–5 businesses. The trucking industry is open 24/7, and truck owners are constantly on calls, looking for loads or trucks, enquiring about the location of trucks or loads, and following up on payments. Due to these factors, their priorities and needs are different, making conducting user research and testing challenging.</p><p>Moreover, many truckers are not familiar with the concepts of user research, testing, and surveys or their importance in the development of a product that they use. As a result, getting feedback from them can be difficult.</p><h3>Research Methods at BlackBuck</h3><p>To overcome the above challenges, BlackBuck has adopted various research and testing methods, such as one-on-one interviews, phone call interviews, and sending screenshots of designs via WhatsApp to gather feedback and on-site user testing. These methods allow BlackBuck to obtain the necessary insights from truckers without making them feel like they have to put in any extra effort. By using innovative research methods, BlackBuck can understand the unique needs and priorities of its target audience and develop products that cater to their requirements.</p><h4>1. One-on-one interviews</h4><p>In these interviews, we talk to individual users to understand their experiences, pain points, and suggestions for improvement. One-on-one interviews are usually conducted on-site, i.e. a <em>transport hub</em> where many BlackBuck-using transporters can be found in close vicinity. This method allows BlackBuck to gain in-depth insights into the user’s perspective and tailor the product accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hw8IYrO1Af3vPd13DB9vIA.jpeg" /><figcaption><em>One-on-one interviews are conducted in an environment where the users are most comfortable.</em></figcaption></figure><p><strong>Limitation -</strong></p><p>Conducting one-on-one interviews can be time-consuming and resource-intensive, limiting the number of users who can participate.</p><p>One-on-one interviews with our users, who are predominantly truck owners and transporters, present unique challenges due to the nature of their work. As the trucking industry is not highly organized, fixed appointments are not always feasible. Our users may have unpredictable schedules and may not be mindful of allocated time. As a result, interviews can range from 15 minutes to an hour, depending on their availability and mood. It’s common to catch them amid their work, requiring flexibility and patience. Interruptions such as phone calls or other tasks may occur during the interview, leading to potential delays. Therefore, conducting interviews with our users requires adaptability and an understanding of the demands of the trucking industry.</p><p><strong>Research Example — Interviewing users for overall feedback on the BlackBuck app -</strong></p><p>In Jodhpur, we conducted interviews with a group of users to gather their general opinions about the app’s usability. Our objective was to gather information on their preferences, grievances, and any challenges they faced while using the app.</p><blockquote>Our goal was to understand how our app was being used by users and identify ways to improve their experience, which required us to engage in individual conversations with them.</blockquote><p>As the interviews were conducted individually, we had sufficient time to understand their requirements and difficulties, gaining valuable insights into their experiences.</p><p>Research Impact -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*q1J6EZdvscXWrVxgsC6cZQ.png" /><figcaption>One of the many insights of the research. We asked the users extensive questions about different categories, flows and screens.</figcaption></figure><p>Having one-on-one interactions with the users provided an excellent foundation for revamping the app. These detailed interviews gave us valuable insight into how the users interacted with the app. We discovered the other apps they used in their daily routines and what aspects they appreciated about those apps. This knowledge helped us identify what modifications we could implement in our app.</p><h4>2. Telephone Interviews</h4><p>BlackBuck also conducts phone call interviews with its target audience. Phone call interviews are cost-effective and allow researchers to reach a large number of users quickly. In phone call interviews, researchers ask users questions about their experience with the product, their pain points, and suggestions for improvement. Phone call interviews also allow BlackBuck to gather feedback from users who are geographically dispersed.</p><p><strong>Limitation -</strong></p><p>Our phone calls to users are not prearranged. We receive a list of users to interview and begin contacting them. However, the process can be unpredictable as users may decline to speak or hang up after only a few minutes, and may not answer all questions. Despite these challenges, we persist until we receive adequate feedback from a targeted number of participants. Typically, for every 20 feedbacks received, we need to call an average of 50–60 people. Therefore, conducting interviews via phone requires persistence and adaptability to navigate the variability of user engagement.</p><p><strong>Research Example — Finding out if the Chats feature is as important for users as the Calls feature</strong></p><p>Our aim was to provide truck owners with the ability to communicate with transporters on our platform through the Chats feature. After a month of its release, we wanted to see the significance of this feature to our users.</p><p>The objectives of this research were -</p><ol><li>To find out why certain users used the chat feature before calling a transporter.</li><li>How important was the chat feature to users in comparison to the calls feature?</li></ol><blockquote>We decided to call the users for this research because we were looking to gather qualitative feedback from users in a relatively short amount of time.</blockquote><p>Research Impact -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*GcRz_d45BpgmV1LnHsz7DA.png" /><figcaption>Synthesis of the research to understand why users used the chat feature, how important it was for them and if they liked it more than the call feature.</figcaption></figure><p>The research data provided a clear indication that the users did not consider the chat feature as a must-have feature, but rather a nice-to-have feature. While some users expressed positive sentiment towards the chat feature, the overall data suggested that it wasn’t as important to them as the call feature. This information helped the product team to focus on developing or improving the features that were more essential to the users.</p><h4>3. Sharing designs via Phone</h4><p>Sending screenshots of designs to users and asking for feedback is another method used by BlackBuck. This method is particularly useful when the user is not available for a one-on-one or phone call interview. Sending screenshots of designs to users allows BlackBuck to gather feedback quickly and efficiently. It also allows users to provide feedback at their convenience, making it more likely that they will respond.</p><p>After the screenshots are shared, and once the user has responded to the message, we call the user for detailed feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrOuJNpVEgj3EPaGR3Vw5Q.jpeg" /><figcaption><em>Sharing designs on a phone is a time-effective way to test small features with a small user group.</em></figcaption></figure><p><strong>Limitations -</strong></p><p>While sending screenshots via WhatsApp to users for feedback can be a useful method, it does have its limitations. For example, some users may not respond quickly or require multiple follow-ups, making the feedback process slower and less efficient. Additionally, it can be difficult to convey complex navigation flows through screenshots alone, which can make it challenging to get comprehensive feedback on a design.</p><p>This method can only be used to gather feedback on a single-page design or to compare multiple options. When using this method, it’s important to be clear about the specific design or copy elements you’re seeking feedback on and to provide context for how the screenshot fits into the broader design. Additionally, it can be helpful to follow up with users to clarify any questions or concerns they may have and to ensure that you’re getting the most useful feedback possible.</p><p><strong>Research Example — Assessing the degree of correlation between Boss and BlackBuck and the change of app icon colour for users through testing</strong></p><p>Branding changes in the app icon that we wanted to test —</p><ol><li>Change from Boss Transporter to BlackBuck Transport.</li><li>Change of colour from red to black.</li></ol><p>Prior to making this transition, it was essential to determine whether our users could understand the new icons as we wanted to prevent them from experiencing any confusion while searching for our app on their mobile devices.</p><blockquote>Since it was just an icon we wanted feedback on, we thought it would be best to share a screenshot with the users.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*Aa0WTcU1dzDheyWczgbePQ.png" /><figcaption>We shared screenshots of a mobile screen with the users and asked them which app icon would they choose if they wanted to use the Boss app (erstwhile) to post loads.</figcaption></figure><p>Research Impact -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*DyPFOCgcb3ItEMNtktOXlg.png" /><figcaption>Users&#39; preference for Transport over Transporter was one of the main insights.</figcaption></figure><p>The research also provided us with another unique insight, revealing that the words “Boss” and “BlackBuck” were interchangeable for our users and that changing the app name or icon colour did not cause any hesitation in their decision to choose the app.</p><h4>4. On-site User Testing</h4><p>In some cases of Usability Testing, BlackBuck opts for going directly to the user. This is done through an interactive prototype made in Figma and then presented to the user to interact with.</p><p>For this method also, we visit transporters in their offices (usually in a transport hub where we can find multiple BlackBuck-using transporters in the same place). The researcher, with the help of a translator (if required), gives the user the context of the testing and then shows the prototype (of the feature to be tested) to the user to interact with.</p><p>During user interaction, observations are made on how the user is interacting and any friction points he is coming across while interacting. Post interaction, the researcher (at times) asks some questions with respect to the experience of the user.</p><p>Because the BlackBuck apps also support regional languages, the prototypes are also made in different languages depending on the area we choose for testing. Testing in Rajasthan would mean the prototype would be in English and Hindi. Whereas testing in Karnataka would require us to prepare the prototype in English and Kannada.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uiukTJ7eFT-ZyA2n" /><figcaption><em>Examples of multi-lingual sample screens that are used for testing, depending on the user’s app language.</em></figcaption></figure><p>One big advantage of this method is that the user has minimal disturbance to his schedule as the researcher conducts testing in his environment and hence, his comfort zone. So, the observation and feedback are more genuine and accurate.</p><p><strong>Limitation -</strong></p><ol><li>While this method is highly effective in knowing the actual response in normal scenarios, going directly to the user’s place may not bring accurate results in some cases. If there is a busy occasion for the majority of transporters like festivities, or if there is a sudden loading/unloading spike in the transport hub (and it happens at least once or twice a month), then the majority of transporters won’t be available for user testing. Even the ones who agree are often in a hurry so they might not give a very genuine response about their experience.</li><li>Since users are not familiar with the concept of testing, many have to be explained what a prototype is, and why they are asked to interact with it just like they would with an actual product.</li></ol><blockquote>“For instance, a user was once shown a prototype with made-up data, and he thought it was real. He could not understand why something made-up was being shown to him.”</blockquote><p><strong>Research Example — Finding out if the users were able to use the ignition on and off feature</strong></p><p>The lock and unlock feature is a crucial aspect of BlackBuck GPS and sets us apart from our competitors. This additional layer of security was promised to our users, making it vital that they know how to use it effectively.</p><p><a href="https://www.youtube.com/shorts/NyXWpiLCZuU">User testing of Ignition Lock/unlock</a></p><p>Research Impact —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*1_WkWY4RtnzZLq6w7hNIyg.png" /><figcaption>The testing involved both individuals who used GPS relay and those who did not, with the aim of understanding how everyone found the user experience.</figcaption></figure><p>The usability testing helped us validate the UX of the feature. The users were able to lock and unlock the ignition and understood words like ignition and relay.</p><h3>Conclusion</h3><p>At BlackBuck, we have experimented with and adopted multiple methods for user research and usability testing to overcome the limitations of a target audience that may not be very educated and tech-savvy. Through trial and error, we have been able to develop our own unique way to conduct research and usability testing to gather valuable feedback from its users and improve its product accordingly.</p><p>Special thanks to <a href="https://medium.com/u/63dc821dee26">Mayur Devatwal</a> and <a href="https://medium.com/u/a987ca99d680">Rishabhkumar Uday</a> for their insights and <a href="https://medium.com/u/3828c43f3945">Puranjai Pratap</a> for helping with the design of this blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4ecb747ad49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/identifying-the-needs-of-blackbucks-unique-user-base-a4ecb747ad49">Identifying the needs of BlackBuck’s unique user base</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helping Large Fleet Owners optimise their operations with a GPS web portal]]></title>
            <link>https://medium.com/blackbuck-design/helping-large-fleet-owners-optimise-their-operations-with-a-gps-web-portal-1e38a3fb14d7?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/1e38a3fb14d7</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[transportation]]></category>
            <dc:creator><![CDATA[Rishabh Kumar]]></dc:creator>
            <pubDate>Tue, 11 Apr 2023 08:04:04 GMT</pubDate>
            <atom:updated>2023-04-11T11:46:44.567Z</atom:updated>
            <content:encoded><![CDATA[<h4>BlackBuck GPS web portal design for Large Fleet Owners</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dO0pHAnZ6Nxx1PsAzVgMSA.png" /></figure><h3>Introduction: Who is an LFO?</h3><p>An LFO (or Large Fleet Owner), as the name suggests, is someone who has a large number of trucks under his ownership or management. LFOs are generally owners of sizeable transport enterprises that sometimes have a fleet of 100–150 trucks as well. This means that they handle more logistics than the traditional Fleet Owners (FOs) who mostly have 1–2 trucks in their management. At BlackBuck, every user with more than 10 trucks under their supervision is considered an LFO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GWSScDq74zq3WPuF" /></figure><p>In general terms, LFOs are more educated than regular FOs and are more tech-savvy as well. Since they handle a large volume of information regarding their trucks’ activities, they also sometimes use desktop-based applications. Few LFOs who don’t actively use desktop applications are at least used to seeing desktop-based interfaces. This is the major difference in terms of software usage between an LFO from an FO. FOs generally prefer mobile phone-based apps for their transportation needs while LFOs might also use desktop-based apps along with mobile apps to address their needs.</p><h3>Problem Statement: What were the main pain points of the LFO?</h3><p>Currently, a BlackBuck GPS user’s primary mode of access is through the BlackBuck app. The app provides all the information and features to the user, which enables the users to track their trucks while they are on the move, which they usually are. A regular FO, with 1–2 trucks under him, usually has a field-based job of going to places (other transporters’ offices, warehouses, truck workshops, etc). In some cases, an FO also drives one of his trucks, while subletting any other truck he has to another driver. Hence, tracking through a mobile-based app is an apt solution. However, in a case where the number of trucks is high, as is the case with LFOs, the mobile app starts to have some shortcomings.</p><p>To understand the problem, let’s assume an LFO with 150+ trucks under his management. This LFO is most likely to have the following problems while using the mobile app:</p><h4>Too many trucks to handle in the app</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sHsUAwmFk2d73nVneWSRXQ.png" /></figure><p>A case of 150+ trucks would mean that every truck will have its own set of information working independently. To access the detailed information of a single truck, currently, the user will have to select a truck from the vehicle list page to reach the vehicle details page. Once this information is accessed, to access any other truck information afterwards, the user will have to go back to the vehicle list page. This back and forth from the list to details becomes a tedious task for the LFO, who might have to check the status of 5–10 trucks together.</p><p><strong>An existing web portal was also there for the LFO. </strong>However, it had several problems within itself that are given below:-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hUimFA0NEL-Kk05TKzku2w.png" /><figcaption>Existing Web Portal for GPS by BlackBuck</figcaption></figure><h4>No way to manage the ‘share access’</h4><p>An LFO often has several people working with or under him. These people may either be the supervisors of his fleet of trucks or they can be stakeholders of the load getting transported through one of his trucks. The LFO, many times, has this requirement of sharing tracking access to these types of users. In order to do that, in the mobile app the LFO currently has to hit the share button present on the vehicle details page. The limitations for an LFO in this scenario are -</p><ul><li>The back-and-forth (mentioned earlier) occurs as he may need to share access to 4–5 trucks at a single point in time and there is no way to share access to multiple trucks at once in the mobile app</li><li>The LFO also has the requirement to stop the access after a certain point of time of his trucks which is again, not possible in the mobile app</li></ul><p><strong>In the web portal, there is no good way to share access.</strong></p><p>This leads to the LFOs resorting to sharing login IDs &amp; OTP for their account, which directly leads to unauthorized usage of multiple users other than LFO. And this is along with the pain point that sharing login ID and OTP in itself is a bit tedious task.</p><p>Hence, this portal was completely redesigned to address the earlier described needs better</p><h3>Solution Model: LFO Portal Revamp</h3><p>We decided to revamp the LFO portal that would open in the web browser. This was done taking into account LFO’s usage patterns and our competitors’ responses to LFO’s needs as well. The following guidelines were laid out for the new LFO portal -</p><ul><li>Switching between different truck details should be easy</li><li>Sharing tracking access should be enabled for multiple trucks</li><li>A page shall be dedicated where the LFO can stop sharing access for a particular set of trucks (manage shares)</li><li>All major tracking features would be enabled barring a few controls (ignition lock for a truck)</li></ul><h4>Constraints</h4><ul><li>There has to be an element of familiarity with the mobile version of GPS as the user will be transitioning from there only</li><li>The tight schedule of this project would mean that components must be taken from existing web portals of the BlackBuck app to save time on building the pages</li></ul><h4>Revised User Flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Kq_rAZdEeLw0h4J" /></figure><h3>New Design</h3><p>The new design was made keeping in mind the guidelines to be fulfilled. Upon refining the user flow, UI was designed and prototyped in Figma. Following are the main interactions that were looked upon.</p><h4>Landing Page</h4><ul><li>The landing page was designed to give maximum real estate to the map to allow easier searching of vehicles through the map itself.</li><li>Elements from the mobile app as well as the old portal were taken and integrated into the new design.</li><li>Filters were added alongside the search bar for quicker &amp; easier finding of the vehicle.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fK1OjMFRgf5qnuKhpe9Wyg.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fpfc6nw_chJg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dpfc6nw_chJg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fpfc6nw_chJg%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/34c3c4dd3a87e37023e1594c0d52b808/href">https://medium.com/media/34c3c4dd3a87e37023e1594c0d52b808/href</a></iframe><h4>Opening Vehicle Details section from Landing Page</h4><ul><li>Once the user selects/clicks a vehicle on the list, the vehicle details section of that vehicle will open as a drawer adjacent to the list.</li><li>This design made it easier for the user to switch between different vehicles on the vehicle list page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0y9Yo7s76iHzSAfkIRwDTg.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZ3U3FA1Q3ds&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZ3U3FA1Q3ds&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FZ3U3FA1Q3ds%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/67297e0b630f825a11b78a17a3b0157c/href">https://medium.com/media/67297e0b630f825a11b78a17a3b0157c/href</a></iframe><p><strong>Details section main buttons</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCDRW75A7g-CaKhvROJNxQ.png" /></figure><h4>Change Date / Time of Vehicle Detail Section</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JtP-Kgo6PLEFu5md5iVIhA.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqYWcuii9o7M%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqYWcuii9o7M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqYWcuii9o7M%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/a13b999d916f070e32f9a74966c49e74/href">https://medium.com/media/a13b999d916f070e32f9a74966c49e74/href</a></iframe><h4>Play Trip History from Vehicle Detail Section</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5uOP7fTcUI3ZCgxi0c4umg.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKE94_EdsT_8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKE94_EdsT_8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKE94_EdsT_8%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/2469cca48baa890e09574f81007b10b8/href">https://medium.com/media/2469cca48baa890e09574f81007b10b8/href</a></iframe><h4>Share Dashboard Access from Vehicle Detail Section</h4><p>Sharing can be done globally as well from the share button on the Landing Page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uToa6UmHMjbaiVY_XD5C0g.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6m67QYb402Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6m67QYb402Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6m67QYb402Q%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/010b3d435a06133c1de3c5e1169ae939/href">https://medium.com/media/010b3d435a06133c1de3c5e1169ae939/href</a></iframe><h4>Manage Share Accesses of LFO</h4><p>Upon sharing, there is also a separate page made for managing the shares. It is accessible through the manage shares option of the profile drawer, opened after the profile button clicks on the landing page. This feature was resourceful especially to the LFO as it now gave them the control to share more or stop sharing once the share credentials were generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kQVgEdCkil9TlLq49fCbw.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQdgmUp-72f8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQdgmUp-72f8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQdgmUp-72f8%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/836f73bbe7bfa43583939742887a26fe/href">https://medium.com/media/836f73bbe7bfa43583939742887a26fe/href</a></iframe><h4>Vehicle distance/time calculation from a user-selected place</h4><p>Apart from all this, another feature of measuring the time &amp; distance of the vehicle was included to reduce the general calculation efforts of our user.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fu2C9Cse8L48%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Du2C9Cse8L48&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fu2C9Cse8L48%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/de2b5a97ec1d74b76b124eb0837ceb5b/href">https://medium.com/media/de2b5a97ec1d74b76b124eb0837ceb5b/href</a></iframe><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_ljsbRpb-jJYbcmP0cMew.png" /></figure><p>The LFO Portal was my first project when I joined BlackBuck. The experience and perspective gained (of how transporters operate) through this project were immense by the time. Now when I think about it, it set me up nicely for the next projects of BlackBuck.</p><p>Thank you so much if you have reached this far. Highly appreciate you taking the time to read this. I hope you enjoyed it. Cheers!!</p><h3>Acknowledgement</h3><p>Big thanks to <a href="https://medium.com/u/fc1da27e48c8">Chandra Utkarsha</a> and <a href="https://www.linkedin.com/in/shubham-kumar-56196164/">Shubham Kumar</a>, my Product Managers for their help and contribution to this blog, as well as to this whole project. They were one of the main advisors and facilitators during the project. Thank you very much for providing the user-based data and research wrt this blog.</p><p>Another big thanks to <a href="https://medium.com/u/63dc821dee26">Mayur Devatwal</a>, my Design Head, to help me structure this blog. He was also one of the main advisors during the project. Thanks for your guidance and support.</p><p>Special thanks to <a href="https://medium.com/u/7fd4875a4263">Greeshma Rawat</a> for her help with the content appropriation of this blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e38a3fb14d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/helping-large-fleet-owners-optimise-their-operations-with-a-gps-web-portal-1e38a3fb14d7">Helping Large Fleet Owners optimise their operations with a GPS web portal</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choice Architecture — You are being nudged!]]></title>
            <link>https://medium.com/blackbuck-design/choice-architecture-you-are-being-nudged-61043337830a?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/61043337830a</guid>
            <category><![CDATA[decisions]]></category>
            <category><![CDATA[choice-architecture]]></category>
            <category><![CDATA[nudge]]></category>
            <dc:creator><![CDATA[Jyotika S]]></dc:creator>
            <pubDate>Thu, 02 Feb 2023 06:41:13 GMT</pubDate>
            <atom:updated>2023-02-02T11:52:50.546Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Choice Architecture — You are being nudged!</strong></h3><p><strong>Are your decisions really yours? Find out more about the Choice Architecture and the Nudge Theory.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Afu0k3bMZbSlbney" /></figure><p>Imagine you went to a supermarket to buy a cosmetic product of a brand you prefer. While walking down the aisle of the supermarket, you noticed the sale/offer signs on the shelves. The product that you wanted was right there with a buy 1 get 1 free offer. Though it was not the brand you wanted, it was still a tempting offer. This brand was more expensive but you were getting two products for the price of one! The next moment, you were heading to the payment section with this brand that you had no intention to buy in the first place.</p><p>It’s only later you realize you had spent more money than intended. How did you change your decision to buy the product of some other brand and also paid more? <strong>This is Choice Architecture.</strong></p><blockquote>When we make choices, we are constantly influenced by cues in our environment. The cue can be either intentional (the way a product is designed) or unintentional (the way a store is laid out).</blockquote><p><strong>What is Choice Architecture?</strong></p><p>Choice Architecture is the way the choices are presented to us to influence our decision-making. Our surroundings play a major role in how we make our choices.</p><p>For example, a well-planned footpath will encourage people to walk instead of driving or taking public transportation. Food dishes kept in front of a big table are more likely to be consumed by people at a dinner party. In the supermarket example discussed earlier, we see how a consumer’s decision was influenced by directing their attention to the sale/offers.</p><blockquote>There was a gentle nudge, an implicit suggestion, to select a particular option rather than forcing it.</blockquote><p><strong>How does it work?</strong></p><p>There is a whole framework of behavioural economics that backs the theory of Choice Architecture. But to keep things simple here, there are principles of structuring choices and feedback that plays an important role in employing nudges for decision-making.</p><p>Choice architecture takes into account how our mind works. It leverages our cognitive biases. As humans we want to make the best decisions but in a quick and simple way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VQKepX9I1MKUHfNzfUgAZQ.jpeg" /></figure><blockquote>Keeping this in mind, we are, almost on a daily basis, nudged towards different choices. Ultimately, the decision making is not forced and people remain free to choose from the options available. But the fact that something so simple can change our decision-making process is fascinating.</blockquote><p><strong>Choice Architecture in Retail:</strong></p><p>One of the best examples of choice architecture is the retail industry. How products are placed and where they are placed — whether we see them first or are they placed at eye level — makes us more likely to buy them. Below are a few examples where we may observe choice architecture playing an important role. Knowingly or unknowingly we are using this to organize the everyday parts of our lives. I have tried to break down a few examples in our physical surroundings, where we see things sorted in a certain order to grab customers’ attention.</p><p><strong>Example 1: </strong>‘Cream and Lotion’ section in a supermarket</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*86T4bu1HL3zc4Sqa" /></figure><p><strong>How products are organized in the ‘cream and lotion’ section:</strong></p><ul><li>On the middle shelf, at eye level, you will find all the body lotions from well-known companies in medium/large bottles.</li><li>Brands that are less well-known or cheaper are placed below that.</li><li>Smaller bottles are placed at the very end.</li><li>In the top section, there are products of various brands.</li></ul><p><strong>Example 2: </strong>Clothing store</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sFHI3yWQTm1YAho0" /></figure><p><strong>How products are organized:</strong></p><ul><li>Just at the entrance, there will be an accessory section.</li><li>After that western wear is displayed with the discount. The products with exclusive brands with no discount will be displayed in between.</li><li>There will be a separate section for Indian wear displaying daily wear clothes in the starting and heavy suits at the end</li><li>Near the billing counter, there will be a section of artificial jewellery and small items for eg: hair accessories, socks, perfumes, lotions, small pouches etc</li></ul><p><strong>A few more examples:</strong></p><p><strong>How shelves are organized at Starbucks Cafe</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/0*TRBvVaccqCcGuTsx" /></figure><p><strong>Chocolate Rack near the billing counter</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*n2PQOZkFpXfnd_WcPEFkyg.png" /></figure><p>Although choice architecture is a broader phenomenon, I have tried to scratch the surface here by analyzing our surroundings.</p><p>Whether we are aware of it or not, Choice Architecture affects a lot of our choices on a daily basis. So the next time you see a product displayed in a certain way, pause and consider why it is displayed that way.</p><p>I appreciate your time reading this!</p><h4>Acknowledgements</h4><blockquote>Special thanks to <a href="https://medium.com/u/63dc821dee26">Mayur Devatwal</a><em> </em>and <a href="https://medium.com/u/7fd4875a4263">Greeshma Rawat</a> for their valuable feedback for the refinement of this blog.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61043337830a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/choice-architecture-you-are-being-nudged-61043337830a">Choice Architecture — You are being nudged!</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it takes to design a user-friendly theft protection feature for trucks!]]></title>
            <link>https://medium.com/blackbuck-design/what-it-takes-to-design-a-user-friendly-theft-protection-feature-for-trucks-2ab7f242dcb4?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/2ab7f242dcb4</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[theft-prevention]]></category>
            <category><![CDATA[transportation]]></category>
            <dc:creator><![CDATA[Rishabh Kumar]]></dc:creator>
            <pubDate>Tue, 24 Jan 2023 09:08:37 GMT</pubDate>
            <atom:updated>2023-02-08T09:59:17.845Z</atom:updated>
            <content:encoded><![CDATA[<h4>GPS Theft Protection (Relay) Design — Part 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J0k-fvkQapVHhiMtgZIMRg@2x.png" /></figure><h3>Introduction</h3><p>In the last part of this blog series (<a href="https://medium.com/blackbuck-design/how-is-blackbuck-helping-truck-owners-prevent-truck-theft-c2b3b5be86c5">How BlackBuck’s Telematics helps you keep a hawk-eye over your trucks</a>), we discussed the importance of robust telematics solutions, described how our theft protection (relay) functions in a vehicle and how it’s controlled through the GPS app of BlackBuck. However, like all product design journey, the Relay feature in its first version had room for improvement in its design. In this part, we are going to describe in detail what were the hits &amp; misses in our first version, how we approached them in our reiteration and how we eventually reached the new design of Theft Protection (Relay).</p><h3>Problem Statement</h3><p>This was the initial process to lock/unlock the ignition through the app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehetU9oU8WggP0hjsSACAg@2x.png" /></figure><p>In this case several problems were found in both UX and UI fronts.</p><h4>UX Problems Found</h4><p><strong>#1. Setting wrong expectations for the User:-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXOZ6F7JaKOyQf_I2TNw9w@2x.png" /></figure><p>Since there is no prior intimation of the next step, the user expects the ignition to be locked/unlocked instantly, which is not always the case. There are a few edge cases where this process takes time. But this information is not shared with the user. And when the lock/unlock takes time, the user assumes that the page or app is malfunctioning — clearly not a good user experience.</p><p><strong>#2. Poor handling of Exception:-</strong></p><p>Speaking of exceptions, lock ignition has primarily two of them:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sm7EYAE3WfCaOAUL79uEaA@2x.png" /></figure><p>As shown in the figure above, the unanswered questions arise because these states are not treated like exceptions. Rather, they are treated like an add-on step which sometimes confuses the user.</p><p><strong>#3 Unexpected and unexplained changes in controls</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-jWvASEmgupfgRhyU5JVg@2x.png" /></figure><p>In the lock/unlock process, once the sending of the ‘lock’ signal is complete, the option to cancel lock/unlock is removed without any prior explanation. This is done because after the signal is sent to the truck, the lock/unlock process becomes irreversible from the back-end.</p><h4>UI Problems Found</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qzEtUYOmVpeYpQnw4czRfw@2x.png" /></figure><h3>Solution Process</h3><p>Once the problems were specified, we worked on a viable solution through:-</p><ol><li>Analytics Review and Stakeholder Discussions</li><li>Revised User Flow</li><li>Design Concepts</li><li>Final Design</li></ol><h4>Analytics Review &amp; Stakeholder Discussions</h4><p>We checked the overall distribution of time taken to complete a lock/unlock process. Based on the numbers, we were going to decide what approach to take for the solution model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*cT_3C7_tF0vJIpvhmd3bYw.png" /><figcaption>Numbers in approximate figures</figcaption></figure><p>Based on the distribution and the problems specified, several guidelines were laid out:-</p><ul><li>In the majority of cases, the lock/unlock happens within 1 min. Hence, it was decided that the new design would be focused more on that strata. Since the interaction would last for 1 min in most cases, the overall process of <strong>lock/unlock would be seen in a direct and upfront manner by default when initiated. </strong>The user would be given the option of leaving that upfront view whenever they feel so.</li><li>In case the user exits the upfront view, <strong>a secondary notification component would be present (to inform him of the ongoing progress of lock/unlock in the backdrop) in the truck list and details page</strong>.</li><li>The difference in nature of the ongoing lock/unlock process (initiated &gt; in progress &gt; successful) will be shown evidently in the new design.</li><li>Messaging will be regularised throughout the UI.</li><li>Controls, when needed to be disabled, will be disabled with proper reason given to the user.</li></ul><h4>Revised User Flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tRiswTVHksyvbdMuX4gN0g.png" /></figure><h4>Design Concepts</h4><p>Initially, two iterations were made and their UI analysis was done to differentiate their pros and cons. We then took the pros and cons of both the iterations into consideration and then combined them to design the final iteration, maximising the pros and eliminating the cons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TU2zrYKzYi9w3hYg4VIHdA@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cq5SbQnhqikUlVZSIGULpg@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIqsSXJEueMYCrDE2_514Q@2x.png" /></figure><h3><strong>Final Design</strong></h3><p>Following all the iterations, we came out with the final solution which was later implemented into the application.</p><p><strong>Here below are the Final Design Snippets:</strong></p><h4>Main Screens</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2MRAQi8Bb15nZb3F2Qs6g@2x.png" /></figure><h4><strong>Revised Lock Process</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpSBhsHALwJ4c7GmDrXdwQ@2x.png" /></figure><h4><strong>Revised Unlock Process</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yCDc-Y2P4dMPZcIschfpRQ@2x.png" /></figure><p>You can also view Final Design Prototype below</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FfedykD5Nky8&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DfedykD5Nky8&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FfedykD5Nky8%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/50d23f624d25c579248ef40c30592944/href">https://medium.com/media/50d23f624d25c579248ef40c30592944/href</a></iframe><h3><strong>User Testing of Design</strong></h3><ul><li>Post design completion, to verify the usability of the new Relay (Ignition) lock/unlock pages, we went to a transport hub based in Yeshwantpur, Bangalore.</li><li>There we tested out the new design with 5 randomly picked local truck owners. 3 of them had relay installed in their trucks while 2 were non-relay users of BlackBuck.</li></ul><h4>The gist derived from testing</h4><ul><li>Relay users went through the lock/unlock flow easily and by themselves.</li><li>They understood the colour concept used for lock/unlock.</li></ul><p><a href="https://youtube.com/shorts/NyXWpiLCZuU?feature=share">User testing of Ignition Lock/unlock</a></p><blockquote><strong>One user commented while going through the flow:</strong> “Red matlab lock, green matlab unlock. Yellow bole to thoda thoda lock ya thoda thoda unlock.” (Red means lock, green means unlock. If its yellow its either a little locked or a little unlocked.)</blockquote><p>The non-relay users were intrigued by the screens shown. After going through the flow, they started enquiry with us for relay Installations.</p><blockquote><strong>A non-relay user commented:</strong> “Acha ye relay kitne ka aata hai?”<em>(how much does this relay cost?</em>)</blockquote><p>We took these results as <strong>usability verified</strong> and finally handed over the design to the developers to be implemented.</p><h3>Conclusion</h3><p>The redesigning process taught us many things — how to identify the correct problem statement, dealing with each scenario is important, being helpful and transparent to users is the priority and user testing at an early stage will always give you the right feedback at the right time.</p><p>The project has so far resulted in a smooth adoption and understanding of relay lock/unlock features by the users. What earlier used to be somewhat hidden in between the other details of the truck, now appears upfront to the users when activated, giving users the clarity of what’s happening. Earlier, relay/lock unlock was treated as a complex thing (by the users) with unknown steps. Now, comprehensively it is getting treated like a simple tool that is easy to use and is involved in the day to day life of the user.</p><p>Thank you very much for taking your time out to read this. We hope you found it interesting. Cheers from BlackBuck!</p><h4>Acknowledgement</h4><blockquote>Thanks to <a href="https://medium.com/u/63dc821dee26">Mayur Devatwal</a> (My design head and mentor of this project) for his expert guidance towards this blog as well as this project. Big thanks to <a href="https://medium.com/u/fc1da27e48c8">Chandra Utkarsha</a> and Shubham Kumar for their vital feedbacks and help wrt this whole project.</blockquote><blockquote>Special thanks to <a href="https://medium.com/u/7fd4875a4263">Greeshma Rawat</a> and Amrutha Raman for their vital refinement works into this blog</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ab7f242dcb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/what-it-takes-to-design-a-user-friendly-theft-protection-feature-for-trucks-2ab7f242dcb4">What it takes to design a user-friendly theft protection feature for trucks!</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why humanization and localization of product is critical in fueling digital inclusion in Bharat …]]></title>
            <link>https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-1cc7fbe8f719?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/1cc7fbe8f719</guid>
            <category><![CDATA[trucking]]></category>
            <category><![CDATA[product-localization]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[digital-india]]></category>
            <dc:creator><![CDATA[BlackBuck Design]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 05:54:09 GMT</pubDate>
            <atom:updated>2022-12-21T05:54:09.825Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why humanization and localization of product is critical in fueling digital inclusion in Bharat - PART II</h3><p>Product copy impacts the way people interact with a product. In this part, we discuss how localized and humanised our product copy to create familiarity and trust in our product.</p><p>By Greeshma Rawat &amp; Devrat Singh</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGCtypXUFgWA5azBsLtoGw.png" /></figure><p><strong>Recap</strong></p><p><a href="https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-c87bb3700bdc">Part 1</a> of this blog talked about the growing need for the localization of our product. We found out what our users needed and validated it through usability testing and user research. The end goal was for our users to be able to use our product on their own and with ease.</p><h3>Getting down to the Brass tacks of Product Localization</h3><p>In this second part, we aim to go deeper, give you a sense of what product localization really means and take you through the nuances and challenges while creating our product copy — easy, conversational and colloquial.</p><h3>How did we solve the problem?</h3><p>Solving this problem statement was a daunting task with over 30 thousand strings to be translated into four new languages for over 1000 app screens. And that was just the output displayed to the user. There were information input flows across the app that needed to support the same languages in the keyboards, character limits and suggestions for these inputs. All of this was broken down into multiple steps that eventually took us almost 8 months to solve.</p><h3>Step 1: Establish the Product Voice</h3><p>The first and foremost requirement was to figure out the Voice of our Product. Based on the user’s needs, we wanted our tone to be conversational and colloquial and our language to be clear and precise.</p><ol><li><strong>Day-to-day conversational</strong></li></ol><p>We wanted to speak to them just like they would in day-to-day conversations with a friend, while also keeping it crisp and contextual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G7gD6XjQF9VOxdigV-Zj-A.png" /><figcaption>After truckers (our users) call transporters for loads: The changes here are subtle but effective. We made the feedback copy simpler, crisper and more specific to our users’ problems.</figcaption></figure><p>2. <strong>Transparent</strong></p><p>It is very important to give the users the right information (without alarming them) to gain their trust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hyUrXu5uNpFyy48dwJ7XCQ.png" /><figcaption>When a user buys a FASTag: In the older version, there was no single screen with step-by-step information on the transaction process. The new version helps identify all the steps from making a payment to the delivery and activation of the FASTag and gives all the necessary information on the same page.</figcaption></figure><p>3. <strong>Helpful</strong></p><p>We do not want the users to think they do not have enough information to make smart decisions for themselves. We want to help them understand why they are doing what they are doing!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JS60e-gL543PowAquaP8Hw.png" /><figcaption>Truck ignition lock feature in GPS: Version 1 was information overload. Hence for the new copy, we fixed the information architecture, giving the key information the users needed first.</figcaption></figure><h3>Step 2: Setup a Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6uU-zaE2usUD4WS2h7dnw.png" /></figure><h3>Step 3: Build Product Capabilities</h3><p>With all the processes in place, we moved on to building the translation capabilities throughout the app. These involved 2 parts:</p><ul><li>Built translation capabilities for all the texts across the app (all information outputs)</li><li>Built flows for vernacular keyboards and translated suggestions while searching (all information inputs)</li></ul><p>Since we are an app with multiple categories, this was done one category at a time and took a total of 4–5 months.</p><h3>Step 4: Collect User Feedback</h3><p>Post the launch of the first set of translations, we also started conducting user immersion sessions in parallel to take feedback on the translation quality. This was done on a large scale with over 100 users. With increased interaction with our users, we learned not to take our understanding of things as absolute. Some of the learnings were:</p><ul><li>The language has to be at its simplest and in a way they understand.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6a0uGduNyF5Sy0taYCRpA.jpeg" /><figcaption>Feedback from a trucker after his call to the transporter: While the copy was simple before, we found that most truck owners used the word ‘Deal’ for their truck being placed or not. The new copy is crisper and speaks the language of a truck owner. No frills and on-point.</figcaption></figure><ul><li>Since we live in a country with diversity in culture and language, the understanding of certain words and phrases in different parts of the country is not the same. It was important for the copy to be colloquial and contextual. Example — Words like Bid and POD (Proof of delivery) are understood by most people from the South of India. But in the North, Boli (बोली) for Bid and Pohoch (पोहोच) for POD are more commonly used. For users with Hindi as their app language, we decided to use these words instead.</li><li>The user feedback also brought forth another interesting observation. We realized that we need not do a pure translation of every word. In fact, some words and phrases are more commonly used in English (even by non-English speaking people)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A_0HgjWXIFNFUAVPCCw_xg.jpeg" /><figcaption>Some commonly used words are better transliterated and for some, an easier alternative of the native language should be used</figcaption></figure><h3>Step 5: Introduce Language Selection Option</h3><p>Finally, after all this, it was time to introduce the language selection option to the users across the user journey. We introduced the language selection screen in the signup flow for new users and on the home screen for old users. The hierarchy of language options on the app was based on the city of the user with English always being the second option. For example, a user in Kanpur would see Hindi first, English second, followed by other languages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hi1ryJbkgcODBouKtVJBmg.jpeg" /><figcaption>Drop down of the languages and small nudges of the language options were provided across the app for the users to choose/shift to their language of convenience.</figcaption></figure><h3>What was the outcome?</h3><p>Gathering such fine insights and customizing our product for non-digital natives helped us gain tremendous trust in the trucking community. We spent several months reiterating the smallest of the product features based on our user feedback, preferences and behaviours. The outcomes that we have been seeing since have been very inspiring. Here’s the impact in numbers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UdaQGC-hS5qSoui3" /></figure><h3>Conclusion</h3><p>Working on a helpful and engaging product experience while maintaining consistency in language and tone is an ongoing process. With the processes that we have established, we hope to improve our conversation with our users at every stage. The learnings, the un-learnings and the grassroots level impact that has been able to create so far have been very encouraging for BlackBuck; making us believe that we are moving in the right direction in our journey of building tech for Bharat and digitizing the trucking ecosystem at scale.</p><p>But this is just the tip of the iceberg. We are geared and excited to innovate, build and design several more compelling products that will drive the future of trucking…</p><p><strong><em>Blog design by Puranjai Pratap</em></strong></p><p><em>Read Part 1: </em><a href="https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-c87bb3700bdc"><em>https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-c87bb3700bdc</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cc7fbe8f719" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-1cc7fbe8f719">Why humanization and localization of product is critical in fueling digital inclusion in Bharat …</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How BlackBuck’s Telematics helps you keep a hawk-eye over your trucks]]></title>
            <link>https://medium.com/blackbuck-design/how-is-blackbuck-helping-truck-owners-prevent-truck-theft-c2b3b5be86c5?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/c2b3b5be86c5</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[prevent-vehicle-theft]]></category>
            <category><![CDATA[trucking]]></category>
            <category><![CDATA[gps-tracking-device]]></category>
            <dc:creator><![CDATA[Rishabh Kumar]]></dc:creator>
            <pubDate>Wed, 14 Dec 2022 09:20:38 GMT</pubDate>
            <atom:updated>2023-02-08T09:58:20.198Z</atom:updated>
            <content:encoded><![CDATA[<h4>GPS Theft Protection (Relay) Design — Part 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IyuI6QlFFCUXyhDOdl7J0g.png" /></figure><p>According to Niti Ayog’s report 40 lakh + trucks move around 70% of the domestic freight in India making trucking the main facilitator of the movement of goods and products in the country. Even though it plays a crucial role in the transportation sector, trucking is one of the least digitised industries and faces many challenges: delays, thefts, unloading at wrong locations etc. Ensuring that goods reach the growing consumer base on time, and in the proper condition requires constant technological advancements, especially, in the field of fleet tracking.</p><blockquote>For a truck carrying a load worth lakhs, its safety becomes primary for both the truck owner and the transporter. That’s where the Telematics commonly known as GPS comes in. GPS for commercial vehicles are specially designed to help the fleet operators track their fleet’s location and increase business efficiencies through its various features.</blockquote><p>At BlackBuck, our mission is to solve every need of a trucker and we realized for fleet operators, intelligence on their truck movement can be a huge of sigh of relief and also help them make informed decisions.</p><p>In this blog, we will take you through the benefits of having a robust telematics solutions and in particular, will throw light on our ‘Relay’ feature specifically designed to prevent and protect fleet operators from truck thefts.</p><h4>Many facets of Telematics</h4><p>BlackBuck’s telematics solutions is tailor-made to help fleet operators to manage his fleet better. It enables the fleet operator aka a trucker to keep track of their trucks from loading to unloading points, ensures that safe driving practices are followed and truck thefts are prevented. Here are some of the benefits offered to our truckers -</p><ul><li>Tracking of live location of your truck</li><li>Minimization of calls to the driver for location updates</li><li>Tracking of fuel consumption based on the distance covered</li><li>Number of stops and distance travelled during the trip</li><li>Notifications of unusual stoppages and lengthy low network periods</li><li>Detailed reports of driving behaviors — over speeding, harsh braking/acceleration/cornering etc.</li></ul><h3>Not just another GPS!</h3><p>GPS devices in its existing avatar in the market has its limitations and they aren’t really customised for Commercial Vehicles. BlackBuck understanding the need for customisation and wanting to bring value addition to a trucker’s life, brought in a more holistic approach. We added intelligence layers that has its own set of secondary features making it a double threat to all kinds of ‘buri nazars’.</p><p>One such essential feature is <strong>Theft Protection (Relay) Device Controls and Installation</strong>. Thefts of in-transit trucks carrying loads are a major reason why many truck owners are wary of sending their trucks on new routes. Even with the GPS device installed, the most they can do is track their trucks and call drivers for any unusual activities they notice.</p><blockquote>But with the added Theft Protection (Relay) layer, a user can switch off the ignition of the truck from our app itself, making it a key and must-have feature in preventing truck theft.</blockquote><h3>What is a Theft Protection Device (Relay)?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Qf0X2pdyGYXitmfr" /></figure><p>It is a device that is fitted into a truck for its ignition to be locked or unlocked (through the app) by the user. The user, in this case, is a Truck Operator. Theft Protection (Relay) is only useful if the truck has a GPS. The user finds out the location of the truck through the GPS and decides when he wants to lock/unlock the ignition. BlackBuck’s telematics solution offers a trucker both the GPS device and an added protection layer through Relay.</p><h4>Why is it important?</h4><p>Theft Protection (Relay) acts as a security feature in possible cases of vehicle/load thefts. When trucks are parked in remote locations or have not moved in a long time, the truck owners can lock the ignition from the app and secure the trucks.</p><h4>How does Ignition Lock/Unlock work?</h4><blockquote>Once the user locks the ignition of a truck via the app, one cannot start the truck manually (key insert and turn to start). The only way the truck will start again is if the user on the other side unlocks the truck through the app.</blockquote><h3>Case Study</h3><p>To demonstrate the critical role the Relay feature can play in preventing a theft, let us simulate a scenario for you:</p><blockquote>Mohanlal is a small fleet operator in Kerala who owns three trucks. He also has three permanent drivers who have been working for him for over 7 years. Mohanlal has been in the business of trucking for the last 15 years and until 2 years ago was largely running his operations traditionally with barely any digital interventions.</blockquote><blockquote>Cut to 2022, thanks to the digital push during the pandemic, he now has warmed up to smartphones. He extensively uses BlackBuck’s telematics solutions. Today, all three of Lal’s trucks are fitted with BlackBuck GPS and Relay, he has access to monthly reports of the driving patterns and monitors each of his truck’s movement on his phone.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7y_z7fh4xYREMZBQtUU5Pw.png" /></figure><blockquote>One day, one of Mohanlal’s loaded trucks was on its way to Hyderabad from Jaipur. On the second day of the trip, when the driver had parked the truck at a resting spot for the night, a thief conspired to steal it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gDAklof7KqxMyLII" /></figure><blockquote>Fortunately, since Lal had the Relay device fitted with his GPS, he was able switch off the truck’s ignition remotely through his phone whenever there was a prolonged period of stoppage. So, when his driver stopped at the resting stop, Lal by default activated the Relay feature. When the thief tried to start the vehicle multiple times he was unable to do so, leaving him baffled.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEXNWNSDdPQ4F06hM--Vkw.png" /></figure><blockquote>Eventually someone noticed the thief on the truck and alerted the driver. The thief was caught and handed over to the police.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8Ef8tfkkwHzWgBi8c6FFw.png" /></figure><blockquote>“Thank God I had the Theft Protection Device installed in the truck. Every time the driver parks the truck at night, I switch off the ignition from my app. This way, I know no one can steal my truck.” says Mohanlal</blockquote><p>Trucks carrying goods are highly vulnerable to thefts. The incident described above is extremely common than one might think and the cost of losing a truck along with goods can put a trucker in debt for life and sometimes even out of business. To be able to control and protect the truck anywhere, anytime is a game-changer for a small fleet operator in India.</p><p>It is because of this that today, 1 in 5 trucks in India use BlackBuck’s Telematics Solutions. The GPS device coupled with the Relay feature is helping lakhs of our truckers keep a close eye on their trucks and its safety. However, we have barely scratched the surface and we have been constantly improving our offerings and product design based on the engagement and user behaviour.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FfedykD5Nky8&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DfedykD5Nky8&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FfedykD5Nky8%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/50d23f624d25c579248ef40c30592944/href">https://medium.com/media/50d23f624d25c579248ef40c30592944/href</a></iframe><p>In our next and final installment in the telematics series, we will take you through at greater lengths about what went behind designing the Relay feature on the app, how does a user (fleet operator) interact / engage with this feature and how we have been improving user experience.</p><p><em>To be continued…</em>.</p><h4>Acknowledgement</h4><blockquote>Thanks to <a href="https://medium.com/u/63dc821dee26">Mayur Devatwal</a> (My design head and mentor of this project) for his expert guidance towards this blog as well as this project. Big thanks to <a href="https://medium.com/u/fc1da27e48c8">Chandra Utkarsha</a> and Shubham Kumar for their vital feedbacks and help wrt this whole project.</blockquote><blockquote>Special thanks to <a href="https://medium.com/u/7fd4875a4263">Greeshma Rawat</a> and Amrutha Raman for their vital refinement works into this blog</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2b3b5be86c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/how-is-blackbuck-helping-truck-owners-prevent-truck-theft-c2b3b5be86c5">How BlackBuck’s Telematics helps you keep a hawk-eye over your trucks</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why humanization and localization of product is critical in fueling digital inclusion in Bharat —…]]></title>
            <link>https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-c87bb3700bdc?source=rss----c872c2d218b6---4</link>
            <guid isPermaLink="false">https://medium.com/p/c87bb3700bdc</guid>
            <dc:creator><![CDATA[BlackBuck Design]]></dc:creator>
            <pubDate>Thu, 13 Oct 2022 12:05:37 GMT</pubDate>
            <atom:updated>2022-10-13T12:05:37.377Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why humanization and localization of product is critical in fueling digital inclusion in Bharat — Part 1</h3><h4>For the next billion users, localisation creates familiarity and trust in the product. Read to find out how we made our product speak the language of our users.</h4><p>By Greeshma Rawat &amp; Devrat Singh</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UjyhSZV_LYlOf-t7Ymqe9A.png" /></figure><p>India is predominantly a vernacular country. Out of its 1.4 billion population, only 140 million people (~10%) speak English and less than 0.1% speak English as their first language in India.</p><p>Language today is arguably the biggest critical barrier to digital inclusion in India. While the country is experiencing a digital revolution, is digital truly inclusive in India? Despite the country being multi-lingual, English continues to be the dominating language of most digital products that are available today and some of the devices in the market also don’t support vernacular fonts creating an added layer of complexity in building apps for Bharat.</p><p>Legacy industries particularly such as transportation and Logistics are the types of industries where the literacy of English is well below the standard 10%. At the same time, these industries are undergoing digital transformation with mandates like Fastag, and GPS coming into effect. If a trucker sitting in a remote village needs to adapt to digital, he needs a trustworthy digital partner, an app that is easy to use, technology that is empathetic to his limitations and most importantly is in his language of convenience.</p><p>Truckers in India are the last bastion to be included in the digital economy. He is a different user from a regular eCommerce consumer, localization and humanization of the user product experience is extremely paramount in gaining the trust of the trucking community. And this is what we have been doing at BlackBuck; continuously understanding the nuances of the trucking ecosystem to customize and better our product offerings. The journey hasn’t been easy though! We made mistakes, we listened, we learnt and we went back to the drawing board when we had to.</p><p>In this two-part blog series, we attempt to give you a peek into what goes behind designing tech products for the underserved small fleet operators of India and the several insights that emerge along the way…</p><h4><strong>A Typical BlackBuck User and His Needs</strong></h4><p>First, let’s understand the demography that is using our BlackBuck app. A typical user in this highly unorganized and undigitized industry has the following persona:</p><ul><li>Male, typically in his 30s/40s.</li><li>Class 8 or 10 graduate.</li><li>Not tech savvy but has a basic understanding of the core functionalities like ‘scroll, search etc., that are common across apps.</li><li>English is not his first language. Only a handful in his community/peer group can read and write basic words in English.</li><li>On average receives or makes 50+ work calls a day. Has limited mental bandwidth to ‘explore’ apps.</li><li>Trust in online platforms is very low and the onus lies on the tech platform to gain his trust.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D4KN4mYV0Zph3uCC" /><figcaption>Most truck owners still depend on paperwork for daily operations.</figcaption></figure><p>Such a user needs a lot of convincing and handholding throughout the adoption journey. And if this needs to be done at scale it requires a combination of human touch and a superior product experience. On the one end, we laid the foundation for a large distribution network with people deployed across 14,000 pin codes of the country and on the other, an app that is highly customized for a trucker. A fleet operator, unlike your urban consumer, is not willing to invest in a product or a service for the sake of convenience. This customer is struggling day in &amp; day out to make ends meet, he will try only those products which can make his economics improve.</p><p>The challenge in product designing was always about whether we are solving the right problem for the truckers which helps improve their business. Are we addressing the trust factor? Is our service reliable, that works 24*7? Can my customer reach out to my team even at 3.00 am in the morning? And finally, is my product in their language of convenience?</p><h4>How did we first find out about the need?</h4><p>The above discussion makes a solid case for the Humanization and Localization of the content. This was something that was also consistently observed by our Product team in all their User Immersion sessions. Even our ground sales team had given us input that a decent chunk of users was having a tough time using the app in English</p><p>We also found some users who had learnt the buttons and sections by colour and location on the screen.</p><ul><li>This was still a hacky solution for categories which are transactional in nature (For example — Features like recharge that have fixed steps and can be memorized.)</li><li>In an exploratory category like a Marketplace, this method was falling flat and thus adoption was suffering.</li></ul><p>All this was further supported by a few data points:</p><ul><li>Digitally acquired customers from vernacular ads had a higher drop-off rate after installation because while the ad was in their language, the app wasn’t.</li><li>Outbound User Telecalling activities showed that the low adoption of the users was primarily because of the language barrier.</li></ul><h4>How did we validate the requirement?</h4><p>While the inputs were coming from all directions, it was important for our product team to validate these requirements at scale and then lay down the path ahead.</p><p>The first part was verifying if this was the user’s conscious need. Were they already phrasing their problem statement as a need for this feature? Or was this a latent need that would solve the issues of the user?</p><p>Based on extensive user research, the team was able to identify that this was a clear need for ~40–50% of the users. However, they were not able to put this exact solution requirement into words. Thus, we needed to revalidate the same with some sample designs!</p><p>The team then identified the top primary languages for ~95% of our user base. These came out to be Hindi, Tamil, Telugu, and Kannada and a few were comfortable in English. We built sample screens for these users and did extensive user immersion with over 50 users across geographies in the North, South, East and West.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/0*oSqxXgCuglFRi1lv" /><figcaption>Multi-lingual sample screens that were piloted</figcaption></figure><p>When we piloted this in the market, we received positive feedback from the users. Truckers were elated to finally be able to use a product that solved THEIR problems in THEIR language, all the while being easy to use and understand. The users also liked the fact that the copy style was more conversational and personal and felt less like a machine that was communicating with them!</p><p>One prime example of the power of localization was seen during the following meeting with a fleet operator:</p><p>We visited a truck owner, whose daughter helped him out with the business. We attempted an experiment with this duo. We showed the trucker the BlackBuck app in English and he was quick to respond — <em>“I can’t read English. Please explain it to my daughter</em>”. We then showed a vernacular-translated sample screen to the daughter. As soon as the trucker saw the app screen in vernacular, he became interested in the app. He immediately took away the phone from his daughter and started using it himself. He then went on to ask questions about our service and product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m1ujrO1r6HulUm5A" /></figure><h4><strong>Rajendra Kumar who was previously dependent on the younger generation when it came to managing tech was now included in the digital realm thanks to localization.</strong></h4><h4><strong>Plan of Action…</strong></h4><p>After we had validated the needs of the users, the next step was to sketch a plan of action for the product copy to be unified in all languages and tones. It wasn’t enough to just launch our products in vernacular languages, we needed to go deeper with our product localization. We wanted our product to speak to the users the way they talk on an everyday basis — simple, informal, conversational, contextual and a mix of English with their local language. Hinglish, Kanglish, Tanglish — you name it, we created multiple combinations of copy to make it highly relatable and convenient to use.</p><p>How did we do it? It was a lengthy process that yielded the results we were looking for. Stay tuned to find out…</p><p><strong><em>Blog design by Puranjai Pratap</em></strong></p><p><strong>Part 2 coming soon!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c87bb3700bdc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blackbuck-design/why-humanization-and-localization-of-product-is-critical-in-fueling-digital-inclusion-in-bharat-c87bb3700bdc">Why humanization and localization of product is critical in fueling digital inclusion in Bharat —…</a> was originally published in <a href="https://medium.com/blackbuck-design">BlackBuck Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>