Digital Transformation in 2019: No Longer a Project, but an Organizational Reflex

A manufacturing company general manager said something telling last year: ‘We completed our ERP project successfully — our digital transformation is done.’ The budget closed, the consultants left, the system went live. Twelve months later, reports were still being exported to Excel and formatted by hand, process improvement meetings had stopped, and newly available system modules sat untouched. The transformation was ‘finished,’ but the company had drifted back to its old habits. This pattern repeats across dozens of mid-sized Turkish firms, and the root cause is not technology — it is the decision to define transformation as a project.

Equating digital transformation with a project means treating it as work that has a start date, an end date, and a budget that closes when it is done. That framing feels logical; project management disciplines taught us to think in terms of scope, time, and cost. But transformation lives outside that triangle. Customer behaviours shift, competitive conditions evolve, regulatory requirements change. Turkey’s e-Waybill mandate in 2019 caught many companies unprepared — including firms that had already ‘completed’ their e-Invoice and e-Ledger transitions as discrete projects. The lesson is straightforward: transformation is not a one-time software installation. It is an organization’s sustained capacity to respond to changing conditions.

This is where the concept of organizational reflex becomes meaningful. A reflex is a learned and internalized response pattern; it does not wait for a decision meeting or a project approval. A digitally mature company, when a new regulatory requirement arrives, does not launch a project to figure out how to comply — it adapts using existing infrastructure and existing capability. Turkey’s 2018 currency crisis made this divide visible in stark terms. Companies that could monitor their cost structures in near real time, with supplier and customer data integrated in a single system, made fast decisions. Companies managing that data in disconnected Excel files spent weeks in uncertainty. The technology infrastructure was often comparable; the difference was whether that infrastructure had been converted into organizational reflex.

How is that reflex built? The first condition is placing data at the center of operational decision-making, not at the edge of it. When a retail firm’s inventory manager reviews an automatically generated exception report every morning and acts on it before the day begins, that is a reflex. When the same report is presented to a director in a weekly meeting, that is still a process — not yet a reflex. The second condition is developing technology competency inside business units, not only inside the IT department. A procurement manager should be able to run a supplier performance analysis independently. A finance team should be able to update a cash flow model without raising an IT request. Without this distributed competency, every new need becomes a ticket, and transformation stalls at the IT queue. The third condition is embedding a continuous improvement cycle into the organizational calendar: quarterly process reviews, annual system capacity assessments, monthly data quality checks. Without these cycles, the system gradually becomes what practitioners call ‘neglected infrastructure.’

A realistic boundary deserves to be drawn here. Organizational reflex is not built at the same pace or the same cost for every company. A significant share of Turkish manufacturing and textile firms with fifty to two hundred employees are, as of 2019, still operating with a single IT generalist or fully outsourced IT support. For these companies, the idea of ‘technology competency inside business units’ is aspirational but slow to realize. Training budgets are typically among the first items cut when currency pressure and inflation tighten operating margins. This means that reflex-building requires a different roadmap for a resource-constrained SME than it does for a large corporate group. For the SME, a realistic starting point is this: automate the data flow in one or two critical processes, ensure the people in those processes use the system as part of their daily work — not as an occasional reference — and then move to the next process. Attempting to transform the entire organization simultaneously exhausts both budget and motivation.

The separation between companies that build reflex and those that do not will become sharper in the coming years. Hyperautomation is entering the corporate agenda; RPA tools are automating repetitive tasks, and process mining is making bottlenecks visible in ways that were previously impossible without dedicated analysis teams. These tools generate value quickly in companies that already have digital reflex. In companies that have not yet stabilized their basic data infrastructure, they tend to begin as new projects and stall halfway. The tool is not the differentiator — the underlying capacity is. For an Izmir-based exporter, the value of RPA in customs documentation does not come from the automation itself; it comes from the fact that the firm has already documented and standardized its processes. The RPA simply accelerates what is already structured.

As 2019 begins, the question worth asking is direct: in your last completed digital transformation project, which habits remained six months after the project team disbanded, and which ones reverted? If the honest answer is ‘most of them reverted,’ the problem is not in the technology selection — it is in the transition from project delivery to organizational capability. Answering that question before committing to the next project budget is a more valuable starting point than any new software evaluation.

This article was originally written in Turkish by Gökhan MERCANOĞLU on January 7, 2019 and has been automatically translated into English and other languages using machine translation.


The first gain in business unit ownership 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