Picture a mid-sized textile factory. The purchasing manager keeps his own records, the accounting department works from a separate ledger, and the warehouse supervisor maintains yet another set of notebooks. The company decides to install an ERP system. A consultant arrives, the software gets set up, and three months later the project has stalled. Why? Because nobody could answer the question: ‘who signs off on this screen?’ Everyone was waiting for someone else to decide.
The most common reason ERP projects slow down is not technical. The software itself works. The problem is that nobody inside the company has clear authority over specific decisions. When a change is needed in the purchasing workflow, does the purchasing manager decide, or the general manager, or the finance director? That kind of ambiguity can push a project back by weeks. This is where process ownership comes in. A process owner is the single manager responsible for one defined area of the business. Decisions come from that person, and that person answers for the results.
Here is how it works in practice. The company lists every major business flow: purchasing, sales, inventory, accounting, production. Then one name is written next to each item. That person is the manager who knows that area best and runs it day to day. The warehouse manager takes ownership of inventory. The finance manager takes ownership of invoicing and collections. This assignment does not stay on paper. The general manager announces it in writing so that everyone in the company knows who holds authority over what.
The practical benefit is straightforward. When the consultant brings a proposed screen layout to a meeting, the process owner is in the room and can say yes or no on the spot. Before this kind of structure existed, the same decision might require coordinating three different managers across separate meetings, with faxes going back and forth and schedules never quite lining up. Think of it like the branch manager at a bank who has the keys to the vault. Without that clear authority, every small transaction would require a call to the head office. One decision point means faster movement.
A process owner has three core responsibilities. The first is working directly with the consultant to define how the process will run inside the new system. Questions like ‘what happens when a purchase order arrives, who approves it, does stock update automatically?’ belong to the process owner to answer. The second responsibility is preparing the team for the new way of working. When the software changes, habits must change too. If there is resistance from staff, the process owner addresses it. The third responsibility continues after the consultant leaves. Problems surface after go-live, and the process owner is the first person those problems reach.
There is a real difficulty here that cannot be ignored. In small and medium-sized companies, managers already carry heavy workloads. The finance manager handles bookkeeping, tax filings, and payroll all at once. Adding ERP process ownership on top of that is a serious burden. Project meetings get missed, responses to the consultant are delayed, and the timeline stretches. The general manager must treat process ownership as a priority assignment, not an extra task. In some cases, routine duties need to be shifted to another person so the process owner has the time to do the job properly.
There is also the question of authority matching responsibility. It is not enough to name someone a process owner if they cannot actually make decisions. If every choice still has to go up to the general manager for final approval, the structure does not help. The person named as process owner must genuinely hold the authority to decide within their area. Without that, the title is meaningless and the bottleneck simply moves one step to the left.
If your company has committed to an ERP installation and is in early conversations with a consultant, the first practical step is simple. Write down every major business process on a single sheet of paper and put one name next to each one. Tell that person clearly: ‘final decisions in this area are yours.’ Then announce it to the rest of the company. A consultant’s technical knowledge only goes so far. Without an empowered decision-maker on the client side, even a well-designed system will sit idle while people wait for someone to say yes.
This article was originally written in Turkish by Gökhan MERCANOĞLU on April 8, 2002 and has been automatically translated into English and other languages using machine translation.