The Chief Digital Officer: The Seat That Owns the Customer

Chief digital officer carries 2,900 monthly UK searches at the lowest measurable competitive difficulty JOH's keyword tracking has found for a term this size (DataForSEO, September 2026), and the Gulf's own pattern behind that search interest is unusually consistent: the seat is created to build a digital channel and, within a small number of years, finds itself arbitrating a boundary the group never actually settled at the point of hire, between an information technology function that owns the systems estate and an operating business that has always owned the customer relationship. JOH's reading of its own technology and transformation search mandates across the region is that this unresolved boundary, not a shortfall in any individual appointee's capability, explains why the seat carries the shortest average tenure of any senior technology title the firm places into Gulf groups.

Two seats, one systems estate

A chief digital officer and a chief information officer, in a technology and digital organisation or any Gulf platform now building a comparable capability, both work in technology, and a Gulf board that treats the two mandates as points on a single spectrum rather than genuinely separate jobs is, in JOH's reading, the single most common source of confusion in the region's technology hiring. The chief information officer owns the internal systems estate the organisation depends on to run: enterprise applications, infrastructure, IT governance, and increasingly cybersecurity oversight. The chief digital officer is scoped toward the outward-facing side of the same organisation: digital channels, product, and elements of the business model the group builds on top of what it already runs. The separately benchmarked internal-systems seat, priced apart from the customer-facing mandate that sits beside it, makes the same distinction from the pricing side: the market pays for the two mandates differently because it recognises them as genuinely different jobs, even where a Gulf group's own organisation chart still uses the two titles almost interchangeably.

A chief information officer is judged on whether the systems stay up. A chief digital officer is judged on whether the customer noticed. Those are different jobs, and a Gulf group that hires for one while writing the brief for the other gets a short, difficult tenure almost by design.

Why the seat was built to arbitrate, not just to build

JOH's mandate experience across the region's technology searches finds a specific, repeated sequence behind most chief digital officer appointments. A shareholder or chief executive has seen a digital capability succeed elsewhere, commissions a channel or product build, and hires a chief digital officer to lead it, without first resolving what happens to the customer relationship if the channel actually works. Early in the mandate, while the digital effort is small and unproven, this ambiguity costs nothing; the operating business units tolerate the new function because it has not yet touched anything they consider theirs. The difficulty arrives precisely at the point of success, when the digital channel starts generating a meaningful share of revenue, transaction volume or customer contact, and the operating business that has always owned that relationship discovers a function it once treated as a side project is now a genuine claim on territory it never agreed to cede.

Farooq Shaikh's account of building LogiPoint's digital transformation under Vision 2030 is a useful companion listen on precisely this dynamic from the operating side of a large-scale digital build: the technical delivery of a digital or logistics platform is rarely the harder half of the mandate; negotiating who inside the existing organisation actually owns the outcome once the platform starts working is. JOH's engagement building the chief technology officer seat for a GCC universal bank illustrates the same discipline applied earlier in a mandate's life: naming, before the search opened, exactly which existing business lines the new seat would need standing to influence, rather than leaving that boundary to be negotiated informally once the appointee was already in the building.

The boundary against the wider technology family

The chief digital officer now sits inside a technology and digital family that has grown to five distinct titles on a typical Gulf platform's senior organisation chart: the chief information officer, the chief data officer, the chief technology officer, the seat JOH has separately described as the AI-titled role that does not yet know its own name, and this one. The most acute collision, in JOH's reading, sits with the chief data officer, because the two titles share an initialism and a genuine overlap in subject matter: a chief digital officer building a customer-facing product depends on the same data the chief data officer is separately mandated to govern, and a board that has not stated plainly which seat owns product decisions and which owns data governance and quality is setting both appointees up to negotiate that boundary informally, in real time, under the pressure of a live launch.

JOH's forthcoming reading of who owns growth beneath the Gulf chief executive covers the closely related boundary against the innovation mandate specifically. JOH's separate reading of how Gulf boards govern the technology and AI seat at board level sets out the equivalent boundary question from the governance side: which board committee, and which named director, actually owns oversight of a system already touching customers, as distinct from the executive mandate to build it in the first place. A board that has answered the governance question but left the two executive mandates, digital and data, unresolved against each other has closed only half the gap.

Every Gulf group now has a chief information officer, a chief data officer and a chief digital officer within one reporting line of each other. Naming which one owns the product decision is a five-minute conversation before the search opens, and a very expensive one to have for the first time after all three are already in post.

Where the mandate differs by platform type

