Back to Overview
Executive Process Ownership & AI Transformation

What a Process Costs When Nobody Really Owns It

Rework, waiting and status chasing become costly when nobody leads an end-to-end process with clear decision rights. The Fassbender Process Ownership Contract connects outcomes, evidence, governance and AI readiness in one manageable system.

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 mechanismWhat happens day to dayWhat the baseline should examine
ReworkInformation is completed, cases are corrected or checked again.Returns, loops, active rework time, first-pass completion.
Waiting timeCases sit ahead of approvals, handovers or unresolved decisions.End-to-end lead time, time spent waiting, number of handovers.
Queries and status chasingEmployees look for the latest status, the right file or the responsible decision-maker.Status enquiries, research time, missing mandatory information.
Exceptions and reversionsSpecial cases leave the standard route and return without a clear rule.Exception types, reversions, escalation duration, lead time by case type.
Information reconstructionData is entered, verified or reconstructed from different sources more than once.Duplicate entries, data corrections, checking effort, breaks between systems.
Delayed business outcomesA 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.

RoleOngoing remitTypically decidesDoes not decide alone
Process OwnerLeads 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 leaderLeads 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 leaderDelivers a time-limited change.Project plan, dependencies, risks and deliverables within the project remit.Ongoing operational accountability after the project closes.
Executive SponsorGives 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-offThe wrong simplificationManagement decision
Speed versus controlEvery approval is bureaucracy.Define risk classes and determine which cases are standardised, checked or escalated.
Customer commitment versus operational feasibilitySales always decides in the customer's interest.Set binding limits for commitments, an exception process and feedback into the standard.
Consistent standard versus necessary variationEvery variation is an error.Separate legitimate case types from unresolved exceptions and create learning loops.
Local utilisation versus end-to-end throughputEvery 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.

An integrated solution system, not another process document

For this, I use the Fassbender Process Ownership Contract. It is a working logic derived from evidence and consulting practice, not an externally validated standard. Its purpose is straightforward: before any significant change to a process, data or automation, it must be clear which outcome is being led and who carries which decision.

Component of the Fassbender Process Ownership ContractBinding clarification
1. OutcomeWhich customer or business outcome counts and which adverse effects must not increase?
2. Process boundaryWhat are the initial trigger, successful completion, case types, pauses and cancellations?
3. Named OwnerWho is permanently accountable for the outcome, flow, exceptions and improvement?
4. Decision rightsWhat does the Owner decide, what does the functional leader decide and what does the Sponsor decide?
5. Evidence and baselineWhich data, definitions, sources and cost assumptions show the starting position?
6. Review and escalationWhat is the review cadence, which threshold triggers which escalation and who then decides?

The Contract is useful only if it does not stand alone. It therefore connects ownership with the six layers of the Fassbender AI Operating System. This Operating System is not a marketing slogan. It is a management system that prevents a process problem from being reduced to a tool, an organisation chart or a single measure.

AI Operating System layerContribution to process ownership
Strategy & ValueDefines the outcome, value hypothesis, customer outcome and balancing measure.
Processes & DecisionsSets the process boundary, standard, exception route, decision rights and escalation.
Data & KnowledgeDetermines the case ID, event definition, data source, quality check and knowledge base for exceptions.
Technology & IntegrationClarifies system boundaries, logging, integration and the appropriate degree of technical support.
Governance & EvaluationEstablishes the review cadence, measures sheet, change log, risk and control plan.
People & Operating ModelSecures time, capability, data access and backing for the Owner and participating functions.

Fact: Outcome, process and balancing measures should be considered together so that an improvement does not merely shift a local measure. 12 Limit of the evidence: This does not imply a universal target value. Start, end, case types and rework must be clearly defined and versioned before any comparison.

What process mining can do and what it cannot

Process mining can be a valuable diagnostic aid. It examines digitally recorded event logs to make observed case paths, handovers, variations and timing patterns visible. Conformance checking can compare those log data with a reference model. 8 9

The limitation is material: process mining shows only what has been captured in the selected digital log. It proves neither the cause of a pattern, nor fault, nor the financial effect. Nor does it designate a Process Owner. Missing events, inconsistent activity names and unclear timestamps can distort the picture. The Process Owner should therefore first verify data provenance and log quality with functional teams and data owners before management decides. 9

