We ran training sessions for several days straight. The following week, the service technicians were back to writing job cards on paper. This happened at a mid-sized automotive service company in Ankara — 78 employees, running both authorised and independent repair work. When I describe that scene, people sometimes laugh. But there is nothing funny about it. The same scene played out at dozens of workshops across Turkey, and it is still playing out today. ERP — enterprise resource planning, meaning software that brings a company’s inventory, accounting, sales, and service operations into a single computer system — is not primarily a technical challenge. It is a human challenge. Companies that understand this early get the software working. Those that do not end up paying the licence fee and shelving the program within months.The automotive service sector has its own internal culture, and it runs deep. The workshop foreman has been doing things the same way for years: job orders in his head, parts ordered by phone, invoices written by hand. This person genuinely knows how the work flows. When ERP arrives, the foreman sees it as an outside intrusion rather than a tool. The feeling of ‘I know my job’ creates a quiet but powerful resistance to the new system. Training sessions were delivered. Screens were shown. Buttons were explained. But when service forms start piling up in the desk drawer a few days later, the problem is not the software. The problem is that the training never recognised this resistance and made no attempt to work through it. The central argument here is this: ERP training in automotive workshops is not technical instruction — it is a negotiation with craft culture. Every training project that begins without understanding this produces a half-used system.Before the project in that Ankara company began, I spent two days walking the workshop floor. The service reception clerk was entering every job order into two separate notebooks — one went to the technicians, one stayed at the desk. I asked why. ‘What happens if the one we send to the technician gets lost?’ she said. Behind the double-entry system was a concrete reason rooted in distrust. Could ERP eliminate this? Yes. But first, someone needed to understand where that distrust came from. Consultants who skip this question install the software, deliver the training, and watch users drift back to old habits six months later. Requirements analysis — meaning the step where you go on-site and understand what is actually happening, not what the org chart says should be happening — must come before training. The difference between the written process and the real one is where ERP projects either succeed or stall.Looking at this experience clearly, ERP training in a service business has three distinct layers. The first is technical instruction: which menu does what, what goes into which field, how to run a report. This is the easiest layer, and most training programs stop here. The second is process alignment: mapping the company’s existing workflow onto the software modules. In automotive service, this is particularly critical — service intake, job order creation, parts ordering, cost calculation, and invoicing each need a clear counterpart in the system. If these steps are not mapped properly, the user stares at the screen not knowing what to do and reaches for the paper pad. The third layer, and the least discussed, is management ownership. If the business owner or the general manager is not standing behind the program, no training will stick. At the Ankara company, the owner’s attitude of ‘you handle it, I won’t get involved’ was the single biggest reason the first round of training collapsed within the first month.What actually changes when training is structured correctly? During a second attempt at the same company — this time rebuilding the process from scratch — we sat down with the service reception clerk and mapped each job order step directly into the software. We ran a separate session for the technicians. The question we asked them was not ‘how does a job order get closed in the system’ but ‘how do you enter what you did into the system.’ These are different questions. The first is software-centred; the second is user-centred. The result was honest: we never fully eliminated paper job cards — that is worth saying plainly. But the share of job orders entered into the system grew noticeably over roughly four and a half months. Parts inventory tracking fell into a reliable pattern. Month-end accounting closure came down from several days to a single day. These gains seem small on paper. In a 78-person workshop, cutting month-end close by that margin means the accountant and the owner stop working weekends. That is a concrete result, not a promise.The real difficulty in this environment deserves a direct look. In early 2003 in Turkey, the number of mid-sized automotive service businesses actually running ERP was very small. Large authorised dealership networks operated their own systems provided by the manufacturer. Independent and mid-tier workshops either managed with a standalone accounting program or kept everything on paper. When a company in this position decided to adopt ERP, it had almost no local reference point — no neighbouring workshop it could visit and say ‘we want what they have.’ The question ‘have you seen this working somewhere else?’ almost always drew a blank. That uncertainty pushed the decision-maker toward hesitation before the software even arrived. On top of this, internet connections at the time were mostly dial-up — a telephone-line connection — or early ADSL where it was available at all. Remote support, update installations, and even licence activation regularly turned into technical standoffs that could not be resolved without a technician on site. Every unresolvable problem pushed the user one step further away from the system.If you are considering an ERP project in an automotive service business, ask three questions before you begin. First: will the business owner genuinely take ownership of this project, or will the response be ‘I hired you, you figure it out’? Without that ownership, training dissipates. Second: are job orders, parts requests, and invoices currently on paper or in another program? Moving from paper takes longer than moving between systems — build that time into your plan. Third: why would the foreman and the service intake clerk want to switch to this program? If you cannot answer that question from their perspective, do not start the training. ERP is a tool. If the person using it is not convinced, the tool sits unused. Buying the software does not mean you have solved the problem. It means you have bought the opportunity to solve it — and the work of actually solving it starts with the people, not the program.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 11, 2003. The English edition has been reviewed and edited by the author.