Would knowing exactly where every other driver in your rideshare fleet is at this exact second actually make any of them better at their jobs?
I keep coming back to that question. Mostly because I am, embarrassingly, the kind of person who opens a rideshare app at midnight and just stares at the little cars circling the block near my apartment. Not to book anything. Just to look. (I know. It is borderline creepy and I am working on it.)
That habit is the reason I have opinions about driver-to-driver visibility, and the reason I am suspicious of my own opinions at the same time.
What does coordination actually look like at street level?
The pitch for letting drivers see each other is easy to make on a whiteboard. If two drivers can see each other, they can avoid stacking up at the same corner. A flooded underpass becomes something you warn the next driver about instead of discovering yourself. They can call dibs on the next pickup at a crowded venue without dispatch having to play traffic cop.
That sounds clean. Real life is rarely clean.
I have a friend who used to drive me home from the airport on weeknights, back when she was doing it full time. Honest, nervous in a way I recognized, kept a clipboard in the glove box (a clipboard, which I found charming) with notes about which terminals had the best cell reception. She is the unnamed voice in my head every time this topic comes up. Her take, paraphrased because I would never put words in her mouth on the record, was that seeing the other cars would have made her drive worse, not better. She would have spent the whole shift scanning the map instead of watching the road. She said the only thing she actually wanted to see was a heat-blob showing where pickups were dense, not pinpoints of every other driver.
Which, fair. There is a real difference between knowing the neighborhood is busy and knowing that Marcus in the silver Camry is exactly two blocks east of you.
If they can see each other, what do they do with it?
Try the if-then ladder for a second. If a driver sees another car circling the same hotel, do they peel off to a different zone, or do they double down because clearly that hotel is hot? If they peel off, great, the system spreads load. If they double down, you have just built a thunderdome.
If you add a softer signal (something like a colored haze instead of car icons), do drivers actually trust it? If they trust it, do they behave better? If they do not trust it, you have built a feature nobody uses, which is somehow worse than a feature people misuse, because at least the misused one taught you something. This piece on what location apps actually expose to other users is a decent place to start thinking about where that line sits, because the same tradeoffs apply whether you are sharing with a friend or with a fleet.
Territory, competition, and the part nobody puts in the marketing deck
A concession first, then the actual point. Drivers are not enemies. Most of the rideshare drivers I have ever talked to are decent, tired people trying to clear a number by the end of their shift. The competition framing gets oversold by people who have never sat in a stationary Honda Civic at 2am waiting for an airport queue to thin.
And yet.
The minute you let drivers see exactly where the other drivers are, you change the math of every decision they make. Territory becomes a thing. Some drivers will absolutely start parking themselves between competitors and the next likely pickup. Others will retreat from areas that look “claimed” even if there are plenty of riders. The platform did not create that tension. The platform exposed it.
My driver friend made one more point I keep thinking about. She said the worst nights were the ones where she thought she knew where everyone else was, even when she did not. The mental model she was building from scattered evidence (a car she saw twice, a guess about where the bar crowd was going) was already affecting her choices. Giving her a real map, she said, might have just made the bad guesses feel more official.
That is the trap, I think. More information is not the same as better decisions. (This is the thing I am bad at remembering, even though I literally study it. The little-cars-near-my-apartment habit is exhibit A.)
The privacy question that gets skipped
Most fleet conversations treat driver privacy like an HR formality. It is not.
If your drivers can see each other, then by definition each driver is being seen by everyone else on the platform, all shift, every shift. That is a different relationship than being seen by a dispatcher in a back office. A dispatcher is one set of eyes with a job description. The other drivers are dozens of strangers with their own incentives, their own grudges, and in some cases, their own apps recording the screen.
If a driver tells dispatch she does not feel safe in a certain neighborhood, that is a private conversation. If she just stops showing up on a shared driver map in that neighborhood, that is public information. Anyone watching can infer her route, her habits, the times she logs off. That is not paranoid. That is just what live data does when you publish it.
And if a driver wants to take a long break in a parking lot to eat a sandwich, do they get to do that without every other driver on shift seeing the dot stop moving and forming opinions?
And then there is the surge gaming problem, which deserves its own paragraph because it is the thing that should genuinely worry any operator considering this feature.
If drivers can see each other, they can also see when a region is thinly covered. And if they can see thin coverage, they can collectively decide to vacate it. There have been informal versions of this for years (group chats, Discord servers, parking lot meet-ups before football games). Building it into the official app is just removing the friction. Friction is sometimes the only thing keeping a system honest.
Picture the scenario. A concert lets out. Twenty drivers are within range. They can all see each other. One of them suggests, in some side channel, that everyone hold position for five minutes to push surge pricing higher. If even half of them do it, the riders pay more, the drivers earn more on the next ride, and the platform looks like it has a supply problem when it actually has a coordination problem. The map made that easier, not harder.
You can mitigate this. You can fuzz locations, you can show only zones instead of cars, you can rate-limit the visibility to specific events. All of those work, sort of. None of them work perfectly. The fundamental tension stays put.
What would I actually do?
If I were running a rideshare ops team tomorrow morning, here is the if-then I would use.
If the goal is reducing duplicate pickups at venues, then show density, not identities. A heatmap is enough. Drivers do not need to see Marcus. They need to see “this corner is crowded, try the next block.”
For safety coordination during weather events or incidents, enable temporary, opt-in visibility for the duration of the event, and turn it off automatically when it ends. Privacy defaults matter more than privacy settings. People do not change settings.
If the goal is letting drivers help each other (a tire change, a battery jump, a heads-up about a sketchy pickup), then build a request-and-respond system, not a live map. The other drivers should only see who needs help, not where everyone is at all times.
And if the goal is “we want drivers to feel like a team,” that is a culture problem and a map will not fix it. I say this with affection toward the operators who keep trying.
I am still going to peek at the cars near my apartment tonight, probably. The instinct to look is hard to break.
But would I want my own driver to be doing the same thing while she is supposed to be watching the road?