A practical method for settling ownership conflicts during an ISO rollout without allowing departmental boundaries to weaken controls or delay decisions.
Ownership disputes are seldom arguments about a box on an organization chart. They emerge when a process crosses functional boundaries, the outcome is shared, and nobody has authority to resolve a difficult exception. During an ISO rollout these disagreements often surface at supplier onboarding, customer complaints, engineering changes, contractor work or local site deployment. The answer is not to assign every task to a central ISO coordinator. It is to make one accountable process owner visible, protect specialist control responsibilities and establish a decision route for unresolved interfaces.
01Name the disputed outcome before debating titles
Begin with the result that is not reliably achieved: A late supplier approval, an unsigned release, an unclosed complaint or inconsistent site data. Ask which decision was missing when the control failed, what exposure followed and which existing manager had access to the information. A vague dispute over who owns quality becomes clearer when the team examines an actual transaction and the moment authority was needed.
Separate ownership of the end to end result from completion of individual activities. Procurement may collect supplier records while Engineering confirms technical suitability and Operations authorizes use. The accountable owner needs enough authority to ensure these contributions combine into a controlled outcome. Recording only the person who uploads a document confuses evidence custody with accountability.
02Distinguish accountability, execution and expert authority
A useful ownership model differentiates the person accountable for process effectiveness, the people executing steps, specialists setting mandatory controls and the executive who can settle competing priorities. A RACI chart can expose ambiguity, but initials alone do not grant decision rights. Confirm the actual permissions to change criteria, assign capacity, reject an exception and stop an unsafe or nonconforming release.
For an outsourced calibration activity, the asset owner may remain accountable for the operational outcome while a metrology specialist defines technical acceptance and a contractor performs the work. The contract manager may administer invoices without owning equipment fitness. If a dispute persists, map the full decision sequence and label its authority points, not only its departmental handoffs.
A practical ownership workshop should start with a swimlane of the real process and end with a statement that can be tested. Ask each manager to identify the decisions they currently make, the evidence they receive and what they do when another function provides unacceptable input. Some responsibilities are genuinely concurrent: An engineering authority must approve a technical criterion while a supply manager manages delivery. The governance defect arises when nobody has an end to end duty to reconcile these contributions before product or service release. The facilitator should avoid forcing all specialist decisions into the hands of one general manager merely to simplify a chart.
03Use a real event as the arbitration case
Choose one representative case rather than arguing hypothetically. Trace the input, approval, handover, acceptance record and resulting customer or compliance obligation. If several teams claim a different owner, test each proposal against three questions: Can this person direct the process, obtain reliable data and intervene when the result is unacceptable? A named owner without these abilities is only a nominal contact.
In an illustrative manufacturing case, a supplier substitution is discovered after production scheduling. Purchasing believes Engineering should approve the substitution; Engineering believes Operations should confirm its effect. The resolution assigns technical acceptance to Engineering, scheduling and containment to Operations, and end to end supplier change accountability to a defined process owner. All three permissions and their evidence are recorded.
Decision evidence matrix
Use the criteria below as a practical check, not as a numerical certification scoring system.
| Decision / Gate | Test of adequacy | Evidence |
|---|---|---|
| Decision to settle | Identify the affected output and obligation | Process exception record |
| Assign accountability | Check capacity to direct the end to end outcome | Approved authority map |
| Maintain interim control | Limit exposure while ownership is disputed | Temporary disposition and deadline |
| Verify resolution | Sample the next complete transaction | Effectiveness review record |
04Escalate the decision, not the interpersonal conflict
Escalation should present the consequence and options, rather than asking senior leaders to settle personalities. A useful one page escalation identifies the contested decision, applicable obligation, interim safeguard, preferred accountable owner, consulted specialists and the deadline. The sponsor should approve an operating rule that works on the next transaction, not just an organizational title.
Set a temporary control if operations must continue before a permanent assignment is agreed. Restrict the affected change, require an additional technical check or postpone release where risk warrants it. Avoid informal approval by email that cannot be traced to a competent person or acceptance criterion. A good escalation decision identifies what will happen if the same condition recurs on a weekend shift or at another site.
A robust decision rights register records more than a role name. It identifies the affected process, permission, threshold, delegated substitute, required consultation and record location. Consider a purchase above an approved supplier limit: Does the buyer have permission to proceed, or is technical release required? Who can grant an exceptional approval during the primary owner's absence? Are different sites permitted to vary the rule? These questions turn an argument over departmental identity into a manageable set of operational authorities. When the register conflicts with software permissions, the project must change the configuration or revise the rule before claiming completion.
05Confirm authority at interfaces and sites
Local variations often reintroduce ownership disputes. The corporate process designer may own common rules, but a site manager may control staffing and emergency actions. Record which approvals are central, which are delegated and which require specialist concurrence. Where legal obligations differ by location, an enterprise wide title must not obscure the locally responsible person.
Test the model through process walk throughs with people who perform the work. Ask them who can authorize exceptions, which system records the decision, what happens in the decision maker’s absence and how conflicting customer deadlines are handled. A procedure that describes a smooth handoff but cannot explain exception handling leaves the true dispute unresolved.
06Capture the resolution in working controls
Translate the decision into a process map, authority matrix, approved procedure or workflow configuration. Identify the effective date, delegated substitutes, required evidence and approval thresholds. Train the affected teams using a realistic example; sending a revised policy link does not establish that the new rule will be applied during a production delay.
Maintain a small decision record that states why the owner was selected and which boundary conditions apply. The record helps resolve later disagreements when organizational structure changes. It also provides a rational basis for internal audit: Reviewers can test the actual decision path rather than interpreting an outdated reporting chart.
Ownership arbitration should also examine incentives. A warehouse leader evaluated only on shipment speed may resist an additional release control, while the quality function is evaluated on defects but cannot change staffing. The sponsor's decision needs to reconcile these competing outcomes, not just repeat the mandate to cooperate. Agree a balanced measure for correct and timely release, define the maximum acceptable risk and review a sample of real transactions. Where a team reasonably disputes a deadline or acceptance criterion, the process owner should seek a documented technical decision rather than exerting informal pressure on the recorder of the evidence.
07Verify the next transaction and close the dispute
A dispute is resolved when staff apply the assigned ownership reliably, not when a steering meeting declares it closed. Sample a new transaction from initiation through acceptance. Interview the accountable owner, the technical specialist and an executor separately to check that they describe compatible decision rights. Inspect approvals for timeliness, appropriate competence and response to exceptions.
Review a measurable signal, such as rework caused by delayed approval or repeat late handovers, but do not treat a single successful sample as proof of permanent control. If confusion reappears, analyze whether the failure arises from access rights, inconsistent training, inadequate capacity or a genuinely unclear decision boundary.
- Decision to settle: Identify the affected output and obligation, Process exception record.
- Assign accountability: Check capacity to direct the end to end outcome, Approved authority map.
- Maintain interim control: Limit exposure while ownership is disputed, Temporary disposition and deadline.
08Keep the model stable through change
As departments reorganize, vendors change and responsibilities shift, revisit the ownership map as part of change control. Transfer open actions and outstanding risks explicitly. New managers should receive both the process outcomes they own and the controls they are expected to enforce. Otherwise the organization gains a fresh organization chart while inheriting the same unresolved interface.
A sound rollout can tolerate shared execution; it cannot tolerate undefined authority over material decisions. The durable result is a clear end to end owner, transparent specialist acceptance requirements and an escalation route that protects operational outcomes when priorities compete.
After implementing the resolution, review the next several applicable events to detect whether the agreed rights survive urgency and staff absence. Note delays caused by permissions, unfamiliarity with the new path or disagreement over what evidence is sufficient. Correct each specific barrier. The governance model is reliable when people can describe the same approval rule independently and a subsequent reviewer can reconstruct the decision from records. The target is not universal agreement about every management title; it is consistent, authorized operation of an important process despite legitimate functional differences.
Decision checkpoint
Confirm the accountable decision, evidence expected and treatment of any open exposure before the next milestone. Check capacity to direct the end to end outcome.
Explore implementation resources
Editable planning, control and evidence tools aligned with the management topics discussed in this article.