Menu
Talk to us →
← All insights

Technology rarely fails first. People and process usually do.

By Tony Byrne · Vertex Automotive Solutions

When a new system disappoints, the root cause is often unclear ownership, weak routines or inconsistent behaviours rather than the software itself.

Editorial illustration for Technology rarely fails first. People and process usually do.
Original Vertex editorial illustration.

Automotive businesses keep buying systems to solve operating problems. Sometimes the technology is the right answer. But if the process is ambiguous and accountability is weak, digitalisation simply makes the ambiguity move faster.

A system cannot decide who owns the customer

A DMS can timestamp a job. A CRM can trigger a message. A warranty platform can validate fields. None of them can resolve a culture in which the service advisor assumes the workshop controller will call the customer, the controller assumes parts will update the advisor, and everyone believes someone else owns the exception.

Standard work creates freedom

Good process is not bureaucracy for its own sake. It defines the minimum reliable way of working so people can spend their judgement on the exceptions that actually need judgement. In aftersales that means clear booking standards, pre-pick rules, escalation points, evidence requirements, customer update triggers and end-of-day control.

Training must be connected to the operating model

A one-day course can improve knowledge and confidence, but capability only changes when the workplace reinforces the behaviour. Coaching, observation, role clarity, simple measures and manager follow-through matter more than the certificate.

This is why training, operational consulting and intelligence belong together: the evidence identifies the gap, the process defines the required behaviour and coaching helps the behaviour hold.

The leadership test

Before approving another technology project, ask three questions: Which decision will this make better? Which role will act differently because of it? What existing routine will change when it goes live? If those answers are vague, the implementation risk is already visible.

Test the process under pressure

The real test of a process is the morning when someone is absent, a delivery is late and three customers arrive together. If the standard only works when every experienced employee is present, the business has documented an ideal rather than designed a reliable operation. Observe the handovers under normal pressure before deciding that staff need more training.

Choose one recurring exception and define the minimum information that must travel with it. A delayed part, for example, needs an affected job, a customer commitment, a current supply position, an escalation owner and the next review time. Agree where that record lives so the advisor and controller do not maintain competing versions.

Managers should reinforce the routine through short observation and feedback. Correct the unclear instruction before criticising the person who interpreted it differently. The commercial return comes from reducing duplicated checking, preventable interruption and missed promises. Technology becomes useful when it supports that behaviour consistently and makes an exception visible before the customer has to expose it.

FROM INSIGHT TO ACTION

What is your operation telling you?

Bring us the evidence. We will help you turn it into a decision.

Continue exploring