Your dealer network is trained. That doesn’t mean it is ready.

The launch dashboard is green. Training developed. Translations completed. Markets activated. Technicians enrolled. Completion rate: 94%.

The network is ready. Right? Not necessarily.

One of the most dangerous assumptions in automotive learning is that training completion equals operational readiness. It does not. Completion tells you that training happened. Readiness tells you whether the network can perform when customers arrive. Those are different questions.

Product launches expose the difference

Consider the launch of a vehicle using unfamiliar technology. The OEM may have done everything expected from a learning perspective. Technical training has been delivered. Sales teams have received product training. Service advisors understand the maintenance proposition. Digital modules are online.

Yet the first difficult vehicles arrive and problems appear.

• A technician struggles to diagnose an unfamiliar symptom.
• A service advisor cannot confidently explain a charging-related concern.
• A workshop lacks the correct equipment.
• A dealer has only one trained technician, who happens to be on leave.
• Another dealer completed training months ago but has not yet worked on the technology.

Technically, the network was trained. Operationally, parts of it were never ready.

Readiness is a system

Capability lives inside an environment. That means readiness depends on more than whether an individual attended training.

People need the knowledge and skills. But they also need tools. Access to technical information. Correct equipment. Processes. Escalation routes. Confidence. Enough exposure to maintain competence. And sufficient capability across the network to absorb real demand.

A weakness in any of those areas can create a performance bottleneck. This is why dealer readiness is best viewed as a system condition, not a training metric.

The average hides the problem

Network-level reporting makes this especially tricky. Imagine an OEM network with a 92% training completion rate. That sounds strong.

But perhaps the missing 8% is concentrated in fifteen high-volume dealerships. Or perhaps almost every dealership has one trained technician, but workload requires three. Or perhaps training was completed, but practical capability differs dramatically between participants. Or perhaps the people originally trained have already left the organisation.

"The average still looks reassuring. A customer arriving at one unprepared dealership experiences a network that is 0% ready."

Readiness changes over time

Another important reality is that readiness is not permanent. Networks move. People leave. New employees join. Models change. Software updates introduce new behaviour. Technical procedures evolve. New repair patterns appear once vehicles accumulate real-world mileage.

A network that was ready at launch may be less ready twelve months later. Conversely, technicians who initially struggled may become highly capable once they gain experience.

So readiness should not be treated as a one-off launch activity. It needs to be maintained. The learning challenge evolves from preparing the network to supporting the network while it learns from reality.

Central training cannot predict everything

Automotive organisations understandably want training ready before launch. But the field will always teach us something the training department did not know. New diagnostic patterns appear. Customer questions evolve. Certain procedures prove more difficult than expected. Some explanations work better than others. Some markets encounter specific issues sooner.

A mature learning system therefore needs a feedback loop. What are technicians struggling with? What is technical support seeing repeatedly? Which questions are trainers receiving? Where are warranty or diagnostic patterns emerging? What are customers asking dealerships?

That intelligence should flow back into learning. Training should not be frozen at launch. It should evolve with the vehicle population.

Train for the first difficult day

There is also a design issue. Launch training often tries to cover everything. Every technical feature. Every specification. Every procedure. Every new component. The result can be an impressive but cognitively overwhelming programme.

Readiness requires prioritisation.

• What must people absolutely understand before the first vehicle arrives?
• Which tasks are most safety-critical?
• Which failures will have the highest operational impact?
• Which situations are likely to be unfamiliar?
• What information can be found later when needed?
• What deserves hands-on practice?

The objective is not to create a walking service manual. It is to prepare someone for the first real decisions they will need to make.

A better question for OEM learning teams

Instead of asking “Has the network completed training?”, ask “Where would we currently expect performance to break?”

That question creates a very different conversation. It connects learning with operations. It exposes differences between markets and dealerships. It identifies where support may be required. And it turns readiness into something that can actually be managed.

Training remains crucial. But it is one input into readiness, not the definition of readiness itself. Because ultimately, the customer will never ask whether the technician completed the LMS module. They will ask whether the dealership can solve the problem.

"For IAS, network learning is successful when capability reaches the job. That means connecting training design, trainer capability, localisation and real-world implementation instead of stopping at course delivery."