The Chief Data Officer Role: Who Owns the Data a Gulf Board Answers For

Gulf groups have appointed the chief data officer role faster than they have decided what it owns, and JOH Partners' reading of its technology and digital senior search mandates across the region finds most boards cannot currently name, with confidence, which single executive is accountable if a material data governance failure surfaces tomorrow. The question a board should be asking is not whether it needs a chief data officer, but which of its existing officers is already carrying that accountability by default, and whether that arrangement was a deliberate decision or simply the outcome of nobody having made one. This piece sets out what the chief data officer role actually covers where it is built with genuine intent, how it differs from the adjacent technology seats it is routinely confused with, and what a board should decide before the gap is exposed by an incident rather than by design.

Why the title arrived before the definition

The chief data officer title has spread across Gulf institutions considerably faster than a shared understanding of what it owns has developed, and the reason is structural rather than a failure of any individual appointment. Data accountability sits at the intersection of several remits Gulf boards have historically kept separate: the chief information officer's infrastructure and systems mandate, the chief technology officer's product and client-facing mandate, and increasingly the chief risk officer's exposure to how poor data quality or governance translates into regulatory or reputational risk. A chief data officer title, created without a board decision about which of these adjacent claims it is actually meant to consolidate, tends to become a fourth claim layered onto an already contested space rather than a genuine resolution of it.

JOH's earlier research into the technology seat on the Gulf board documented the closely related pattern at chief technology officer and chief information officer level, where the arrival of artificial intelligence collapsed a previously clean division of labour between the two titles. The chief data officer role sits squarely inside that same collapse, and in JOH's reading it is frequently the seat that surfaces the problem most sharply, because data ownership is the layer beneath both the infrastructure question and the product question, and a board that has not resolved who owns it struggles to resolve either of the other two cleanly either.

A chief data officer title does not automatically consolidate accountability. Left undefined, it just adds a fourth claimant to a question the board had already left three seats fighting over.

What the seat owns where it is built with genuine intent

Where JOH has observed the chief data officer role built deliberately rather than layered on reactively, it typically holds four distinct areas of ownership. The first is data quality and lineage: a documented, current understanding of where the group's material data originates, how it moves through systems, and how reliable it is at each stage, rather than an assumption of reliability that nobody has actually tested. The second is data governance policy: the rules by which data is classified, protected, retained and shared, set and enforced consistently across business units rather than improvised locally by whichever function happens to be building a given system.

The third is accountability for how data feeds AI and analytics systems specifically, which has become the most board-visible part of the mandate as AI adoption has accelerated across the region faster than the governance structures meant to oversee it. The fourth, and the one JOH's search practice finds most frequently missing from otherwise well-designed mandates, is a genuine reporting line to the board or a board committee, distinct from reporting purely through the chief information officer or chief technology officer, because a data accountability function that only ever reaches the board secondhand through an adjacent seat is not, in any meaningful governance sense, board-accountable at all.

The boundary against chief information officer, drawn plainly

JOH's earlier work on the chief information officer role sets out that seat's systems and infrastructure mandate in detail; this piece is concerned with a genuinely distinct question, who owns data as an asset and who answers for its governance and AI accountability, rather than who keeps the systems running. The two seats overlap in practice more than their formal descriptions suggest, and JOH's mandate experience finds the overlap itself is rarely the problem. The problem is a board assuming the overlap has been resolved simply because both titles exist on the organisation chart, when in most cases JOH has observed, nobody has actually decided which seat wins when the two claims genuinely conflict.

The distinction the live market itself increasingly draws, and the one a board scoping a new chief data officer mandate should draw explicitly in the role specification, is between systems reliability, which belongs with the chief information officer, and data meaning, ownership and governance, which is the chief data officer's genuine remit. A board that cannot articulate this distinction in a single sentence has not yet resolved it internally, and a candidate interviewing for either seat will notice the gap in the first conversation.

Ask a board who owns the reliability of a system and who owns the meaning of the data inside it, and you will usually get two different answers, or the same answer twice, and neither response tells you the accountability question has actually been resolved.

Why the gap persists even at well-governed institutions

The persistence of this accountability gap is not confined to less mature Gulf institutions; JOH has observed it at well-governed, well-resourced platforms with otherwise strong technology leadership. The reason, consistent with JOH's boardroom AI readiness research, is that data and AI governance cuts across categories Gulf boards have historically kept in separate committees, technology risk with IT, operational risk with the COO, and increasingly regulatory and reputational risk with legal or compliance, so that a board asked to name the single committee that owns data accountability is frequently choosing between several imperfect answers rather than an obviously correct one. A chief data officer appointed into that structure without a board decision about which committee receives their reporting inherits the ambiguity rather than resolving it.

JOH's search building Chief Technology Officer leadership at a tier-one GCC universal bank, anchoring a multi-year core banking modernisation programme, illustrates the scale of governance clarity a well-resourced technology mandate requires at a mature institution, and the data accountability question sits directly beneath that same modernisation work at almost every institution JOH has advised on a comparable programme. JOH's guide to what a board tests in a chief data officer interview sets out how this ambiguity has changed the interview itself: boards increasingly test less for technical data architecture and considerably more for a candidate's ability to explain, in language a non-technical board can act on, what data ownership actually costs and what leaving it unresolved is likely to cost more.

What a functioning structure looks like

Boards that have closed this gap, in JOH's observation across its technology and digital senior mandates, share a consistent pattern. They name one executive, whatever the title, as the board's single point of accountability for data ownership and governance, and write that decision into the relevant committee's terms of reference rather than leaving it inferred. They give that accountability a genuine board or committee reporting line, distinct from routing purely through an adjacent technology seat. They distinguish explicitly, in the role specification and in how the seat is evaluated, between systems reliability and data meaning, so the chief data officer and chief information officer are not quietly competing for the same territory. And they review the structure on a defined cycle, because data governance is not a decision made once and then left, it is a live question that evolves as the group's own AI adoption accelerates.

Boards wanting ongoing visibility into how this accountability structure is functioning between formal review cycles, rather than reconstructing the picture only after an incident has already forced the question, increasingly use platforms such as Board Pulse to track governance and executive-layer signals on a standing basis. Magdolin Boukhary's account of integrating analytics with human leadership offers a useful adjacent perspective on the same underlying discipline from inside an operating business: data only becomes a genuine leadership asset once someone is deliberately accountable for connecting it to how the organisation actually makes decisions, rather than treating it as a technical byproduct owned by whichever system happens to generate it.

Where this leaves a board naming the seat

The chief data officer role is not a governance solution that resolves itself once the title exists on the organisation chart; it is a structural choice that behaves very differently depending on whether a board has decided, deliberately, what the seat consolidates and where it reports. A board that draws the boundary against the chief information officer and chief technology officer explicitly, gives the seat genuine committee access, and reviews the structure on a defined cycle gets a credible answer to the data accountability question before an incident forces it. A board that creates the title without making those decisions gets a fourth name on the organisation chart and the same unresolved question it started with, discovered at the least convenient possible moment.

---

Key takeaways

---

JOH Partners is an executive search and senior executive recruitment firm advising boards, family groups and sovereign-adjacent platforms on chief data officer, chief technology officer and chief information officer appointments across the GCC, the UK and Singapore. Engage a partner for a confidential conversation about scoping or filling a chief data officer mandate, or request a Board Pulse demo for continuous visibility of how the executive-layer accountability structure around it is actually functioning.