<?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 Nikita Yadav on Medium]]></title>
        <description><![CDATA[Stories by Nikita Yadav on Medium]]></description>
        <link>https://medium.com/@nikitay113?source=rss-96e6f461b096------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ov00eFLln3kWWAzq1U8lBA.jpeg</url>
            <title>Stories by Nikita Yadav on Medium</title>
            <link>https://medium.com/@nikitay113?source=rss-96e6f461b096------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:09:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikitay113/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[Untangling the Car Inspections Workflow : A Designer’s Journey into a Complex System]]></title>
            <link>https://medium.com/@nikitay113/untangling-the-car-inspections-workflow-a-designers-journey-into-a-complex-system-34760777fa89?source=rss-96e6f461b096------2</link>
            <guid isPermaLink="false">https://medium.com/p/34760777fa89</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[car-inspection]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Nikita Yadav]]></dc:creator>
            <pubDate>Sun, 07 Sep 2025 19:48:13 GMT</pubDate>
            <atom:updated>2025-09-07T19:48:58.574Z</atom:updated>
            <content:encoded><![CDATA[<h3>Untangling the Car Inspections Workflow : A Designer’s Journey into a Complex System</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DEf-51nfoU9rpnbe74jbqg.png" /></figure><p>It all begins with a simple intent: a customer wants to sell their car.<br>They open the CARS24 app, enter their details, and book an inspection. Sometimes, they don’t do it themselves — customer support steps in and books on their behalf. Either way, this small action sparks the beginning of a much larger chain.</p><p>On the surface, it seems straightforward: a car inspection is scheduled, a Car Jockey (CJ) shows up, evaluates the vehicle, and the process moves forward. But as I soon discovered while shadowing CJs and their managers, what looks simple to the customer is in fact a highly interconnected system where multiple roles, tools, and hidden frictions collide.</p><h4>The First Hand-off: Leads Enter the LMS</h4><p>Once created, every customer request turns into a <strong>lead</strong>. These leads flow into the <strong>Lead Management System (LMS)</strong> — the internal tool that decides who will inspect which car, where, and when.</p><p>Each city is divided into zones. Picture Delhi split into North, South, East, and West. Each zone is managed by a Car Jockey Manager (CJM), who looks after 20–25 CJs. The LMS is supposed to act like a matchmaker, aligning leads with CJs based on their zones.</p><p>One hour before an inspection, LMS automatically assigns a lead to an available CJ. It’s meant to be smooth. But reality often looks different.</p><h4>Where Things Break Down</h4><p>Through my research, I found the cracks in the system:</p><ul><li><strong>Too many leads, too few CJs.</strong> Extra leads end up hanging in limbo.</li><li><strong>Wrong locations.</strong> Leads booked by customer support often carry errors — imagine a North-zone CJ suddenly being assigned a South Delhi inspection.</li><li><strong>Last-minute reschedules.</strong> Even after being assigned, in about 75% of cases customers ask to reschedule or delay when the CJ calls to confirm.</li></ul><p>This is where two critical roles emerge:</p><ul><li><strong>Tele-callers</strong> double-check with customers, fix wrong addresses, and reschedule bookings. Interestingly, they never interact with CJs, only with customers.</li><li><strong>CJMs</strong> step in when auto-assignment fails. And here lies one of the biggest workarounds: WhatsApp.</li></ul><h4>WhatsApp: The Unofficial Control Room</h4><p>Every zone has its own WhatsApp group, run by the CJM. When LMS struggles, CJMs copy-paste appointment details into the group. Idle CJs can then “claim” leads directly from there.</p><p>Sometimes, CJMs even push next-day leads forward, knowing customers are often happy to get inspections earlier. This improvisation keeps the system moving, but it also highlights a gap: the official tool is not enough, and a messaging app has become the real backbone of operations.</p><h4>The Human Experience Behind the Workflow</h4><p>Walking in the shoes of a CJ was eye-opening. I found myself waiting for appointments that got rescheduled at the last minute. I felt the frustration of being idle, refreshing WhatsApp to see if new leads appeared. I watched CJMs juggling between LMS dashboards and group chats, their role reduced to manual coordination.</p><p>The system had no real-time view of where CJs were actually located. CJMs were stuck firefighting. Tele-callers were endlessly correcting data. And the CJs themselves — who are on payroll and expected to be consistently productive — were often left underutilized.</p><p>This wasn’t just a process problem. It was a <strong>human problem</strong>, with inefficiency spilling into frustration, redundancy, and missed opportunities.</p><h4>Where I Stepped In</h4><p>As a designer, I realised my role wasn’t just to document this workflow — it was to empathise deeply with each of these actors, uncover the hidden cracks, and then imagine how the system could truly serve them.</p><p>The inspection workflow isn’t just about leads and assignments. It’s about trust: the customer’s trust in CARS24, the CJ’s trust in their tools, and the CJM’s trust that the system won’t collapse without WhatsApp.</p><p>By dissecting this ecosystem, I uncovered not just how the system works, but how it <strong>feels</strong> to live inside it. And that empathy became the foundation for what came next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FbsrgfnpEoF-SineCLuVmQ.png" /></figure><p>Because once I understood the nuances, I stepped up to reimagine a system that optimises assignments, reduces idle time, and empowers every role involved.</p><p>How did I do it? That’s the story I’ll share in the next part.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34760777fa89" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>