Language: English

Community post

Who Owns AI? A Practical Operating Model for Growing Companies

By · Published · 2 min read

Editorial standards and corrections

Clarify executive sponsorship, business ownership, technical delivery, risk oversight, and employee responsibility without creating bureaucracy.

AI work stalls when everyone is interested but nobody can approve, operate, or stop it. An operating model assigns decisions to roles before an incident or budget dispute exposes the gap. This decision connects to Build an AI Strategy That Starts With Business Value and Turn Company Priorities Into an AI Opportunity Portfolio, which provide the strategic direction and portfolio context. Use this four-part leadership framework Executive sponsor — Connect investment to strategy and resolve cross-functional barriers. Business owner — Own the outcome, workflow, adoption, and operating performance. Delivery owner — Own architecture, integration, testing, monitoring, and technical recovery. Risk and user voices — Set controls and represent the people affected by the system. A practical decision example A customer-service assistant has a COO sponsor, service director as business owner, technology lead as delivery owner, privacy and security reviewers, and frontline representatives. The vendor is not treated as the owner of the business outcome. This is a hypothetical example; use your own baseline, constraints, and evidence. Evidence, governance, and responsible use Use the NIST AI Risk Management Framework to connect the initiative to governance, context, measurement, and ongoing management. The companion NIST AI RMF Playbook turns those functions into questions leaders can assign and review. The GAO AI Accountability Framework is useful for examining governance, data, performance, and monitoring across the system life cycle. Compare the plan with the OECD AI Principles, particularly transparency, robustness, accountability, and respect for people affected by the system. For generative AI, review the NIST Generative AI Profile and test representative cases using OpenAI’s evaluation guidance. Use the OWASP Top 10 for LLM Applications to discuss application threats before a model can access sensitive information or take actions. Check performance statements against the FTC’s guidance on AI claims, and review information handling with the FTC’s privacy and security resources. For a broader organizational management approach, study the ISO/IEC 42001 overview. Take this to the next leadership meeting Make a decision-rights table for funding, data approval, launch, model changes, incident response, customer communication, and shutdown. Put one accountable role in every row. Record the owner, evidence source, decision date, and what would cause the company to stop. The goal is not to make the document look complete. The goal is to make the next decision explicit, measurable, and accountable. Continue with Build a Cross-Functional AI Team Without Creating Another Committee. Use Run a Quarterly AI Portfolio Review: Keep, Fix, Scale, or Stop to revisit the decision with current evidence.

About the author

I help businesses replace manual processes with practical AI systems—and show what changed, what it cost, and what results improved.

Comments (0)

Loading comments…

Keep exploring

All articles