<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pranjal Sutradhar on Medium]]></title>
        <description><![CDATA[Stories by Pranjal Sutradhar on Medium]]></description>
        <link>https://medium.com/@pranjal3d?source=rss-9f1304536408------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*E8p3rykN2V-82fFrGQoj_Q.jpeg</url>
            <title>Stories by Pranjal Sutradhar on Medium</title>
            <link>https://medium.com/@pranjal3d?source=rss-9f1304536408------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:46:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pranjal3d/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Resonating with your product managers: a designer’s guide]]></title>
            <link>https://uxdesign.cc/resonating-with-your-product-managers-a-designers-guide-94f171ea5fee?source=rss-9f1304536408------2</link>
            <guid isPermaLink="false">https://medium.com/p/94f171ea5fee</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Pranjal Sutradhar]]></dc:creator>
            <pubDate>Tue, 03 Mar 2020 13:15:47 GMT</pubDate>
            <atom:updated>2020-03-09T05:53:24.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>3 ways to work hand-in-hand with your PM.</h4><figure><img alt="4 light weight airplanes flying at right angle with all four planes aligned in a straight line horizontally." src="https://cdn-images-1.medium.com/max/1024/1*h8nElYd2_ePsN7HlSuL8ow.png" /></figure><blockquote>An experience shapes into its true form when the Product Manager and the designer resonates in the same frequency.</blockquote><p>The relationship between a product manager and a designer is quite critical, as the synergy play an important role in shaping any product we see in the market. The primary duty of both professionals is to create meaningful experiences for their users, and both are equally responsible for ideating solutions and contributing to the larger piece of the pie.</p><p>In most places, Product Managers positions in the frontline of any project. While engineers are majorly responsible for the technical functioning of the product, PM &amp; designers are generally ‘together responsible’ for the overall experience of the product.</p><p>It is very important for both of them to understand where to draw the line, to argue clearly and positively, and not let any clouds of ego make unfortunate decisions. Point is, the working relationship between these two beings impacts any product immensely.</p><blockquote>The entire “field” of user experience emerged for one reason — to accommodate, and overcome, poor (or non-existent) product management practices.</blockquote><blockquote>— <a href="http://www.peterme.com/">Peter Merholz</a> in “<a href="http://www.peterme.com/2014/12/01/there-is-no-such-thing-as-ux-design/">There is no such thing as UX design</a>”</blockquote><p>Having the correct mix of emotions and working in resonance throughout a project is critical as both of them need each other to put up the best work. Working with your Product Manager with ever-lasting positive energy might be hard, but these simple rules I learned along the way may help you sync with your Product manager better and build a better product. For Everyone!</p><h3>1. Using the Power of “Why”</h3><p>I personally believe that asking a lot of “Whys” during the initial stages of your project helps not only the designers but also the other contributors to the project. Diving deep into the problem and starting off without a solution is what designers do best. While your Product manager and other stakeholders may have many solutions in mind, but unearthing the problem completely from the beginning will direct everyone towards thinking in terms of users, towards knitting stories that solve their problems.</p><figure><img alt="Here goes a group of people opening up there arms in a imaginary dramatic scene of asking Why to a greater power in the sky" src="https://cdn-images-1.medium.com/max/1024/1*hARz-m-MNzKs--BlUS64KA.png" /><figcaption>People using Whys for a higher reason. Credits to <a href="http://unsplash.com/">Unsplash</a></figcaption></figure><p>Unveiling the <em>Whys</em> throughout your process will empower everyone to learn deeply about their users.</p><h4>Involving everyone will help everyone</h4><p>Brainstorming sessions across product, engineering, and design team at the start of a project always helps in defining a proper roadmap, in increasing efficiency and reducing contradictions along the way. I believe, the most important thing is to brainstorm the <strong>problem:</strong> the build-up, the causes, and the effects.</p><p>Understanding the <em>Why</em> of the problem helps everyone involved to lie on the same page while setting a common ground of goals for the project. But in many cases, the problem setting part is handled by the product manager, creating a chain process of product development.</p><blockquote>“Having an inclusive process with all stakeholders from the initial phase benefits because — whether we like it or not, everyone outside your design team is making some design decisions”</blockquote><blockquote>— <a href="https://library.gv.com/everyone-is-a-designer-get-over-it-501cc9a2f434">Everyone is a designer. Get over it.</a> by <a href="https://medium.com/u/c6d7332a2978">Daniel Burka</a></blockquote><p>The point is, you should always ask <em>Why</em> whenever you get a chance, even if the path is super clear. Your Product Manager may have a strong problem statement and may even provide proper wireframes, but don’t forget to ask <em>Why</em>. Start with —</p><ul><li>Why does the problem exist?</li><li>Why is this a problem for the user? Wait... Is it?</li><li>Why do businesses care about this problem?</li><li>Why is this problem important than the other problems(projects)?</li><li>Why are we doing this?</li></ul><figure><img alt="A section of a marker board with Red &amp; yellow Sticky notes/Post-aids reflecting a brainstorming session" src="https://cdn-images-1.medium.com/max/1024/1*wTbILcTD25kcVMQPW1LawA.png" /></figure><p>This general <em>why</em> round will give enough clarity to all stakeholders involved, about the <em>purpose</em> of the project.</p><p>Having a common purpose helps all teams to align on the same path. The string of <em>whys</em> should stretch throughout a designer’s work cycle and must become an integral part of every design decision you take, as it will answer the reasoning behind every pixel movement of your design. These reasons will finally help in rationalizing the designs with other stakeholders.</p><h4>Whys will make you dig into data</h4><p>Product managers know their users very well — with their market expertise and numbers. They float on data and make or break things depending on it. This alone is a big reason for designers running after their PMs. We need data and your PM can help in all ways. A valuable PM will always be excited to know more about their users. They will become your best buddy on conducting User Research exercises and will help you in all possible ways: to learn more about the users, together.</p><figure><img alt="People watching a stick movie through a hole that make it seems like they are digging for something deep" src="https://cdn-images-1.medium.com/max/1024/1*8a8NyT7Hq2spzdZmlQQA_Q.png" /><figcaption>People putting effort to dig into something. Credits to <a href="http://unslash.com/">Unsplash</a></figcaption></figure><p>Dig into the quantitative data that your PM will have at his disposal, or plan to collect with him. Ask for research and more data, push for conducting short user interviews or simply doing A/B test on confused pieces.</p><p>The answers and the data you pulled out with the <em>Whys</em> will generate one true purpose and will help you resonate with your PM more. Keep challenging each other to find the <em>Whys</em>. Seek for more knowledge about the user, their behaviors, their goals, their needs (your list should never end); and the clarity of the story will be the fuel for the team to think together.</p><blockquote><strong>Remember, good questions empower everyone involved.</strong></blockquote><p>Want to explore What to ask &amp; When? Read this — <a href="https://www.toptal.com/designers/product-design/design-thinking-great-questions">Great Questions Lead to Great Designs</a></p><h3>2. Strive for a Balance: Business vs Users</h3><p>Today, businesses value design to scale up and touch the experience of their customers, to build a connection with them and finally knit a beautiful story around the product they are selling.</p><p>They understand that ‘experience is what customer demands.’ To achieve it, companies push for collaboration across their marketing, business, design and development teams to contribute towards creating a user-centered environment. These occasionally lead to overlapping objectives and responsibilities, but the right amount of business thinking on your design process and the right amount of design thinking on the business vertical will take us a long way.</p><blockquote>Setting up the right responsibilities in your organization reduces costs and risks throughout the entire product development process. — <a href="http://www.cooper.com/journal/2001/10/putting_people_together_to_cre">Cooper.com</a></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FhTRtnHe0fWfYs%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FhTRtnHe0fWfYs%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FhTRtnHe0fWfYs%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/54b275793946ab514c57e3389fed6aeb/href">https://medium.com/media/54b275793946ab514c57e3389fed6aeb/href</a></iframe><h4>Being responsible for shared responsibilities</h4><p>Sometimes, this perplexity in the objectives of various teams creates a situation where people are confused about who is in charge of what. For instance, ‘Instant full-screen popup’ to capture email IDs sucks. But more often, email capturing &amp; unwanted friction goes a long way to show positive results and retention.</p><p>While creating it, the Marketing team feels the responsibility of deciding the nature &amp; functioning of their lead generation pop-up blocker. But any form of it will affect the experience of the user. So, the designer feels the responsibility of deciding the final nature &amp; behavior of the blocker. This kind of crossroads creates situations where various teams will want to have a larger say in the decision.</p><figure><img alt="A group of 5 divers cheering in the ocean for something they have accomplished by working together" src="https://cdn-images-1.medium.com/max/1024/1*jkNIJmAitHqrGxJHYAXCxQ.png" /><figcaption>Sharing responsibilities and success. Credits to <a href="http://unsplash.com/">Unslpash</a></figcaption></figure><p>Situations like this demand a product designer who weighs every possible factor, mine out the underlying logic, its long term objectives, its possible effects &amp; impacts and listen carefully to the business needs. As a Product Designer, you know that a part of you is chasing numbers for the business. Which is not wrong, but quite beneficial in helping you find the tipping point for your UX. It helps you create a balance, using the constraint in a way that it doesn’t affect the overall experience but helps fulfill the business need.</p><p>Reaching here is possible when your thoughts align with your Product Manager, who will be the central guy on all these crossroads.</p><h4>Listen, Process &amp; Optimize</h4><p>Debate with logical arguments for every decision your PM takes and do not accept a decision without knowing the true intentions behind it. (Business intentions could be cruel sometimes!). Have a healthy argument and try to understand the thought process behind your PM’s rationale, the factors that led him to that decision. Your Product Manager cares about the business and to create a sustainable business, the user stories should have a shared vision with the business. Listen and value your product manager’s input. It will help you immensely.</p><p>During all these, never compromise on the experience, but create a balance by using the inputs that benefit the business without wrecking up the User Experience. Your intensity of the debates and the passion to find the answer behind every tick of the product decision will eventually create an optimum experience, balancing the business’ and the user&#39;s needs.</p><h3>3. Advocacy for your users</h3><blockquote>The art of how intense design advocacy should be on various stages of your stakeholder meetings.</blockquote><p>As a product designer, we land in situations where you are the only person speaking for the user and you are the one who mostly creates a battleground for friendly discourse. No one might support you and few might not even get the value of fighting for the users. But you go on, you consider factors like cognitive load, empathy, assurance, etc. to back up a design decision or a rejection towards some proposal. You argue whenever you think a loose requirement might affect your users and always stand stiff to speak shamelessly on the behalf of your users.</p><p>But in most startups, larger decisions are driven by the business; while designers mostly get a lot of say on experimental projects. Also who gets the say and takes the final decision is also dependent on the company’s situation, aggression and future plans. A decision against a user need might be beneficial for the company at that moment, but your job is to advocate for the users. Largely, your users don’t care about the business, but be there for them and put their interests on the table. Clearly communicating &amp; rationalizing each one of the stakeholders is the key to pushing more of what users deeply need in the product, and creating a healthy user-centered environment.</p><figure><img alt="A young male wearing a cap with a graphic saying, “LOVE YOUR USERS”" src="https://cdn-images-1.medium.com/max/1024/1*9ZJc4BVWYY2wov_9cPOw9g.png" /></figure><p>Sometimes stakeholder meetings throw a situation, where you believe in your design but somehow forgot the history &amp; reasons behind it. You have no immediate reasoning to pull off that thing in the meeting. You know that this particular design will work, and you want to defend that design. You believe in that design. What do you do?</p><p>Designers lie in these situations when they skip critical steps on their process. It can be a clarity you missed to have from the PM or something your PM missed. It can be because you did not ask yourself the <em>Whys </em>while designing, or just because there wasn&#39;t much time to hover through that one use case and you skipped it. Somehow you are blank for logical reasons.</p><h4>Use the “Next Time” move</h4><p>Ask for more time shamelessly. Take up the blame but don’t agree with any solutions shot at that moment, which will result in compromising the interests of your user. It is better to ask for a little more time, to dig into the things you might have fumbled upon. No wonder, the alternates proposed by others at that moment can be great. Listen to it, value it and note. But taking that extra time for your case and validating it through your design methods before deciding anything is the essence of Design Advocacy.</p><p>Practicing it will create a better product along with a good design culture in the company.</p><h3>In the same boat towards one destination</h3><p>I always felt that product managers and designers have the most frequent lock horns as both their roles overlap on many fronts, but not to forget, both of them contributes uniquely in shaping the product, and both of them are grateful to each other’s contribution. So can’t we draw a line somewhere?</p><p>While companies with clearly defined roles &amp; responsibilities of Product Managers &amp; designers state that it reduces unnecessary conflicts &amp; unfortunate decisions that create delays and broken ownership, but I think a product get its optimum form when both professionals oscillate together.</p><blockquote>Apple is one of the great example of a synchonized workspace. Apple understands the importance of the end-to-end customer experience. Marketing, product, retail, packaging and services all work together to form a cohesive customer experience<br> — <a href="https://blog.agrawals.org/2011/06/01/the-experience-is-the-product/">As experienced by Rakesh Agarwal, Sr. Director of Products at Amazon</a></blockquote><figure><img alt="A section of a Pavement with text “Passion led us here” displayed on it. Seen are two person looking at that text" src="https://cdn-images-1.medium.com/max/1024/1*SyjsQNdDPIZ2QmWp6ZQhLw.png" /></figure><p>The best thing is, that oscillation creates a product that resonates with both the product manager and the designer. Ultimately, we are aiming towards a single purpose of building a better product for the people and more profit for the business. The right fit will win the race.</p><blockquote>“It is in understanding the different job roles, their intersections, values and accountabilities that you will end up with a great product.”</blockquote><blockquote>— <a href="https://medium.com/u/8d842176b4d5">Sarah Deane</a> in <a href="https://www.huffingtonpost.com/sarah-deane/4-signs-your-ux-relations_b_7324510.html">4 signs of UX relations</a></blockquote><h4>Here go a few helpful reads for Designers &amp; PMs —</h4><ol><li><a href="https://medium.com/flowcap/design-basics-for-product-managers-e561427679b5">Design Basics for Product Managers</a> — <a href="https://medium.com/u/53ee7f6cb108">Romy M</a></li><li><a href="https://medium.com/the-year-of-the-looking-glass/what-to-expect-from-pms-e9750ec09bbf">What to expect from PMs</a> — <a href="https://medium.com/u/b8a4e5ae7490">Julie Zhuo</a> in <a href="http://www.juliezhuo.com/design/mailinglist.html"><em>The Looking Glass</em></a></li><li><a href="https://medium.com/@jefago/pm-101-working-with-product-designers-b8ca02e1b87d">PM101: Working with product designers</a> — <a href="https://medium.com/u/7dd7b5b8624f">Jens-Fabian Goetzmann</a></li><li><a href="https://uxdesign.cc/what-do-designers-really-want-from-product-managers-9c0e14993a8">What do designers really want from product managers</a> — <a href="https://medium.com/u/ef6f0c0c66e8">Jess Eddy</a></li><li><a href="https://medium.theuxblog.com/about-ux-product-managers-a451172f7df">Understanding product management as UX designer</a> — <a href="https://medium.com/u/579833d9f35e">Maximilian Wambach</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94f171ea5fee" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/resonating-with-your-product-managers-a-designers-guide-94f171ea5fee">Resonating with your product managers: a designer’s guide</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing app experience of OLA Play driver-partners]]></title>
            <link>https://medium.com/@pranjal3d/enhancing-app-experience-of-ola-play-driver-partners-7432cada0c11?source=rss-9f1304536408------2</link>
            <guid isPermaLink="false">https://medium.com/p/7432cada0c11</guid>
            <category><![CDATA[olacabs]]></category>
            <dc:creator><![CDATA[Pranjal Sutradhar]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 06:40:24 GMT</pubDate>
            <atom:updated>2019-04-17T14:13:17.294Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing Companion mobile app</h4><blockquote>This project was done as a part of the partner experience team, where I played the role of a Product designer on the discovery, ideation, and creation of an mobile experience for the play drivers</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XquupXcCwydVLekMuVklfw.png" /></figure><h3>Understanding the ecosystem</h3><p>Ola cabs is India’s largest ride-hailing company with Operations in 130 cities. <strong>Ola Play </strong>is the connected car platform with in-cab entertainment for consumers and added benefits for Driver-partners. Ola Play<strong> </strong>was launched in Nov 2016.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b1w9GxWzOFkl3eeY0uOIZA.png" /></figure><h4>Ola Play Driver-Partners</h4><p>Ola Play Driver-partners, who attached the Play Tablets (Driver &amp; Consumer) on their car accounts up to 18% of total driver-partners as of March 2018. They experience the same Ola Partner app on the tablet with value-added Play experience and entertainment. Driver Experience Console (DXC) is the tablet attached to all play cars which act as the only device for the drivers to use the Ola Partner app.</p><p>Play Drivers upgrade to the service for —</p><ul><li>Higher earnings per booking for Ola-Play rides (Category upgrade)</li><li>Higher preference during Ola-Prime allocation (Targetting the Prime consumers for migration into Play)</li><li>High Consumer preference of Ola-Play cars for Outstation &amp; Rentals (Higher earnings than city rides).</li></ul><h3>Problem</h3><p>Supply Operations team reported 18 driver attrition per quarter citing — “Immobility of the DXC (Driver tablet) and having to sit idly in the car as the biggest reasons for them attriting.”</p><ul><li>For Ola Play Drivers, <strong>booking re-allocated due to no response from the driver was 28%</strong> more than the non-play drivers.</li><li>Immobility of Ola Partner app decreases <strong>Driver Engagement</strong> with the platform</li></ul><h4>User problem</h4><p>Most outstations and rental bookings are received during the morning and late-night hours. Drivers are allocated a ride 45 minutes before on Outstation &amp; Rentals bookings. While non-play drivers can go On-Duty from anywhere and use “Only Rental &amp; Outstation booking” feature; but for play drivers, all communication happens on the tablet console attached to their car. Problem hypothesized are —</p><ul><li>Sticking to their vehicle all the time to get notified about a new booking (whenever the user is on duty)</li><li>Ergonomic problems in accessing other sections of the app (Accounts, Incentives being the major use case)</li><li>No channel to interact &amp; engage with the app when away from the car</li></ul><h3>The Approach</h3><p>One of the main goal we are trying to achieve is the increase in booking response from play partners. We explored way to find other channels to send bookings to the user’s mobile phone, at the same moment he receives it on the DXC. We wanted to test a fallback channel to send bookings on his phone without requiring to install Ola Partner app.</p><h3>IVR call as a channel</h3><p>Interactive Voice Response (IVR) call was thought out to be a fallback channel to send Rental &amp; Outstation bookings when the user is away from the car. We wanted to check the feasibility of the process.</p><h4>Research</h4><p>With the help of the Pune city operations team, we tested <strong>IVR Penetration and booking acknowledgment time</strong>.</p><p><strong>8 users</strong> (Active Rental &amp; Outstation Ola Play partners) were given an option to use IVR call as a booking channel for a week — whenever he wants to receive Outstation and Rental bookings on his phone. No training was provided on IVR call experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8v-WclsFnYRkWaH6HtYC_Q.png" /></figure><h4>Result</h4><ul><li>Penetration of IVR calls (percentage of IVRs where system successfully records a partner response) is <strong>below 60%</strong>.</li><li>Total booking acknowledgment time through IVR calls is in the range of <strong>50 secs</strong>. Both Outstation and Rentals (unicast) bookings are automatically reallocated within 45 secs in the absence of a partner response. So efficiency of IVR as a primary booking management tool in cases of outstation and rentals is questionable at best.</li></ul><h3>Mobile Approach</h3><p>Introducing a clone mobile app to Play partners will be the ideal scenario for a play driver where the user can switch between devices. Since, this approach requires an enormous engineering effort &amp; change, we wanted to conduct a quantitative research on the same to validate our hypothesized user problems.</p><h4>Deep diving the requirement</h4><p>A research was conducted with 90 partners across 3 cities (Pune, Delhi and Bangalore) with the help of respective city operations team. We circulated a set of questions focusing on—</p><ul><li>Issues faced on receiving outstation and rental bookings</li><li>Preference of Outstation bookings</li><li>Understand difficulties on DXC as a booking device</li><li>Preferred mode of incoming booking</li><li>How will it effect your Duty hours, if we use mobile as a booking device?</li></ul><h4>User Insights</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V7aMRio3Neen5SGMJeIJQw.png" /></figure><ul><li>For Outstation and Rentals,<br><em>“I need to wait inside the car to receive booking”</em> — <strong>13% (largest bucket)</strong><br><em>“I miss bookings because i am outside the car”</em>— <strong>6% (third largest bucket behind “low business”)</strong></li><li>Further 2% said they miss their food to receive bookings</li><li>When asked if they would drive for longer per day given the option to step out of the car while waiting for booking, 60% responded in positive. Further 8% were undecided.</li></ul><h4>User quotes</h4><ul><li><em>“Not comfortable to sit in car long time to wait for bookings /instead of this mobile” (majorly in airports)</em></li><li><em>“Device is better we can take mobile and go out”</em></li><li><em>“Not getting much bookings, Need to be in car always if on duty”</em></li><li><em>“No possibility to check bills and rides at home”</em></li></ul><h3>Designing the Companion app (Mobile mode)</h3><h4>Objectives</h4><ul><li>Ability to accept and reject bookings when outside a Prime Play car.</li><li>Ability to view payments, incentives and performance info when outside a Prime Play car</li><li>Ability to view duty status (off-duty, on-duty, go-to) on the companion device</li></ul><h4>Constraints</h4><ul><li>Current architect doesn’t support multiple logins, <br><strong><em>Need to mirror the tablet app on his phone — OTP auth not possible</em></strong></li><li>Real-time sync between the mobile and DXC was was not full proof and we were experiencing ~3% error cases.<br><strong><em>Need to make real-time data representation into user triggered one</em></strong></li></ul><blockquote>With clear design objectives and noted constraints, I made the experience of the play drivers on using mobile as a secondary medium for business.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G0X7dENUtzRTxl0XSdaO7A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BFlqthLUq7sIpaC3Y7IRaA.png" /></figure><h4>Login to Mobile app (Companion app)</h4><p>We explored ways of pairing the mobile app with the Driver’s Tablet (DXC) — NFC, Wifi, bluetooth and QR code pairing. Since login is a one time process (with an expiry of 6 months), QR login made sense</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ePYhlb16tBXKI6eDwi3Gw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5KTcp93KXi6YbV18VrNcA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Faw-7WL-K4a82PHPqmDI3w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZZMqi-eUNNtRyNqC8jGzkg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytcxMaHEaXf7rxwdXwbWmw.png" /></figure><h3>Team</h3><p><strong>Pranjal Sutradhar</strong> (Product Designer)<br><strong>Aravind Appakutan</strong> (Director of Design)<br><strong>Sanchit Gupta</strong> (Product Manager)<br><strong>Nipun Joshi and team</strong> (Driver Engineering Team — Android )</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ePj3LkPSMlDpUQld8Xy5fA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7432cada0c11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[App Diagnostics: How Ola Cabs reduced 35% driver support calls]]></title>
            <link>https://medium.com/@pranjal3d/https-medium-com-pranjal3d-ad-cf01a8b06b52?source=rss-9f1304536408------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf01a8b06b52</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[olacabs]]></category>
            <category><![CDATA[customer-support]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ola]]></category>
            <dc:creator><![CDATA[Pranjal Sutradhar]]></dc:creator>
            <pubDate>Mon, 15 Apr 2019 12:46:23 GMT</pubDate>
            <atom:updated>2019-04-18T11:17:59.654Z</atom:updated>
            <content:encoded><![CDATA[<h3>App Diagnostics: How Ola Cabs reduced 35% Driver support calls</h3><h4>Troubleshooting tool done right!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*krudWbnOcgzZ8Wms0-9Ozw.jpeg" /><figcaption>Most probable environment for the Auto drivers using the App Diagnostic feature</figcaption></figure><blockquote>This project was a part of the Partner Experience team, where I played the role of a Product Designer on creating a troubleshooting experience for our driver partners on solving real-time Internet/GPS/Navigation issues.</blockquote><h3>About Ola Cabs</h3><p>Ola Cabs is India’s largest ride-hailing company and the 5th largest in the world with operations in 4 countries. Ola integrates city transportation for customers and driver-partners onto a mobile technology platform ensuring convenient, transparent, and quick service fulfillment. Ola is focused on leveraging the best of technology and building innovative solutions ground-up, that are relevant at the global scale for a seamless cab experience with an equal focus on riders and the drivers.</p><h3>The Problem</h3><p>More than 1 million driver-partners are working with Ola across India, UK, Australia, and New Zealand. Driver Partners face multiple issues using the app on their device like — ‘No Internet connection scenarios’ across the app and ‘map navigation failure’ impacting their business and experience.</p><p><strong><em>In these scenarios, driver-partners today are primed to call Partner Support, explain their issue over the phone and get basic resolution steps (reboot the device, change your location and device setting checks) where the average handling time is 8 min.</em></strong></p><h4>Business Problem</h4><p>Internet &amp; Navigation issue related calls generally have solutions which are not dependent on Ola’s ecosystem and can be solved without the intervention of Driver support calls. With an increase in the number of drivers partners in the platform, <strong>weekly call volumes regarding Internet &amp; Navigation issues counted up to more than 28,000 calls</strong> in the first week of November 2017, thus incurring huge call costs on non-platform dependent issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6CYlMMYCx2l_KWUhWrenA.png" /></figure><h3>The Approach</h3><p>Firstly, I wanted to understand the current flow — from the realization of app issues by the user to resorting on calling partner support. I wanted to explore the conversation among the user &amp; the support agent to find the causes and how the partner support detect the issues and give suggestions.</p><h4><strong>Research</strong></h4><p>For that, I visited the partner office and had discussions with 3 support agents who have handled Internet &amp; Navigation issues. Also, talked to 1 walk-in support agent (Partner office agent) who have experienced auto drivers visiting office because of some faulty device settings.</p><p><em>I also listened to support calls related to Internet &amp; Navigation issues to get user insights on the cause-effect of various scenarios.</em></p><p><strong>Research Themes in mind —</strong></p><ul><li>What does the user think causes Internet &amp; Navigation issues?</li><li>What actually causes the issues?</li><li>How critical is the user perception of the issues?</li><li>Why do users resort to calling support for this issues?</li><li>Understand Current flow between the support agent and the user on solving the issues.</li><li>Extract the user needs and motivations on the journey.</li><li>Understand their expectations on the resolution part if these issues are bound to occur.</li></ul><h4>User Insights</h4><p>After speaking to several drivers &amp; support agents we could identify the problems in the existing system. Some of them are —</p><ul><li>Users feel lost in the system when no incoming trips are received due to these issues.</li><li>Troublesome task of calling partner care hampers user experience</li><li>Creates tension when navigation fails during a trip.</li><li>Loss in duty hours creates user frustration and doubts his/her performance</li><li>Loses trust in the platform</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GG-B2YZLp6q5IR8meeXjPA.jpeg" /></figure><h4>Cause and Effect</h4><p>We wanted to identify the causes that create app issues, how it is effecting the user and the business, and what are their needs . We proceeded to brainstorm the <strong>cause &amp; effect diagram</strong> with the <strong>product manager &amp; design manager.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lJUKyhLcMRQUBvaAUc-VoA.png" /></figure><blockquote>Solving the detected issues &amp; Reduction of Partner support calls were the primary success metrics for the project, while we also aimed at creating a user-initiated diagnosis behavior before calling the partner care.</blockquote><h4>Understanding Flows</h4><p>After the initial research, a pattern was observed on how support agent gets to know about the issues and the resolution steps followed by them. After analyzing the cause, we learned that <strong><em>the solutions for Internet &amp; Navigation issues are mostly on user’s control and the agent helps him fix the issues by checking device settings or suggesting tips if the issue could not be fixed.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dbm4214UaUugB5iFDW8Q0w.png" /><figcaption><strong>Current journey of issue detection to resolution</strong></figcaption></figure><ul><li><em>Issue detection</em><strong>:</strong> Currently, users convey on the call as “Internet problem” or “Navigation problem”, which is a user understanding of the issue from past events. <br><strong><em>Can the app detect the issues and surface on the app?</em></strong></li><li><em>Cause detection</em>: Currently, support agent runs through a checklist of the expected device settings like “Go to settings and check flight mode”, where user cross check for any faulty settings. This is a long process on call.<br><strong><em>Can the app run a check and surface the unexpected device settings?</em></strong></li><li><em>Resolutions</em>: Currently, the support agent walks the user through to fix any fault on settings. <br><strong><em>Can we lead the user from app to fix the unexpected device settings?</em></strong></li><li><em>Suggestion</em>: After the cross-check of device settings, support agent asks the user to reboot the device and also gives few tips since many unknown factors might cause the issues.<br><strong><em>Can we give the user a sense of “All settings are fine”, and communicate that few problems are out of scope for Ola to solve?</em></strong></li></ul><h3>Design</h3><p>Finally, we came up with <strong>App Diagnostics</strong> to combat the user expectations and increase efficiency on handling app issues for the above mentioned use cases.</p><p>The insights and design directions from the analysis helped me frame <strong>the flow of the App Diagnostics</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U5aj5Tbmqps_CeM4rOJi-w.png" /></figure><h4>Auto-trigger of Internet &amp; Navigation issue</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mYACwSKBgx5u50bEoGQJTg.png" /></figure><h4>Efficient detection of causes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nsd5XW1jA-cX1qOl87ALHw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2SwY9lKu-YXPTmbDa25o2g.png" /></figure><h3>Usability Testing</h3><p>Once the designs were ready, I teamed up with the research team and conducted Usability tests for <strong>10 users: 5 Auto drivers &amp; 5 Cab drivers</strong>.</p><h4>Research Insights</h4><ul><li>40% users accepted to have faced these problems and at times turns up calling partner support — Useful</li><li>70% (4 cab-3 auto)of the users were able to successfully complete the 2 use cases tested.</li><li>50% of the users completed each task in less than 2 min, which took 6–8 min through support calls</li><li>Half the driver queried about the initiation of the feature, whether they can start the check themselves. At that time, our feature was not made to be self-triggered, but helped us gain insight on their expectation.</li><li>Users are motivated to use the feature as it significantly decreases the time of resolving the issues, and they can get rid of the support calls queue.</li></ul><h4>Using Diagnosis Report &amp; handling edge case</h4><p>With previous experience, few drivers might still end up calling partner care for resolution. To fast forward the process, we introduced <strong>“Diagnose my app” — Self-trigger of App Diagnostics.</strong><br>User can use the feature to perform a check and get the issues and a summary which can be used by support agent for cross-checking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*APC83hM9Vs-35wXC649_vQ.png" /></figure><h4>Contextual suggestions for various issues</h4><p>It was being observed that “not receiving bookings” complain support call is also a major issue with the system, where the support agent suggest user to wait for booking or go to a crowded area. Once in a while, support agent give Demand Zone locations to the user. (Operations allows a maximum of 3 times in a month for one driver, with less than 5 bookings in a day) <br>This gave us an idea to connect partner care queries (FAQs like <em>Why no bookings</em>?) with App diagnostics and give contextual suggestions.</p><p><strong><em>This can be scaled in the future but currently, it was launched only for “Not Receiving Booking” article query on Partner Care section of the app</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_BNVGlHy-TIn2t8O6ZV6g.png" /></figure><h3>Impact</h3><p>User research proved the acceptance of the feature from the users, to which we expected a decrease in support calls, but was skeptical about resolution success of the feature. We reviewed the numbers after 3 months and saw an exciting change in metrics —</p><ul><li><strong>35% reduction in Partner Support calls related to Internet &amp; Navigation issues</strong></li><li><strong>App Diagnostics experienced 80% success whenever it was triggered for Internet Issues.</strong></li></ul><h3>My Thoughts and the Future</h3><p>The problems we faced in this projects were majorly for the unawareness of our users on the mobile platform. Most of the calls and issues are also not directly linked with the Ola Partner App. I believe app diagnostics will help Ola soft-train the drivers on understanding the ecosystem of how various factors can lead to facing app issues which are not in control of Ola. Future improvements would be —</p><ul><li>Exploring more app issues and usage pattern to include more use cases that effect user’s business</li><li>Timely app check to find any faulty settings — maybe before the user starts his/her day or was not doing business for more than a defined time period.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5s9FS8vgVNAUa-DvYOe44g.jpeg" /></figure><h3>Team</h3><p><strong>Pranjal Sutradhar </strong>(Product Designer, <em>Driver Partners)<br></em><strong>Jaisheel Nishad</strong> (Principal Designer, <em>Driver Partners</em>)<br><strong>Gunjan Sobhani </strong>(Senior User Researcher)<br><strong>Manish Jha</strong> (Senior Product Manager, <em>Driver experience</em>)<br><strong>Aravind Appakuttan</strong> (Director of Design)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf01a8b06b52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increasing timely Repair & Maintenance of OLA’s leasing drivers]]></title>
            <link>https://medium.com/pranjal-sutradhar/increasing-timely-repair-maintenance-of-olas-leasing-drivers-e35e2521fe28?source=rss-9f1304536408------2</link>
            <guid isPermaLink="false">https://medium.com/p/e35e2521fe28</guid>
            <category><![CDATA[olacabs]]></category>
            <dc:creator><![CDATA[Pranjal Sutradhar]]></dc:creator>
            <pubDate>Mon, 15 Apr 2019 12:25:34 GMT</pubDate>
            <atom:updated>2019-04-16T06:33:12.647Z</atom:updated>
            <content:encoded><![CDATA[<h3>Increasing timely Repair &amp; Maintenance: Ola Cabs’ leasing driver-partners</h3><h4>More timely maintenance, More on-road time</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-bD7q9BYQ6bIu3J8chpIeQ.jpeg" /></figure><h3>About Ola Fleet Technologies</h3><p>Ola currently has more than 10,00,000 vehicles on road, out of which around 28% of cars are leased to the interested driver-partners through Ola Fleet Technologies. They experience the Ola Partner app in the same way as the car-owned drivers, apart from two things in the ecosystem.</p><ul><li>Incentives: Leasing driver miss the opportunity to earn extra through incentives, but they get high priority during booking allocation.</li><li>Leasing perks: All accidental or timely repair and maintenance (RMT) of the vehicle are covered by Ola through authorized workshops.</li></ul><h4>How Repair &amp; Maintenance (RMT) work?</h4><p>Repair and maintenance is a very essential part of maintaining the health of the Ola owned fleet vehicles. Leasing drivers can take advantage of Ola authorized workshops for timely servicing, accidental/regular repairs or any emergency breakdown. Drivers can schedule for any of the services through the leasing section of the app. Users can also request for a tow truck and get an immediate towing facility, in case of emergency breakdowns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*vbeJOBfUlLuUNd-gJk3gvg.jpeg" /></figure><p><em>Leasing drivers-partners are totally responsible for Timely maintenance of the leased vehicles.</em></p><h4><strong>Why its important for the business?</strong></h4><p><strong>Timely maintenance</strong> ensures that Ola does not incur expensive repair costs due to oversight or neglect on the driver partner’s part. Also, with less car getting off-roaded due to penalty, there will be increase in on-road time of Ola cars. <br>In order to ensure that we allow the driver partner to schedule RMT with our authorized workshops, we created the RMT flow. For timely car servicing, drivers can schedule from the app, where he selects the date and an available slot on any of the listed workshops. Leasing drivers are trained to consider these services whenever required and are nudged through app communications for timely servicing.</p><h3>The Challenge</h3><p>For an average Ola-leased driver, maintenance service counts up to 2–3 times in a month. The user needs to schedule for the service through the app, but only <em>43% leasing drivers schedule the maintenance service before the last due date of service (adherence maintenance)</em>, where 65% use the app and others end up calling Ola support to schedule for them<em>. </em>Our challenge is to —</p><ul><li>Improve adherence maintenance for leasing drivers</li><li>Reduction of Repair &amp; Maintenence scheduling related support calls</li><li>Introduction of night-time maintenance</li></ul><h3>The Approach</h3><h4>Understanding Current ecosystem</h4><p>I explored the current app journey for the complete Repair and Maintenence process. The journey starts with in-app communication (snackbar) sent a week before the last servicing date. Users are expected to schedule and service the car before the date to avoid getting off-roaded. Another communication (pop-up) is done 48 hours before the penalty of <em>Late Service. </em>Any user failing to schedule a service before the deadline will be off-roaded and need to complete the service to get back on the platform.</p><p>The scheduling flow starts with a selection of date &amp; time-slot, then listing out the available workshop for the same. User can then select the workshop and book the service. Users are communicated 24 hours before the service time and are off-roaded 2 hours before as a buffer time to deliver the car to the workshop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7xtx2-sQcT14zWW-FqbABA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GbDRiHAoYEzRkD02Q5yIuQ.png" /></figure><h3>Research</h3><p>With the understanding of the current journey, <strong>I listened to few support calls related to scheduling</strong>. It helped me understand the problems faced at various parts of the journey. It helped me frame my questions and learn the focus for the primary research. Few user quotes were —</p><ul><li>“Help me book a Car service in the app”</li><li>“I forgot to book, now I am off-roaded”</li><li>“My regular workshop is not on the list”</li><li>“Why Ola asks for so many services?”</li></ul><h4>User interviews</h4><p>I visited the leasing office with the product manager and <strong>interviewed 8 users </strong>and also <strong>discussed with the Ola agents</strong> who help the drivers visiting the office with various issues. We interviewed around the pain points and tried understanding the user’s mental model on timely Car Service. We tried to extract the most common terms they generally use to communicate.</p><p>Questions asked were —</p><ul><li>How do you know when to plan for servicing?</li><li>Do you feel Ola asks for too many services?</li><li>Learn Car service experience before joining Ola</li><li>Do you use the app to book? If no why? If yes, where do you face the problems</li><li>What is “Repair &amp; Maintenance” (current terminology). What terms do you generally use?</li></ul><h3>Discovery</h3><p>After the research, I used the notes to understand the pain points, goals and need of the user at all stages of the journey. It helped me carve the end-to-end user journey map for the timely maintenance service.</p><p>After analysis, I synthesized all the information I have now, which can help me gain insights about the user and find possible solutions to tackle the challenges. Next follows the user insights and design thinking for the same.</p><h4>Design Directions</h4><p>Majority of our users were in the driving profession before joining Ola, and are used to a way of planning, scheduling and completing the servicing process in the offline world.</p><ul><li>Users tend to stick to a particular workshop for service and not change it unless required as it hampers their trust.</li><li>Date and time of service is always a secondary factor while booking a workshop for service.</li><li>Overnight servicing is welcomed by all the users that were interviewed.</li></ul><h3><em>Design</em></h3><p>With the analyzed insights, the team brainstormed on creating flows that connect with the mental model of the user.</p><h4>Change in flow</h4><p>The current flow asks the scheduling date first and then show the available workshops, in which the user desired workshop might not be available. Also, unavailable workshops are listed at the bottom of the list (which is generally a very long scroll for Tier 1&amp;2 cities), thus creating a resistance on going ahead on the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6AfgYhtSj6JK-fQmdLFPbw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O8DZcLX5wB2Dv_7ApWCiGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rH9H8QQUKqqEY47e4h_iIA.png" /></figure><h4>Night time Servicing</h4><p>With the user’s validation, we introduced night time service.</p><ul><li>User will not lose the duty hours and earnings which is the case when a whole day is required for service.</li><li>For business, it will increase the time that the OFT leased vehicles are on the road during peak hours.</li></ul><h3>The Impact</h3><p>After the changes in flows and communication channels, along with the introduction of night time service, it was launched in all Tier 1&amp;2 cities across India. Night time service saw an exponential increase in booking counts. After 3 months, we reviewed the impact caused by the changes. Surprisingly, things went pretty well and CTO mentioned it as an impactful project of the quarter.</p><ul><li><strong>After 3 months, ~40% of scheduled maintenance was happening during the night (with lease rental applied)</strong></li><li><strong>Adherence scheduled maintenance increased to 71% (from 43%)</strong></li></ul><h3>The Team</h3><p><strong>Pranjal Sutradhar</strong> (Product Designer)<br><strong>Jaisheel Nishad</strong> (Principal Designer)<br><strong>Rajesh M K</strong> (Product Manager, OFT)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5s9FS8vgVNAUa-DvYOe44g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35e2521fe28" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pranjal-sutradhar/increasing-timely-repair-maintenance-of-olas-leasing-drivers-e35e2521fe28">Increasing timely Repair &amp; Maintenance of OLA’s leasing drivers</a> was originally published in <a href="https://medium.com/pranjal-sutradhar">Pranjal Sutradhar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>