Blue Tree Technology®

AI for business

Who Should Own AI: IT, Operations, or Leadership?

Published · Last reviewed · Next review due:

Leadership owns the business decision and accepted risk. That does not mean leadership writes the code. Operations owns the workflow; qualified implementers build or configure it; IT and security control access and technical safeguards; named people operate and review it.

"Everyone owns AI" is not an assignment. For each use case, identify a person accountable for the outcome and people responsible for the work. NIST's GOVERN 2.1-2.3 separates clear roles and training from executive responsibility for AI risk decisions. [1]

Assign authority and deliverables, not just departments

The following is our practical role model. A small business may combine roles, but should not leave them unnamed or allow consequential work to escape review because one person wears several hats.

RoleWhat ownership looks like
Executive sponsorApproves the purpose, budget, risk tolerance, and accountable business owner; authorizes major scope changes and accepts residual business risk.
Business-process ownerDefines how the work should function, success criteria, exceptions, required human decisions, and whether the result is fit for use.
Technical implementerConfigures the product or writes integrations; maintains versions, tests, documentation, and the technical means to stop or recover. May be an employee or contracted specialist.
IT/security ownerApproves identity and connector design, enforces access boundaries, reviews security testing, and coordinates technical incident response.
Legal/privacy or professional reviewerAdvises on applicable duties, contracts, sensitive data, records, and matters requiring qualified professional judgment.
Operating owner and reviewersMonitors work, handles exceptions and incidents, approves specified actions, and maintains day-to-day service and evidence.

This is not a requirement to hire six people. It is a requirement in our proposed operating model to make the decisions and handoffs explicit. NIST's actor descriptions distinguish design, development, deployment, and operation rather than making all of them a single task. [2]

Who actually programs it?

Some approved uses need only configuration, permissions, and a supervised process. Others require code, APIs, testing, and maintenance. Assign that work to someone qualified for the technical scope, whether internal staff or a contracted implementer.

Leadership can decide that reducing invoice-entry work is worthwhile without deciding how the integration parses a file. The process owner must still explain a correct invoice, and the implementer must demonstrate that the agreed workflow works within its boundaries. Buying a vendor product does not transfer all accountability to that vendor.

Give every workflow a short ownership record

Record the named sponsor, process owner, implementer, operator and deputy; approved data and actions; success and rejection criteria; human approvals; support arrangements; review date; and stop/restart authority.

Keep hosting accounts, integrations, documentation, and authorized recovery access under appropriate business control. Do not let a departing employee's personal account become the only way to run or stop the process.

For higher-impact workflows, separate building from acceptance and make the review independent enough to challenge assumptions. This is our risk-based implementation recommendation, not a claim that every business needs an identical committee.

Example: an invoice assistant, not an autonomous payment clerk

In this fictional example, leadership approves a limited trial. The controller owns the accounting process and defines acceptance tests. An implementer connects approved documents and builds draft entries. IT/security restricts access so the assistant cannot release payments or silently change bank details.

An authorized reviewer checks the proposed entry against original records and established payment-verification procedures. The operating owner monitors failed jobs, duplicates, exceptions, and cost. The sponsor decides whether the measured benefit and remaining risks justify expansion.

The controller does not have to code. The developer does not decide which invoice is legally payable. The AI does not grant itself authority. Restricted functions and permissions address the excessive-agency concerns described by OWASP. [3]

Decide who can stop it before something goes wrong

Give the operating and security owners pre-agreed authority to suspend unsafe processing. Identify who can revoke access and what manual fallback the business will use. Require the right business and technical sign-offs before restarting; do not wait for an unavailable executive merely to stop preventable harm.

Avoid treating "human in the loop" as a job description. Specify which person reviews which decision, what evidence they see, when they must escalate, and what happens when they are absent.

Ownership continues after launch

Review correction effort, failure patterns, consequential actions, access, cost, and changing provider terms. Maintain tests and retest affected behavior after a material change. NCSC treats monitoring and maintenance as operating responsibilities, not optional work after deployment. [4]

As a starting practice, review an active pilot weekly and established arrangements monthly, adjusted to risk. Train staff on their actual responsibilities and how to report mistakes. Blue Tree Technology® can help define the technical responsibilities in an agreed scope; business leadership remains responsible for the use it authorizes.

Approve an owner, implementer, operator, and stop process together. Approving a software subscription alone does not establish AI governance.

Sources and further reading

[1] NIST AI RMF 1.0: Core, especially GOVERN 2.1-2.3

[2] NIST AI RMF: Appendix A - AI actor tasks

[3] OWASP: Excessive Agency (2025 risk guidance)

[4] NCSC: Secure operation and maintenance of AI systems

Back to the Knowledge Hub

More in this topic

Discuss your business technology needs

Review your priorities with Blue Tree Technology®.

Schedule a discovery call