Ch6 01: What Happens When You Send the Service Center to the Customer?#

This is the chapter where everything clicks into place.

For five chapters, I’ve walked you through the Algorithm step by step — questioning requirements, deleting waste, simplifying what’s left, accelerating cycles, and automating last. Each step was presented on its own, with its own cases and its own logic. But the real power of the Algorithm isn’t in any single step. It’s in what happens when all five are stacked together, over and over, against the same problem.

The result isn’t a better version of the old answer. It’s a completely different answer — one that redefines the question itself. Tesla’s mobile service operation is the clearest proof of this effect I’ve ever witnessed. And it started with a question nobody in the auto industry had bothered to ask.

Step one: question. Why does car service require a service center?

Sounds trivial. It’s anything but. The entire automotive service industry rests on the assumption that cars must be hauled to a fixed location where equipment, parts, and technicians live under one roof. Dealerships pour millions into service facilities. Customers accept the hassle of dropping off their car, scrounging for a ride, and waiting days for a callback. The system is universally accepted. It’s also universally annoying.

When we asked “why,” the honest answer was: because that’s how it’s always been done. The service center model made sense when most repairs demanded heavy iron — hydraulic lifts, alignment racks, spray booths. But Tesla vehicles are fundamentally different. They’re software-defined. Many issues can be diagnosed remotely through the car’s data link. And a surprising share of physical repairs — more than we initially guessed — need nothing beyond a technician, a toolbox, and a flat surface.

The assumption that service required a service center wasn’t a physical constraint. It was a historical artifact.

Step two: delete. What can we strip out of the service process?

Once the service center assumption crumbled, a cascade of deletions followed. No service center means no facility lease, no overhead, no front-desk staff. No customer drop-off means no loaner fleet, no shuttle service, no waiting room with burnt coffee.

But the cuts went deeper. Remote diagnostics killed the initial inspection visit — the car could tell us what was wrong before the tech left the garage. Pre-staged parts killed the “we need to order a part and reschedule” loop. Automated scheduling killed the phone tag between customer and service advisor.

Each deletion removed not just a step, but the entire support infrastructure propping that step up.

Step three: simplify. What’s left, and how bare can we strip it?

The remaining process was radical in its simplicity. Customer flags an issue through the app. The car’s data confirms or sharpens the diagnosis. A mobile tech is dispatched with the right parts already in the van. The tech drives to wherever the customer’s car sits — home, office, airport garage — and does the repair. The customer might not even be there.

Compare that to the old way: call the dealer, book a slot, drive in, check in, wait, get a loaner, wait for a call, drive back, check out, pay. Eight or nine steps collapsed into one: the technician comes to you.

Step four: accelerate. How do we crush the cycle time?

With the stripped-down process running, acceleration zeroed in on logistics. Route optimization software clustered nearby appointments to slash drive time between jobs. Parts inventory was managed predictively — the twenty most common parts were always in the van. Scheduling algorithms matched tech skills to job types, putting the right person on each task the first time.

Result: a mobile tech knocked out six to eight jobs a day, versus three or four in a traditional center. Not because they wrenched faster — actual repair time was identical. But because the waiting, driving, and coordination dead time between jobs was crushed to near zero.

Step five: automate. What can software handle without a human in the loop?

The final automation layer covered everything except the physical repair itself. Diagnostic data streamed automatically from the vehicle to the scheduling system. Appointment confirmations, arrival ETAs, and completion notifications fired without human touch. Payment processed digitally. Customer satisfaction surveys triggered on their own.

The technician’s entire job became: drive to the spot, fix the car, drive to the next spot. Every admin, logistics, and communication task was handled by software.

Now zoom out and look at what happened. We didn’t set out to build a mobile service business. We set out to improve Tesla’s service operations. But as each step of the Algorithm stripped away constraints, the problem itself changed shape.

The original question was: “How do we cut service center wait times?” After five steps, the question had been rewritten: “How do we deliver service without a service center at all?”

That rewrite is the magic. It’s not a linear upgrade — ten percent faster, twenty percent cheaper. It’s a category shift. Mobile service doesn’t compete with traditional centers the way a faster center would. It competes on a completely different axis — convenience, time savings, customer experience.

The financial impact was jaw-dropping. The mobile service operation generated over three hundred million dollars in annual value — through slashed facility costs, higher customer satisfaction, stronger service retention, and the ability to reach customers in areas where building a center would never have penciled out.

None of it was blueprinted in advance. It emerged from the systematic, sequential application of the Algorithm.

This is what I mean by the multiplicative effect. Each step of the Algorithm doesn’t merely add to the ones before it — it multiplies them. Questioning opens space for deletion. Deletion creates room for simplification. Simplification enables acceleration. Acceleration lays the foundation for effective automation.

Do just one step — say, automation — and you get incremental gains. Do all five, in sequence, and the cumulative impact isn’t five times bigger. It’s exponentially bigger. The problem gets reframed, the constraints melt, and a solution surfaces that was invisible from the starting line.

Guidance#

Pick one process in your business — the most important one, the one that drives the most revenue or touches the most customers. Then run the full Algorithm, in order:

Question: List every assumption baked into the process. “It has to happen here.” “The customer needs to be present.” “Regulation requires this step.” Challenge each one.
Delete: For every step that survives questioning, ask: “Would the customer pay for this step?” Cut everything that serves the organization but not the customer.
Simplify: Compress what’s left. Can three steps become one? Can a ten-page form become a single question? Apply the newbie test.
Accelerate: Measure cycle time versus touch time. Kill the waiting. Go parallel where you can.
Automate: Only now. Automate the stable, predictable, well-understood parts. Keep humans on the complex, variable stuff.
Repeat: Go back to step one. Do it again. Each pass will surface new assumptions, new deletions, new simplifications. Keep cycling until the problem itself changes shape.

You’ll know you’ve hit a breakthrough when the solution you land on isn’t just better than where you started — it’s different. When the problem has been reframed. When your competitors can’t respond by copying your improvement, because it isn’t an improvement at all. It’s a new game.

That is the Algorithm at full power.