Appointing a Chief AI Officer is the easier decision

Suppose a Chief AI Officer is appointed with a mandate and a budget held outside the operating units. A quarter in, the function can plausibly have a ranked list of candidate use cases and a position on which decisions a model should be allowed to make. That is what a new unit with one subject and a short path to the board is built to produce. Then a conclusion has to reach an operating unit whose targets were set before the function existed. The appointment letter says what the new executive owns. Who carries a finding across that boundary, and what happens to the receiving unit’s numbers while it does, is left to goodwill.

The title has gone from unusual to expected, and the commentary runs two ways. Either artificial intelligence is consequential enough to need a seat of its own, or the title is decoration and the work belongs to whoever already owns technology. Both positions argue about whether the unit should exist, and leave aside who would carry its conclusions into the operating units.

The case for the appointment is strong. A capability held fractionally across several functions gets whatever attention is left after each function’s targets. The appointment settles the part that can be settled by naming someone, and that part is real: a named executive with a budget turns a shared aspiration into somebody’s actual job, and often that is the right call.

Differentiation and what spans it

Paul Lawrence and Jay Lorsch published a comparative field study in 1967 covering ten firms across three industries, chosen for how much uncertainty each faced, from plastics at the volatile end through food to containers at the stable one. Sales, research and production were examined separately inside each firm. Their finding was that departments in one company become structurally different, and have to: formal structure, goal orientation, time orientation and interpersonal orientation all diverge in response to the sub-environment each department deals with. A research group on a long horizon and a production group on a tight schedule have each adapted to the work in front of them.

The study’s second half concerns what it costs to hold those differences together. The more genuinely different two units become, the more work it takes to get them to agree on anything, and that work has to be resourced. Lawrence and Lorsch scored each firm on both dimensions and set that against its economic performance. The relation that matters for an appointment decision is between the two scores: a firm that pushed one of them up without the other underperformed firms whose two scores matched, at whatever level they matched.

That second failure is what an appointment announcement usually leaves open. A Chief AI Officer is a differentiation decision, and the environment usually warrants it, since the function faces a supplier market and a technical horizon that an operating unit does not. An announcement says what the role owns. What spans the gap is a separate line. Coordination capacity appears on no revenue line, so nothing in a budget review argues for it on its own behalf. Three Horizons, among the models on our Insights page, gives a future-facing unit its own allocation and says nothing about what connects it to the unit earning this year’s revenue.

What a channel cost Siemens

Siemens built an integrating mechanism of this kind, and the public record of it is unusually full. Its telecoms division had sold into national monopolies, deregulation from the mid-1990s removed that model, and the division found itself bidding complex solutions in more than a hundred countries with no way for a team in one market to reach what a team in another had already worked out. ShareNet, built in 1998, took in how a bid had been structured and what the competitive picture looked like, in place of finished collateral, and it let staff post live questions from live deals. Money was attached to it as well: a scheme in fiscal 2000 paid local division heads for business generated through reuse above a defined threshold. Usage climbed while the payments ran, and fell back after they stopped.

The channel also changed where an answer came from, and some local executives objected to staff reaching past them for it. Whoever funds a coordination line is also funding that objection, and it arrives from people with their own reporting lines to protect.

Scope and the two mandates

A central function can own the definitions and the interfaces between units: what counts as a deployed use case, and what a model must clear before touching a customer decision. The method belongs where the work is done, since nobody at the center has watched it performed. A prescribed workflow that an operating unit cannot complete at its own tempo gets routed around, and the workaround is not visible centrally. Pilots that work and rollouts that stall are that gap from lower down, described here before as a handoff with no owner.

Which gives the coordination machinery a specific job: carrying a negative result up out of a unit with every incentive to keep quiet. A meta-analysis published in 2017, aggregating 136 independent samples covering more than 22,000 individuals, found that a shared belief that candor is safe predicts whether a team’s problems reach the people above it, and tracks learning behavior in turn. A central AI function that hears only about successful deployments has a reporting problem no further headcount at the center will touch.

So there is a decision for whoever drafts the mandate, and two shapes it can take. The first keeps the new function advisory: it owns the definitions and the outcome targets and evaluates what the units bring it, while the method stays with them. That holds where the units are already capable and the scarce thing is a common standard. The second funds the coordination explicitly: named people inside the receiving units whose objectives include adoption, and a route for reporting a failure that does not end someone’s year. Siemens paid for adoption directly and lost it when the payment stopped, so those objectives have to survive the first budget cycle that questions them. The second shape costs more and takes longer to approve, and where the units already agree on their definitions the first does the same work for less. Everywhere else it is the one worth arguing for, and the mandate gets drafted before anyone finds out which. Where the coordination line is left out of it, the function’s conclusions pile up as a queue of unmade decisions above the people who would have had to act on them.