Skip to main content

Who owns AI in your organization?

AI is the new shiny toy in many organizations, promising innovation, efficiency, and a competitive edge. But with great potential comes great complexity—and in many cases, inter-departmental turf wars over who should "own" AI. IT wants control for its infrastructure expertise, Data Science claims it as their domain due to their deep knowledge of models and analytics, and business units see it as a tool to drive their specific goals.

So, who really owns AI?

I think that’s the wrong question to ask….

AI’s transformative potential means it touches almost every part of an organization. Each department has valid reasons for their claim, but this fragmented approach can lead to inefficiencies, duplicated efforts, and missed opportunities.

AI is not a standalone tool that fits neatly into one department. In my opinion it’s a cross-functional enabler that thrives on collaboration. Framing AI as something to be "owned" misses its broader organizational value. Instead, organizations should think about shared stewardship—a model where different departments contribute to and benefit from AI initiatives.

AI is a team sport

One way to resolve this conflict is by establishing a governance structure that fosters collaboration. For example, creating an AI Center of Excellence (CoE) can centralize strategy while decentralizing execution.

Instead of asking, “Who owns AI?” we should ask, “How can we work together to maximize its value?” Ownership battles can hinder progress, while collaboration drives innovation. By embracing shared stewardship, organizations can unlock AI’s full potential and ensure it becomes a transformative force for all.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...