A mid-sized machine manufacturer in Bursa launched a BPM project that, six months in, had nearly stalled. The software was installed, processes had been mapped, and flow diagrams were ready. But on the ground, the picture was different: the purchasing department was still working with its old spreadsheets, and production planning meetings ran on personal observation rather than process data. The project manager summed it up simply: ‘We bought the system, but we never built the culture.’ That sentence explains why so many BPM initiatives fall short.
BPM, business process management, is at its core a management philosophy rather than a software matter. Software provides a tool for applying that philosophy, but without a clear approach to how the organization defines its processes, who is held accountable, and how performance is measured, no tool will deliver results. A process-oriented management culture means replacing the mindset of ‘this is how we do things around here’ with ‘this is how we manage our processes.’ That shift is not a technical installation; it is a behavioral change, and it takes months or even years to take hold.
The first step in building this culture is establishing process ownership across the organization. Every critical business process needs an owner — someone responsible for defining it, monitoring it, and driving its improvement. This is usually a department manager or a senior specialist, but the title matters less than the accountability. The process owner is expected to report regularly on the process’s performance indicators and to explain deviations when they occur. In many mid-sized Turkish companies, this kind of clear accountability is still absent; the question of ‘whose job is this?’ often goes unanswered. Resolving that ambiguity is the first concrete step toward a BPM culture.
The second critical element is grounding performance reviews in process data. In traditional management, meetings tend to be dominated by ‘what happened and why’ discussions where decisions rest on experience and intuition rather than numbers. In a process-oriented culture, every management meeting opens with a review of pre-defined process indicators. How many days does it now take to fulfill an order? How did the return rate change this month? Where did the approval steps create a bottleneck? These questions enter the agenda systematically. Over time, managers become accustomed to speaking in process data, and the decision-making mechanism shifts from intuition toward evidence.
Building a continuous improvement habit is perhaps the hardest part of this culture to establish. It requires the organization to genuinely accept that the current state is never good enough. This means scheduling regular process review sessions, recording improvement suggestions from the floor, and measuring the results of changes once implemented. Making small improvements visible matters: when a step is shortened, an approval is streamlined, or an error rate drops, recognizing that change motivates the organization to repeat the cycle. When improvement suggestions instead disappear into bureaucratic channels, motivation fades quickly.
The most common obstacle in building this culture is resistance from middle management. Process ownership and performance visibility can feel threatening to managers who have grown accustomed to operating in ambiguity; clear processes reduce the informal latitude they have relied on. As processes are defined and data enters the conversation, that latitude shrinks. Senior leadership needs to anticipate this resistance and treat the BPM initiative not as a technical project but as a redefinition of how the company is managed. Without visible commitment from the top, process culture gets blocked at the middle layer and the software gradually ends up sitting unused.
For a small or mid-sized business owner evaluating a BPM initiative, the real question to ask is this: for any given process in your company today, can you name its owner — and can that person tell you last month’s performance in numbers? If the answer is no, that structure needs to be built first. Software selection comes second. When process ownership is defined, performance reviews run on data, and improvement suggestions are handled systematically, BPM software generates real value. Without that foundation, even the best tool accomplishes nothing. Culture is the precondition; everything else follows from it.
This article was originally written in Turkish by Gökhan MERCANOĞLU on February 5, 2007 and has been automatically translated into English and other languages using machine translation.