Only then: AI and automation

AI or automation comes at the end of this logic, not at the beginning. It can support a clear step, prepare information, apply rules or prioritise a case. Its purpose must follow from the defined outcome. Before a pilot, input quality, human override, monitoring, incident response and a manual fallback route should be established.

Fact: The NIST AI RMF and its GenAI Profile identify documented roles, ongoing monitoring, feedback, human intervention, incident response and change management as relevant elements of AI risk management. 10 11 Limit of the evidence: NIST is a voluntary US framework. Obligations under the EU AI Act cannot be applied indiscriminately to every tool or use case either. The specific legal and risk assessment depends on the context.

A realistic 30/60/90-day path

The starting point is exactly one prioritised process, not an organisation-wide redesign. The path first creates the ability to decide, a baseline and a controlled test. It guarantees neither savings nor a sustained earnings effect.

PeriodTestable outputs and activitiesOwner and management gate
Days 1 to 30Draft Contract, named Owner and Sponsor, process boundary, case types, system and data inventory, measures sheet with definitions and an initial overview of risks and exceptions.The Owner leads, the Data Owner validates data and Finance tests the costing logic. Day 30 Sponsor review: confirm the boundary, mandate, data quality and two or three problem hypotheses or redraw the process scope.
Days 31 to 60Current-state flow from event data or case files, segmented waiting time and reversions, validated root-cause interviews, baseline for time, rework, customer outcome and balancing measure and a draft standard and escalation route.The Owner leads, functional leaders confirm causes and the Sponsor decides on no more than two action packages. Day 60 gate: no automation approval without robust data, an Owner mandate and a tested fallback route.
Days 61 to 90Prioritised handover and exception rules in operation, training, an active change and exception log, review cadence and, where appropriate, a limited technology or automation pilot with stop criteria.The Owner is accountable for operations and the Sponsor resolves escalations. Day 90 CEO review: stabilise, selectively extend, adjust or stop; reporting separates measured values, open assumptions and adverse effects.

The baseline remains visible throughout. It includes, at a minimum, volume, lead time, returns or rework, a customer or business effect and a balancing measure such as complaints or overload indicators. Where measurement is missing, this is not concealed; it is documented as a management risk. Seasonality, case mix and delayed customer effects can influence any before-and-after comparison. A 90-day path is therefore a basis for better decisions, not a guarantee of results.

Frequently asked questions

Does every process need its own Owner?

No. Priority belongs to business-critical, cross-functional value flows with material handovers, exceptions or customer consequences. A title for every secondary process creates bureaucracy rather than clarity.

Can a functional leader also be the Process Owner?

Yes, provided the person genuinely has the mandate, time, data access and authority over the full flow. The role matters, not the job title.

Is a RACI matrix sufficient?

It can make responsibilities visible. It does not replace an outcome, decision rights, a baseline and a binding escalation route. Without these elements, it often remains a snapshot.

Must process mining be introduced first?

No. Case files, existing timestamps and structured conversations can be sufficient to begin. Process mining is useful when digital traces are sufficiently complete and are intended to answer a specific diagnostic question.

The next sensible step

If your leadership team cannot clearly answer who owns the end outcome for an important process, who decides which exception and how the actual starting position is measured, the first gap is clarity, not necessarily technology.

An Executive AI Diagnostic can provide an independent management diagnostic of that starting position, value potential, risks and the next 90 days. Where required for the decision, it produces an AI Operating System baseline, an Opportunity & Risk Map, a Top-3 competitive comparison and 90-day orientation. It is neither a mandatory sales sequence nor an ROI promise. It is a robust basis for deciding whether change is needed and what should change.

If you would like to assess a critical value flow with clear eyes, a confidential initial conversation is worthwhile. The first question is not which technology should be introduced. It is: Which outcome can nobody in your organisation be allowed to lose between departments?

Sources

Related Insights

Strategic Advisory

From insight to a decision you can stand behind.

We translate AI potential into clear architecture, measurable priorities and an executable roadmap for your organization.