Monday morning, 8:15am: an important customer order has been sitting between Sales, Operations and Finance for five days. Sales is waiting for approval, Operations for complete information and Finance for clarity on who may authorise an exception. In the status meeting, each leader reports accurately on their own area. Yet nobody can say with confidence when the order will be completed, what is causing the delay or who decides the trade-off. The customer waits, employees search for information and management becomes the escalation point for routine questions. This costs more than time. It puts margin, delivery capability and trust at risk. The key insight is this: a cross-functional process becomes manageable when one person is permanently accountable for its outcome and has genuine decision rights.
The situation: many participants, nobody accountable for the outcome
This situation is not unusual in growing mid-market companies. Processes are created with good intentions: a new control step, a new system, a specialist role. Each function optimises its own remit. Sales protects the customer relationship, Operations execution, Finance commercial control and IT stability. What is often missing is the authority that leads the entire flow from its trigger through to the business outcome.
Fact: ISO recommends assigning responsibility and authority for processes. APQC describes end-to-end processes as cross-functional flows that include every step required for a particular outcome and assigns the Business Process Owner responsibility for end-to-end success. 1 2 3
The consequence: the cost sits between departments
An unowned process often has no visible budget problem. Its cost is distributed across many teams and appears as an individual query, correction, email or waiting period. Locally, every unit can appear productive. For the customer and the profit and loss account, however, the entire journey matters.
| Hidden cost mechanism | What happens day to day | What the baseline should examine |
|---|---|---|
| Rework | Information is completed, cases are corrected or checked again. | Returns, loops, active rework time, first-pass completion. |
| Waiting time | Cases sit ahead of approvals, handovers or unresolved decisions. | End-to-end lead time, time spent waiting, number of handovers. |
| Queries and status chasing | Employees look for the latest status, the right file or the responsible decision-maker. | Status enquiries, research time, missing mandatory information. |
| Exceptions and reversions | Special cases leave the standard route and return without a clear rule. | Exception types, reversions, escalation duration, lead time by case type. |
| Information reconstruction | Data is entered, verified or reconstructed from different sources more than once. | Duplicate entries, data corrections, checking effort, breaks between systems. |
| Delayed business outcomes | A customer waits, an order is delayed or a risk remains open for longer. | Customer outcome, complaints, cancellations, inventory or risk indicators. |
Fact: Quality problems, non-seamless handovers and delays can trigger rework, workarounds, status chasing, queries and complaints. 4 Studies of event logs also show an association between case paths involving exceptions and longer lead times. 5 Fragmented information can cause duplicate entry, searching, verification and rework. 6
Limit of the evidence: These sources establish cost mechanisms, not a standard cost ratio for German mid-market companies or a guaranteed benefit from creating a new role. A handover is not automatically wasteful either. Specialist controls and approvals may be necessary.
Management inference: Where consequential work repeatedly occurs at the same handovers, exceptions or data gaps, the issue is often not employees' willingness to contribute but the absence of a binding end-to-end decision. This is a testable hypothesis, not a diagnosis at a distance. The scale of the cost must be determined for each process using its own case, time and cost data. UK government costing guidance identifies demand, processing time, rework, complexity and service standards as relevant cost drivers. It does not provide a corporate benchmark. 7
The clear answer: ownership is a mandate, not a box on the organisation chart
End-to-end process ownership is the permanently assigned accountability of a named person for a clearly defined customer or business outcome, from the initial trigger to successful completion. That person is accountable for the objective, measures, handovers, risks, exceptions and improvement and holds documented decision and escalation rights within defined boundaries.
This is a practical management definition, not a scientifically validated universal standard. It translates the ISO- and APQC-supported principle of responsibility and authority into an operating model. 1 3
The decisive issue is not the job title. A Process Owner without access to data, the right to decide on standards or an escalation route is simply another co-ordinator. Ownership without decision rights is a title, not the ability to steer.
| Role | Ongoing remit | Typically decides | Does not decide alone |
|---|---|---|---|
| Process Owner | Leads the outcome, measures, handovers, exceptions and improvement of a defined end-to-end process. | Standards within the mandate, prioritisation of process issues, escalation and corrective action. | Line management of all participants, strategic budget decisions outside the mandate. |
| Functional leader | Leads the people, capability, capacity, quality and risks of their own function. | Deployment and development of their own resources, functional requirements. | The overall process against other functional objectives, unless they hold the relevant mandate. |
| Project leader | Delivers a time-limited change. | Project plan, dependencies, risks and deliverables within the project remit. | Ongoing operational accountability after the project closes. |
| Executive Sponsor | Gives legitimacy to priorities, resources and decisions above the Owner's boundary. | Trade-offs, escalations and approvals that exceed the mandate. | The daily management of every individual case. |
The underlying cause: local objectives prevail over the end-to-end flow
The visible symptoms are slower cases, recurring escalations and frustrated customers. The underlying cause often runs deeper: the organisation has structured its functions responsibly, but has not established the value flow as a system that can be led. Five things are then missing at once: a clear process boundary, an outcome, an Owner mandate, a shared view of the data and a decision route for deviations.
In my experience, the first response often fails because of an understandable reflex: the executive team commissions a process project, draws a new process map or implements a tool. That can help. It does not, however, resolve who decides after the project when Sales demands speed, Finance requires a control and Operations rejects an exception. A well-designed target process without binding conflict resolution will once again be interpreted locally in day-to-day operations.
The management decision and its trade-offs
The executive team does not need to decide every operational exception itself. It does, however, need to decide which outcome takes precedence, who may decide within which boundaries and when escalation becomes mandatory. This matters particularly where legitimate objectives conflict.
| Trade-off | The wrong simplification | Management decision |
|---|---|---|
| Speed versus control | Every approval is bureaucracy. | Define risk classes and determine which cases are standardised, checked or escalated. |
| Customer commitment versus operational feasibility | Sales always decides in the customer's interest. | Set binding limits for commitments, an exception process and feedback into the standard. |
| Consistent standard versus necessary variation | Every variation is an error. | Separate legitimate case types from unresolved exceptions and create learning loops. |
| Local utilisation versus end-to-end throughput | Every department maximises its own measure. | Use a shared outcome and balancing set alongside local measures. |
Fassbender recommendation: The CEO or COO appoints a Process Owner and an Executive Sponsor for a prioritised value flow. The Owner mandate is defined in writing, but made effective. It includes, at a minimum, decision rights over standards, exception routes, measurement logic and escalation. This is not a call to disempower the line organisation. On the contrary, functional leaders remain accountable for their people, functional expertise and capacity. The Owner connects this accountability to the overall outcome.