Picture the general manager of a mid-size textile company: the accounting software runs on one machine, inventory is tracked in a separate spreadsheet, and the sales team keeps its own records in a notebook. At the end of every month, the finance manager spends two full days reconciling these three sources before a single management report can be produced. This is not an unusual picture in Turkish SMEs right now; buying software and actually using it well are two very different things, and the gap between them is still wide. The real question is: where do you start closing it?
Several topics compete for a manager’s attention at once: enterprise resource planning, meaning ERP; defining and improving business processes; and turning raw data into meaningful reports. Each of these can look like a separate project, but they are in fact linked. Without ERP, producing reliable data is difficult. Without reliable data, measuring performance is impossible. And without performance measurement, you cannot know which processes need fixing. These three areas are not independent investments — they are links in the same chain, and the chain only holds when all three are addressed together.
So where should a company begin? The answer depends on the firm’s current size and infrastructure. For a business with fewer than fifty employees that still runs accounting and inventory in separate programs, the first priority is straightforward: install an integrated accounting and inventory solution. At this scale, moving directly to SAP or Oracle is neither necessary nor economical. Domestic solutions such as LOGO, Netsis or Mikro offer cost-effective options with strong local support networks, which matters a great deal when something goes wrong during implementation. The critical point is this: software installation is a starting point, not a finish line. After the software is in place, data must be entered correctly, users must be trained, and reports must be read regularly. Without these disciplines, even the best program becomes idle within months.
For companies between fifty and two hundred employees, the situation is somewhat different. An accounting package is usually already in place; the problem is that different departments operate in isolation from each other. When purchasing, production and sales do not share the same database, the manager cannot make real-time decisions with confidence. The right move here is either to consolidate existing software under a single ERP framework or to add missing modules to the current system. Once this step is taken, the manager can for the first time look at the whole business from a single screen: how much stock is on hand for each product, which customer invoices are overdue, which raw material orders are still pending. That visibility alone is a meaningful competitive advantage in a market where most competitors are still working blind.
Once data starts flowing, the next question becomes: how do we read it? Standard accounting reports satisfy legal requirements but fall short for management decisions. Profitability by sales channel, cost distribution by product group, average collection period by customer — these figures can only be calculated if the data has been structured correctly from the start. Most ERP systems include reporting tools that can produce these views, but those tools only work when data entry has been disciplined and consistent. This means reporting quality is directly tied to data entry discipline, which shifts the real challenge from the technical side of a software project to the human side.
The difficulty managers most commonly face is this: the project looks like a technical task at the outset, but the strongest resistance comes not from the IT team but from the business units. The accounting department does not want to give up the Excel files it has used for years. The sales team would rather skip entering data into the new system. The production supervisor sees recording stock movements in the software as a waste of time. These are not technical problems — they are change management problems. The success of a software project depends largely on how firmly senior management commits to the change. The software vendor can complete the technical installation; making users actually adopt the system is entirely the manager’s responsibility.
As the company moves toward 2007, a manager who wants to take the business to the next level can follow a clear sequence of priorities. First, establish data integrity: make sure every department enters data into the same system according to the same rules. Second, define a small set of core management reports and commit to reading them every month without exception. Third, use those reports to identify recurring problems and build a prioritized list of process improvements. These three steps come before any large software investment. A powerful system installed on a weak foundation will always disappoint. Software is a tool; strategy still sits on the manager’s desk.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 24, 2006 and has been automatically translated into English and other languages using machine translation.