Chief Data Officer — Enterprise-Connectivity Business

The mandate

This enterprise-connectivity business has extensive information about customers but limited shared evidence about relationship health. Account teams see executive sentiment and renewal activity; network teams see faults and capacity; service managers see tickets and change; finance sees margin, credits and payment. Identifiers, time horizons and definitions differ. By the time several weak signals are assembled for an executive review, the customer may already have decided to move critical services elsewhere.

The company is creating a Chief Data Officer role to build a trustworthy customer-and-service evidence system. The CDO will own data strategy, governance, domain accountability, analytical products, responsible artificial intelligence and data-platform priorities for the business. They will not own retention campaigns or account decisions. Their obligation is to make service experience, operational dependency and economic consequence visible with sufficient confidence that commercial and delivery leaders can act.

This planned appointment must avoid the familiar trap of centralising everything before delivering value. The first work will concentrate on a few high-value questions: which accounts are deteriorating, what controllable causes explain the change, where intervention has worked, and which revenue is unprofitable to retain. The data architecture will grow from governed operational use rather than a universal model designed in isolation.

Scope and operating context

Based onsite in Dubai, the role influences approximately 1,000 employees and material partners across the United Arab Emirates and a wider international region. The perimeter includes data governance, architecture, engineering, analytics, data science, master and reference data, platform operations and responsible-AI controls. Principal partners sit in enterprise sales, product, solutioning, network, service assurance, finance, billing, cyber, privacy and legal.

Enterprise relationships are structurally complex. One customer may hold contracts across countries, subsidiaries, sites and services, with different account names and identifiers. A ticket can relate to a logical service, physical circuit, managed device or customer business process. Joining those records incorrectly can produce confident but false conclusions about incident frequency, usage or profitability.

Access to information is also constrained. Network and security data may reveal customer architecture; communications and sentiment may contain personal or privileged material; public-sector and regulated clients may impose localisation and purpose restrictions. The CDO must make data useful without creating a broad surveillance environment or weakening contractual control.

First-year agenda

The first ninety days will define the minimum relationship-and-service graph needed for priority accounts. The CDO will map customer entities, contracts, sites, products, logical services, network resources, incidents, changes, bills, credits and account interactions. Domain owners will agree which source is authoritative, how identity is reconciled and where confidence remains limited. A sample of account histories will be verified with operational and commercial teams.

The team will create a small set of decision products rather than another dashboard estate. A relationship-deterioration view may combine fault recurrence, missed changes, complaint escalation, usage shift, credit, renewal stage and service-cost movement. An incident-concentration product may reveal that apparently unrelated customer failures share one platform, access provider or configuration. Each product will name its user, decision, refresh, confidence and feedback loop.

The CDO will insist on causal discipline. Models may rank accounts for review but cannot claim why a customer will leave solely from correlation. Account and service leaders will test hypotheses through customer evidence and operational investigation. Interventions will be recorded so the business can distinguish genuine improvement from customers who would have remained anyway.

Data quality effort will follow decision consequence. Customer hierarchy, service identity, fault coding, change linkage and cost allocation are likely priorities because defects there undermine both experience and economics. Owners will receive clear thresholds and remediation queues. Manual stewardship may be appropriate for critical accounts while systemic fixes are developed; silent spreadsheet reconciliation will not become the permanent design.

Responsible use will be built in from the start. Purpose, lawful basis, contract permission, minimisation, access, retention and model monitoring will be documented for each sensitive product. Unstructured customer communications will not be ingested simply because technology allows it. Automated recommendations affecting price, service or retention will remain explainable and subject to accountable human judgement.

The data platform will be simplified around these use cases. The CDO will assess pipelines, warehouses, semantic layers, analytical tools and vendor contracts, retaining what can meet target controls and performance. New technology will require a clear gap. Teams will favour interoperable components, lineage and reusable domain products over duplicated project extracts.

Capability will extend beyond the central team. Account managers must understand what a risk signal means and does not mean; service teams must record root causes consistently; finance must reconcile cost and value definitions. The CDO will establish a network of domain stewards with protected capacity and executive backing, supported by practical training and decision-focused governance.

Within twelve months, priority leaders should see deteriorating accounts earlier, identify shared service causes faster and evaluate interventions with greater honesty. The business should also have a stable customer-service identity, fewer contested metrics and a data roadmap justified by operational decisions rather than technology fashion.

Leadership responsibilities

The CDO will chair a data council that resolves ownership, definition, access and investment decisions. Governance will be brief enough to enable delivery but firm where customer or network sensitivity is high. When executives request a single number despite material uncertainty, the CDO will show the range, confidence and decision implication rather than manufacture agreement.

They will lead data product, engineering and governance teams as one function. Product leaders will own adoption and outcome, engineers will own reliable delivery, and stewards will carry domain quality with line executives. The CDO will develop successors and reduce dependency on vendors or a few employees who understand customer identity.

The role will partner with cyber, privacy and legal leaders on incident response, data sharing and AI controls. In a material data event, the CDO must establish lineage, affected decisions and correction priorities, not merely restore a pipeline.

Measures of success

The executive committee will track earlier identification of deteriorating accounts, time from signal to accountable review, shared service causes found, interventions evaluated and avoidable churn in targeted cohorts. It will also measure whether uneconomic retention is identified rather than hidden by a success rate.

Data health includes customer-service identity coverage, critical-field quality, lineage, access exceptions, freshness, product adoption and reconciliation effort. Platform cost, vendor concentration, release reliability and retired duplication will be reviewed. Model measures include precision, drift, override, outcome and material differences across customer groups.

Candidate profile

Candidates should bring 18–22 years in data, analytics or technology leadership within telecommunications, enterprise services, banking, utilities or another complex relationship-and-asset environment. They must have built trusted entity and service data across fragmented operational systems and delivered analytical products used in consequential commercial decisions.

The board will seek examples of correcting a false churn narrative, refusing an intrusive data use and improving decisions before a perfect platform existed. Candidates should understand entity resolution, graph and service models, data engineering, causal analysis, responsible AI, privacy, security and enterprise economics.

The successful CDO will combine technical credibility with restraint. They must challenge account anecdotes without dismissing relationship knowledge, challenge model certainty without paralysing action and persuade executives to own data defects in their domains.

Compensation and appointment terms

Annual base compensation is expected between AED 1,600,000 and AED 2,200,000, supplemented by annual incentive and long-term participation. Reward will reflect adopted decision products, customer and service outcomes, responsible data use, platform discipline and leadership depth. Final terms will consider comparable data accountability, regional experience and verified forfeited awards.

Confidentiality

The business remains unnamed because customer relationships, service topology, commercial economics and analytical methods are sensitive. Detailed information will follow identity, conflict and confidentiality review. Applicants must not supply customer-level extracts, network relationships, models or proprietary data definitions from previous employers.