A general manager of a mid-sized manufacturing company sits across the desk asking why the ERP investment made last year has not delivered the expected return. The software is installed, licenses are paid, training sessions are done. Yet the sales team still works off its own spreadsheets, data inconsistencies between the accounting and inventory modules remain unresolved, and every approval layer is stacked on top of the last. The problem is not the technology. The problem is the organizational structure trying to carry it.
Digital transformation is not, at its core, a software installation project. It means redesigning decision-making mechanisms, information flows, and accountability boundaries. Many SMEs in Turkey miss this distinction at the outset: they purchase the technology but leave the organization unchanged. Yet every digital tool — from e-Invoice compliance to mobile ERP access, from cloud-based reporting to cross-departmental data sharing — assumes a certain speed and flexibility in approval processes. A layered command chain undermines that assumption from the start.
At the center of the problem sits the question of delegation. In the traditional Turkish business culture, decision-making authority tends to concentrate at the top; middle managers often function as relays waiting for approval rather than owners acting on judgment. This structure produces a cycle where information travels upward and decisions travel downward, consuming time at every step. Digital systems demand the opposite: information must be real-time, decisions must be made at the point of action, and execution must be fast. A sales representative checking stock availability on a mobile device during a customer visit, generating a price offer, and entering the order into the system only makes operational sense when that representative is authorized to make those decisions. Without delegation, mobile ERP becomes an expensive display tool and nothing more.
Cross-functional team structures emerge as a critical mechanism here. For sales, logistics, finance, and production to operate within a shared data environment, these departments need to meet within a common accountability space. In companies organized as silos, each department optimizes its own process; but end-to-end process efficiency across the whole organization belongs to no one’s agenda. ERP systems make this integrated view technically possible, but if the organizational structure remains divided, system integration stays on paper. In practice, cross-departmental data conflicts, authority disputes, and the ‘that’s not our problem’ reflex paralyze the system entirely.
When the issue of decision speed is examined through a total cost of ownership — TCO — lens, the picture sharpens further. Beyond license and infrastructure costs, the opportunity cost of delayed decisions is routinely overlooked. Responding late to a customer request, missing a procurement window, or failing to identify excess inventory in time all translate into concrete financial losses. An ROI calculation limited to the efficiency gains the software itself delivers becomes misleading; without improving the organization’s decision speed, the efficiency ceiling is low. The real return on transformation appears only at the point where technology and organizational structure change together.
To be direct: this transformation is not easy. Delegation is the area where Turkish family businesses and traditional corporate structures show the most resistance. The founder or general manager approving every decision is partly a matter of trust, partly a fear of losing control. Moving to cross-functional team structures narrows the influence domain of department heads, which generates political resistance inside the organization. Moreover, unlike a software deployment, organizational change has no completion date — it requires continuous management. When companies underestimate this difficulty and focus exclusively on the technology investment, the transformation stalls halfway.
The practical decision criterion for executives comes down to one question: when a frontline employee identifies a problem today, how many levels does it travel through before it becomes a decision? If the answer is three or more, the organizational design needs to come to the table before the digital investment does. Allocating a portion of the technology budget to change management consulting, redrawing the authority matrix, and preparing middle managers for their new roles is as strategic a spend as a software license. Digital transformation is not a technology project — it is a leadership decision, and the hardest part of that decision is confronting the hierarchy itself.
This article was originally written in Turkish by Gökhan MERCANOĞLU on May 7, 2018 and has been automatically translated into English and other languages using machine translation.