JOH's reading across its own digital search mandates finds the boundary problem this piece describes plays out differently depending on the kind of Gulf platform doing the hiring, which matters because a brief written for one type transfers poorly to another. At a family-controlled group holding company running several distinct operating entities, the chief digital officer is frequently asked to build a shared digital capability across businesses that have never coordinated closely before, which makes the internal negotiation less about any single operating unit's resistance and more about persuading several semi-autonomous entities to adopt a common platform none of them asked for individually. At a bank or financial-services platform, by contrast, the boundary problem is sharper and faster to surface, because digital channels there touch regulated activity almost immediately, which forces the customer-ownership and data-governance questions this piece has described onto the table within months rather than years. At a logistics or industrials platform, the chief digital officer's brief more often concerns the ordering, tracking and account-management layer wrapped around a physical operation the group has run for decades, where the operating business's resistance tends to centre on data visibility rather than customer ownership as such: the physical operation already controls the customer relationship and is more worried about who else can now see how that relationship actually performs.

A board writing the appointment brief should therefore start from its own platform type rather than from a generic digital-transformation template borrowed from a different kind of business entirely. The specific boundary a Riyadh-listed bank needs to resolve before hiring is not the same boundary a diversified family holding company needs to resolve, and JOH's experience is that briefs written without this distinction tend to import assumptions, about regulatory exposure, about data ownership, about which existing function has the loudest internal voice, that do not actually hold for the platform in question.

What the second appointment usually gets right

JOH's mandate experience across the region's digital searches finds the same pattern this series has documented in adjacent technology seats: a group's second chief digital officer is regularly given something the first was denied, most often an explicit, board-agreed statement of which operating business units the seat has standing to negotiate with, and on what terms the customer relationship transfers if the digital channel succeeds. The first appointment, made before the group had felt the actual friction of a successful digital build, rarely carries that clarity, because the friction that makes it necessary has not yet happened. Boards that wait for the first incumbent to surface the boundary problem are, in effect, using a real appointment to do the organisational design work that should have preceded the search.

What good looks like once the boundary is drawn

The Gulf platforms JOH sees manage this seat well share a specific practice: they write the customer-relationship boundary into the chief digital officer's mandate as a set of named, revisable milestones, rather than as a single fixed org-chart line agreed once at hire and never revisited. A digital channel handling five percent of transaction volume needs a different boundary agreement from the same channel handling forty percent, and a board that pre-agrees how the boundary will move as the channel grows gives both the digital function and the operating business a shared, predictable framework rather than a recurring negotiation each time the channel crosses a new threshold of relevance. This staged approach also gives the chief digital officer a legitimate basis for asking the board to intervene when an operating business unit slow-walks a handover the milestones already anticipated, rather than leaving the appointee to escalate an ambiguous complaint about internal cooperation that is difficult for a board to adjudicate fairly after the fact.

The second practice JOH observes among the stronger appointments is deliberately less technical than it sounds: the chief digital officer's own performance measures are set jointly with the operating business unit most affected, rather than handed down from the chief executive alone. A digital channel that succeeds by the appointee's own metrics while quietly damaging the operating business's customer economics is not, in any meaningful sense, a successful appointment, whatever the dashboard shows the chief executive at quarterly review. Boards that insist on a jointly agreed scorecard from the outset find the resulting tension between digital and operating leadership becomes a genuine, productive negotiation rather than the slow, adversarial drift that otherwise defines the seat's difficult tenure pattern across the region.

The chief digital officer's dashboard and the operating business's dashboard should be measuring the same customer, not two different stories about the same customer that happen to share a logo. Where they diverge, the board has a governance problem, not a performance problem.

What a board should decide before it appoints

A board scoping a genuine chief digital officer mandate should resolve one question before any other, because almost every other design decision follows from the answer: what happens to the customer relationship, and to the revenue or data that comes with it, if the digital channel this appointee builds actually succeeds. Naming that answer in advance, and communicating it to the operating business units whose territory the channel will eventually touch, converts what is usually a slow, informal and personally costly negotiation conducted by the appointee alone into a governance decision the board has already made. Boards that skip this step get the pattern this piece has described: a capable appointee spending their tenure negotiating a boundary that was always the board's decision to draw, and rarely lasting long enough to see the digital channel through to the point the negotiation was actually worth having. Boards wanting standing visibility into how a newly created digital mandate is performing against its brief, rather than discovering the boundary problem only once it has already become a dispute, can use platforms such as Board Pulse to track that signal through the appointment's early years.

---

Key takeaways

---

JOH Partners is an executive search and senior executive recruitment firm advising boards, family groups and sovereign-adjacent platforms on chief digital officer and wider technology appointments across the GCC, the UK and Singapore. Boards scoping a digital mandate can engage a partner for a confidential conversation about structuring or filling the seat, or request a Board Pulse demo for continuous visibility of how the appointment is performing against its brief.