What should you do when no one knows who owns a business process?
How to establish process ownership when work spans several teams and everyone owns a fragment of it.
The short answer
Map the process end to end first, then assign a single accountable owner for the outcome — separately from the people who perform individual steps. Ownership means authority to change how the work is done, to arbitrate exceptions, and to approve supporting technology. Until someone holds that authority, improvement efforts will keep dissolving at department boundaries.
What is happening
Everyone owns part of the process. Nobody owns the outcome. Each team optimizes its own segment, handoffs accumulate delay and rework, and when the result is poor there is no one to hold accountable — only a chain of people who each did their part correctly.
Why it happens
- Organizations are structured by function; work flows across functions.
- The process grew rather than being designed.
- The original owner left and ownership was never formally reassigned.
- Owning a cross-functional process carries accountability without authority, so no one volunteers.
What to do first
- Map the process as it actually runs, including the informal steps and the exceptions.
- Identify each handoff and what is lost or re-entered at it.
- Name the outcome the process exists to produce, and who feels it when it fails.
- Assign one accountable owner for that outcome, with explicit authority: change the workflow, arbitrate exceptions, approve tooling, and set the measures.
- Define step owners underneath, and document the decision rights between them.
- Set a small number of measures the owner reports on.
What not to do
- Do not assign ownership without authority — it produces a coordinator, not an owner.
- Do not create a committee to own it.
- Do not document the ideal process and skip the exceptions; the exceptions are where the work actually goes.
- Do not automate before ownership is settled.
Questions to ask
- Who can change how this work is done without asking anyone?
- Who hears about it first when the outcome is wrong?
- Where does work wait, and who is it waiting for?
- What percentage of cases follow the documented path?
Warning signs
- Improvement initiatives stall at a department boundary.
- Each team's metrics look healthy while the end-to-end result does not.
- Escalations are routed by relationship rather than by role.
When internal teams can handle it
When an executive can simply assign the ownership and make it stick.
When outside help may be appropriate
When ownership is contested, when the process spans functions with different leadership, or when prior attempts to assign it have not held.
Relevant capability
Operations & Process Transformation
If this describes your situation, tell us what's happening and what you've already tried. We'll help determine what the problem requires.
Related resources
This resource is general educational information about organizational, technology, and governance practice. It is not legal, regulatory, forensic, or professional advice, and it does not account for the specific circumstances of any organization.