Last month, the general manager of a mid-sized textile company put it plainly: ‘We installed the ERP, three modules are running, but I still hear different numbers from different people every morning.’ This complaint is familiar across many Turkish businesses of similar scale. The system is in place, the software is running, the data sits somewhere in the database — yet management decisions still rest on intuition, habit, or whoever speaks loudest in the room. The problem is not the software. The problem is the management culture that needs to form around it.
An information system is the infrastructure that collects raw data and turns it into meaningful business information. ERP software represents the most integrated form of this infrastructure, bringing together accounting, inventory, purchasing, sales, and production data into a single database and generating reports for management. But for those reports to reach the decision table, to be discussed and acted upon, a culture needs to exist. By culture, the meaning is specific: a management team that knows which data matters, reads it regularly, and shapes its decisions accordingly. Software does not create this culture on its own.
The first dimension of a data-driven management culture is leadership. Unless the general manager or business owner asks ‘what do the numbers say?’ in meetings, the team will not prepare the numbers. In Turkish SMEs, trust in the owner’s intuition runs deep — and that instinct is not wrong in itself, but it is no longer sufficient on its own. In an environment of tightening margins, rising competition, and shifting customer expectations, decisions backed by data are simply more reliable than those made on feel alone. The leader must be the first person to use the data; otherwise, the system becomes an installed but unused tool.
The second dimension is measurement. Every business has a handful of key indicators worth tracking: inventory turnover, collection period, gross margin, revenue per customer. These figures can already be produced inside most ERP systems; the question is which ones to watch weekly, which ones monthly, and who is responsible for reading them. Too long a list and nobody reads it; too short and a critical problem surfaces too late. Experience suggests that five to eight core indicators give most SMEs a workable starting point. Turning these into weekly printed reports or Excel tables shared by email puts the system within reach of the management table — and in 2005, that is exactly how most businesses are doing it.
The third dimension is habit. The habit of reading and discussing data takes root through regular repetition. A short weekly review meeting, held at the same time, covering the same indicators, gradually builds a shared language across the management team. The sales manager stops saying ‘this month went well’ and starts saying ‘our collection period extended by four days compared to last month.’ The finance manager moves from defending numbers to explaining them. This shift in language seems small but meaningfully improves the quality of decisions. Building the habit takes six to twelve months; during that period, the leader will need to initiate the meeting repeatedly before it becomes self-sustaining.
Real obstacles stand in the way of building this culture. The most common is data quality. Inventory entries are incomplete, invoice dates are wrong, the same customer has been opened under three different codes. The ERP system amplifies these errors, and the reports start to look unreliable. At this point, many managers say ‘I don’t trust the system’ and revert to old habits. The right response is the opposite: fix the data entry discipline, correct the records, and rebuild confidence in the output. The second obstacle is time pressure. In the daily grind of operations, the weekly review meeting is the first thing to get postponed. Locking it into the calendar and keeping it tight — no more than forty-five minutes — is the most effective way to protect continuity.
When planning for 2006, three questions are worth putting on the table. What are the five core indicators of this business, and who tracks them, how often? Is data entry responsibility clearly assigned, or does everyone enter things ‘somehow’? How many of the general manager’s recent decisions were made after reading actual figures? Honest answers to these questions reveal where the system stands and how far the culture has travelled. Installing the system was the hard, expensive step. Making it work requires less money but considerably more management resolve — and that resolve starts with deciding that data is not just a reporting formality but the foundation of how the business is run.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 25, 2005 and has been automatically translated into English and other languages using machine translation.