Picture a small textile workshop. Every month, the accountant prints the inventory report and leaves it on the owner’s desk. The owner glances at it, says nothing, and puts it in a drawer. Next month, the same problems appear: excess stock, late orders, unpaid invoices. The report was accurate. Nothing changed. This is the everyday reality for many small and medium-sized businesses across Turkey.
A MIS, or Management Information System, is a computer system that collects data from across the business and presents it to managers as useful reports. It pulls together figures from the accounting program, the stock records, and the sales ledger. The goal is to help the manager make the right decision at the right time. But here is the catch: the system produces the report, and turning that report into action is still a human job. In most businesses, that second step never happens.
The core of the problem is this: a report is a piece of information, not a decision. ‘Inventory turnover has slowed down’ is information. ‘Do not place new orders this week — clear the old stock first’ is a decision. Bridging the gap between the two requires discipline. Without that discipline, no matter how good your software is, reports will keep collecting dust. For businesses still recovering from the 2001 economic crisis, this gap is not a minor inefficiency. Cash is tight, margins are thin, and missing a signal costs real money.
Action discipline means defining three things in advance for every important indicator. First, a threshold: at what value does this indicator trigger a response? Second, an owner: who is responsible for evaluating the alert and acting on it? Third, a protocol: what is the first step when action is required? Take the accounts receivable ageing report — the list showing how long customer invoices have gone unpaid — as an example. Threshold: any invoice older than 60 days. Owner: the sales manager. Protocol: call the customer, ask for a payment plan, record the outcome. If these three things are not written down, the report goes back in the drawer.
The most immediate benefit of this model is that it eliminates surprises. Instead of sitting down at month-end and saying ‘This customer has not paid in three months,’ the phone call was made six weeks ago. When the stock report shows raw materials reaching a critical level, the warehouse supervisor has already contacted the supplier. By the time the manager sits at the table, the fires are already out. Even in a small manufacturing firm, once this habit takes hold, month-end meetings stop being crisis sessions and start being short, focused reviews.
A second practical benefit is that responsibility becomes clear. In most small businesses, the question ‘Whose job is this?’ goes unanswered. The owner tries to track everything personally, gets tired, and things slip through. Once action protocols are defined, ‘you handle receivables’ stops being a vague instruction and becomes a concrete assignment. The employee knows when to act, what to do, and where to record the result. That clarity is good for the employee and good for the owner.
Putting this model into practice does not require sophisticated software. You can take the weekly reports from your existing accounting or stock program, print them out, and write down the threshold, owner, and protocol for each key line. The real difficulty is not technical. It is a matter of habit. In the first few weeks, everyone will say ‘We already know all this.’ But a month later, you will have a written record showing which receivables were followed up, which stock alerts were acted on, and which ones were ignored. That record is the business’s memory.
Ask yourself this question: of all the reports produced last month, how many led to a concrete action? If the answer is ‘I am not sure,’ you have your starting point. Pick the three indicators that matter most — cash position, receivables age, inventory turnover — and define a threshold, an owner, and a protocol for each one. Do not leave it as a verbal agreement from a meeting. A rule that is not written down is not a rule. No matter how good your software is, skipping this step means your reports will always end up in a drawer.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 14, 2003 and has been automatically translated into English and other languages using machine translation.