An ERP Consultant Is Not a Digital Transformation Advisor: Where the Gap Begins

After a decade or more of ERP project work, many consultants naturally start calling themselves digital transformation advisors. On paper the logic holds: experience with enterprise systems like SAP, Logo, Netsis or IFS brings genuine organisational knowledge, integration depth, and the hard-won ability to manage executive expectations. Yet a project I led in early 2017 with a mid-sized food manufacturer in Konya showed me something I could not unsee: a consultant who understands ERP but cannot read an organisation at the strategic level will solve the technical problem and leave the transformation problem completely untouched. The gap between the two roles is not primarily a gap in methodology. It is a gap in perspective — and that gap costs companies real money.The Konya manufacturer ran a bread and dry-food operation with 295 employees, supplying domestic retail chains and exporting to Gulf markets. Their five-year-old ERP system was, in management’s words, ‘working but not working for us.’ The production planning module sat unused. Stock figures were unreliable. The sales team had quietly rebuilt its own parallel Excel universe rather than log anything in the system. To an ERP-trained eye, this looked like a textbook user adoption problem. But the actual situation was far more entangled: the business processes in practice had drifted so far from the processes the system was originally built on that another round of reimplementation would simply restart the same decay cycle. Seeing that required not ERP knowledge — it required process mapping literacy and basic organisational diagnosis capability.ERP consulting has a well-defined success condition: the system is live, users can log in, the accounting integration closes correctly, and the project manager signs off on go-live. Digital transformation advising starts from a fundamentally different question: which business processes should this organisation use to generate competitive advantage, and which processes must be simplified before any technology layer can create durable value? That question demands strategic judgement, not technical execution. And strategic judgement does not flow automatically from a portfolio of successful ERP go-lives. In Konya, someone arriving with a pure ERP mandate could have reconfigured the system competently. The transformation advisor asked a prior question: why have sales, production and logistics become isolated from each other? The answer was found not in any system log but in a structural trust deficit between two department heads who had been in open conflict for nearly three years.The sharpest practical line between the two roles appears at the integration question. An ERP consultant answers it technically: which modules exchange data, which file bridge or service layer connects them, where the master data definitions conflict. A digital transformation advisor must answer the same question organisationally: why is the integration breaking down, which unit is protecting its own data island, who is withholding information and for what reason? In Konya, the production manager and the sales director were entering contradictory stock figures into the same system. There was no technical explanation. When the right questions were asked in the right room, the pattern was visible inside thirty minutes. No ERP log would have surfaced it. This is the point at which consulting maturity overtakes technical knowledge as the decisive variable.One thing deserves to be said directly: not every ERP consultant should attempt this transition, and not every engagement requires it. Some projects genuinely call for a system architect, not a process strategist. The market problem in Turkey in 2017 is that the label ‘digital transformation consulting’ has been applied so loosely that many organisations cannot identify what they are actually buying. The Konya company had framed its need as ‘fix the system.’ The underlying need was ‘realign the organisation.’ A consultant who cannot tell those two things apart will successfully deliver the first, politely close the project, cash the invoice, receive a thank-you email — and watch the system go dark again within six months. A significant share of ERP reimplementation projects in Turkey are products of exactly this cycle repeating.For any practitioner who wants to make this transition honestly, the practical decision criterion is simple: can you analyse the people and processes using the system, not just the system itself? In Konya, the sequence I followed was this. First, three days of observation — sales floor, production line, warehouse — before opening a single configuration screen. I mapped actual daily workflows by hand. Second, I pulled real usage data from the ERP: which modules were opened, by which users, and how often. Several screens were effectively ghost modules — present in the menu, untouched for months. Third, I placed those two data sets side by side in front of the management team. The recommendation that followed had nothing to do with software: it was a weekly stock reconciliation meeting between sales and production, chaired by the CFO. No code changed. Within eight weeks, stock discrepancy incidents fell from %58 to %16. The system did not need to be smarter. The organisation needed a single structured conversation it had been avoiding.The move from ERP delivery to digital transformation advising is a shift in perspective, not a change in credentials. Technical knowledge remains the foundation — without it you cannot earn organisational trust in the first place — but it stops being the primary instrument. The Konya manufacturer’s warehouse floor taught me more in three days than any configuration guide. A digital transformation advisor is not someone who knows the technology. It is someone who reads the people and processes that the technology is supposed to serve. That perspective begins in ERP projects but does not end there. If you are a manager evaluating a consultant today, ask one question: did they explain the system to you, or did they explain why your organisation cannot use it?

This article was originally published in Turkish by Gökhan MERCANOĞLU on February 4, 2017. The English edition has been reviewed and edited by the author.


The first gain in user adoption investments is usually visibility. The company starts to see where it slows down, which information is missing, and which decisions are delayed. This visibility may be uncomfortable, but it is the strongest starting point for sustainable improvement.


Gökhan Mercanoğlu
ERP ve Kurumsal Yazılım