O'Connor: You See it, Read It and Repeat It - That's Not Learning

Walk into almost any tire dealership today and you'll find a technician with a diagnostic question pulling up an AI tool.

Picture a kid who's just finished her first week of gymnastics class. She comes home and does exactly what every parent has seen a hundred times — a wobbly cartwheel in the living room, narrated the whole way through: "You put your hands down like this, then your legs go over and you have to keep your arms straight or you'll fall." She isn't just showing the move. She's teaching it to whoever's standing there. 

For a full week, she'd been told what to do. She'd been shown what to do. A coach corrected the positioning of her hands, her legs and her arms a dozen times. None of that — the telling, the showing, the correcting — was the moment she learned the cartwheel. The moment she learned it was the moment she had to explain it to someone else. 

I keep thinking about moments like these because I think it's the exact moment our industry is at risk of skipping entirely — and technology is why. 

Walk into almost any tire dealership today and you'll find a tech with a diagnostic question pulling up an artificial intelligence (AI) tool instead of cracking open a manual or calling a mentor. He types in the symptom, the code and the vehicle. Within seconds, he's got a plausible answer — sometimes a genuinely good one. He reads it. He repeats it back to the customer or to himself or types it into the work order. The job gets done. Same goes for the manager who’s force fed any series of reports highlighting performance. They open the email or dashboard, see the output and move on. 

That's telling and showing, compressed into a search bar. And it's fast, which is exactly the problem — it's fast enough that it feels like understanding. 

Here's my test — the same one I'd apply to any tech, any service writer or any store  manager: Can they teach it? Not "can they repeat what the technology told them.” Can they explain — in their own words, to the next new hire — why that fault code shows up, why that fix works, why the numbers changed and how the behavior affected the outputs? If the answer's coming from a screen and it stops the moment the screen's not there, nothing was actually learned. Something was borrowed. 

I'm not writing this as an AI or tech skeptic. I use these tools regularly and so does most of the industry at this point, whether it's diagnostic assistance, service write-ups or figuring out a fair way to phrase a difficult conversation with a customer. The tools aren't the issue. The issue is what we let them replace. Told-and-shown was never the finish line, even before tech and AI. These tools have just made the told-and-shown phase so quick and so convincing that a lot of us have started mistaking it for the whole process. 

Think about the tech who gets an AI-generated answer, applies it correctly and moves to the next car. Six months later, he hits a variation of that same problem and same root cause, but with different symptoms because he never actually built the mental model underneath the answer. He memorized an output. He didn't learn a diagnosis.  

Compare that to the manager who took that same type of situation, but with data outputs and used it as a starting point, then had to explain to a co-worker why it made sense, where they could be going wrong and what he'd suggest first. That's owning something. The first scenarios simply rent the information, one search at a time. 

So here's what I'd challenge you to build into your shop: Treat technology and AI outputs the way you'd treat a suggestion from a parts catalog or a tip from a forum — a starting point, not a finish line. When a tech uses one of these tools to solve something, don't just check whether the car got fixed. Ask him to explain it to the newer guy standing next to him. Make him defend the answer, not just repeat it. Same with the manager. Have them explain the connectivity between the behavior and the output. If they can only recite what the tool told them, that's your signal the learning hasn't happened yet. The telling has, but not the teaching. 

This matters more now — not less — precisely because these tools are only going to get better and faster at telling and showing. That means the teach-back step is the only part of the process tech and AI can't do for your people. And even if they could, would you want that? It can give your people an answer. It can't give them understanding. Only a person explaining it to another person does that. 

The kid doing cartwheels in the living room didn't learn gymnastics because someone told her how. She learned it the moment she had to teach it. Your teams are no different and neither is anyone else in your business leaning on a screen for the first draft of an answer or solution. You see it, you read it, you repeat it — none of that is learning. Learning starts the moment you have to teach it back.

About the Author

Randy O'Connor

Randy O'Connor

Tire and auto industry veteran Randy O’Connor is the Owner/Principal of D2D Development Group (Dealer to Dealer Development Group). He can be reached at [email protected]. For more information, please visit www.d2ddevelopmentgroup.com.

Sign up for our eNewsletters
Get the latest news and updates