CIO Mandate: When AI Judgment Must Leave the CIO Seat

# CIO Mandate: When AI Judgment Must Leave the CIO Seat

The CIO mandate does not break on the title. It breaks when the CIO seat absorbs AI judgments that are no longer a systems preference: who may spend, which model may shape a commercial call, who may stop a use, and who records that the product, the price, or the process has changed.

Christian Pobbig and Beyond Chiefs work from Hamburg on AI Executive Search in DACH. This piece is not a title comparison and not a job description.

The mandate breaks on the four calls, not on the title

A CIO can hold architecture, integration, and run. That is orchestration. It becomes the wrong owner the moment the same ticket must decide whether AI changes the offer — and the Vorstand only sees the systems choice, not the judgment.

The test is not “CIO or CAIO.” The test is whether the judgment has left the seat and a name has recorded it before the organ decides.

Orchestration is not ownership

Platform sourcing, the integration path, and run-cost hygiene can stay in the CIO seat. Judgment must leave once it hits the commercial shape of the house.

Two public seat facts — patterns, not a Mittelstand template:

On 30 June 2025 Siemens appointed Vasi Philomin EVP and Head of Data & Artificial Intelligence; he reports to Peter Koerte, member of the Managing Board, CTO and CSO — not a CIO line (Siemens, 30 Jun 2025).

On 28 January 2025 SAP gave Philipp Herzig the worldwide CTO role in addition to CAIO; the extended board advises; the SAP Vorstand remains the Leitungsorgan (SAP, 28 Jan 2025). Adding a title does not move the final decision.

Four calls that are not a systems preference inside the CIO seat

BC frame (INFERENCE):

1. Spend — who may commit AI opex or capex that changes the offer — not platform run-cost hygiene.
2. Model — which model may shape a commercial call. Platform sourcing may stay with the CIO.
3. Override — who may stop a model, cut autonomy, or refuse a commercial use. This is not a security kill-switch and not incident command.
4. Commercial AI call — who records that the use changes the product, the price, or the process.

Title (CAIO, Head of AI, other) is not the test. The test is whether these four calls have a name.

A named owner records; the organ accepts or overrules in writing

The named AI-leadership owner records the judgment. Vorstand or Geschäftsführung accepts or overrules in writing. Without that writing, the judgment stays inside the seat that filtered it.

The Vorstand’s duty of care requires an adequate information basis (§ 93 (1) AktG). A commercial AI call that never leaves the CIO seat is an information-basis problem for the organ (INFERENCE) — not a statutory AI office and not a ban on a CIO line. The AI Act does not prescribe a CAIO; that is a boundary, not a literacy pack.

Boundary to the CISO judgment and the AI reporting line

The CISO spoke covers security exits: stop a release, override a live control, incident command, written risk acceptance. Override here is model, autonomy, and commercial use — not the kill-switch.

The AI reporting line says who reports AI facts to the Aufsichtsrat. This piece says who makes the four calls. Same organ logic, two contracts. A missing owner is not a fractional vacancy and not a search brief.

FAQ

### Must the CIO give up AI?

No. Architecture, integration, and run can stay. What must leave are the four calls, once they change the offer.

### Is “Head of AI under the CIO” enough?

No. A line under the CIO without a named judgment and a written organ decision does not close the break. Siemens shows a named owner under the Technik Vorstand — as a seat fact, not a template.

### Is this a CIO-versus-CAIO piece?

No. The title is not the test. The organ decides; someone must record the judgment first.

---

Draft. Not live without Christian. No service CTA.