Each move brought me closer to the consequences of the account.

Mandate

Maintain an intelligible relationship between telecom records and the commercial or operating claims based on them.

Outcomes

• Distinguished the 2023 population of 7.8 million registered subscriptions from 6.1 million meeting an internal activity condition.
• Corrected the 2021 inventory account to distinguish twelve hundred sites from thirty-six hundred sector records.
• Restricted the 2025 voluntary-test account to its selected cohort instead of asserting an all-subscriber result.

Decisions in context

The CDO appointment broadened the audience for the distinctions I had learned through usage and customer records. A management claim could change meaning as quickly as a join between systems. I wanted the team to retain the counting object, relationship and observation conditions when presenting evidence to senior readers. My delegated expense supports that function, while network engineering, operations, billing, marketing, finance and cybersecurity remain separately owned. Executive board presentations began with this appointment in April 2019; they do not constitute statutory-director service. The subscription and voluntary-test reviews show why a more qualified statement can be a useful result even without an improvement claim. I would rather explain the boundary of an account before it is relied on than allow the size of the dataset to make an unsupported conclusion appear settled.

Reason for the move

Appointed to the group data remit after leading customer and network information; remains in this role.

Mandate

Explain how customer and network identifiers relate across source systems and through time.

Outcomes

• Reviewed eighty-four thousand number disconnections in the 2015 assignment-history work.
• Retained interval evidence for fifty-one thousand numbers reassigned during that review year.
• Completed S$2.4 million data work removing unsupported continuity from number-based customer histories.

Decisions in context

This role moved my attention from individual usage events to the identities through which the enterprise connected its records. The reassignment case showed that a familiar field could remain unchanged while its relationship to a customer changed. I worked with commercial, operating and privacy colleagues to distinguish a useful join from a permitted or well-supported interpretation. The title referred to an executive job, not membership of a statutory board. My team maintained the relationships and their evidence; it did not take ownership of customer policy or legal conclusions. I also became more alert to histories that appeared complete because uncertainty had been removed during preparation. The move into the CDO role followed that broader understanding of the account, rather than a claim that the function itself had produced all growth in the company around it.

Reason for the move

Promoted to CDO to extend the interpretation discipline across the group’s data account.

Mandate

Maintain the usage-data account and distinguish delivery evidence from the events represented.

Outcomes

• Owned the mistaken 2007 interpretation of eighty million received records as additional traffic events.
• Reconciled the reviewed log to seventy-four million distinct source-and-event pairs with six million documented replays.
• Supported S$720000 correction preserving receipt history and the separately defined event view.

Decisions in context

Joining the operator meant living with a definition after the initial analytical delivery. The replay-counting error was a difficult lesson because I had approved the label myself. Daniel Varneshu’s challenge required a correction to management, not just a technical adjustment hidden in the next extract. I wanted the team to preserve the delivery history while explaining why it differed from the distinct-event account. Similar-looking records were not enough to justify deletion, and the correction could not be used to imply a billing result beyond its evidence. This period made responsibility for interpretation part of my working definition of data leadership. The later company scale is not assigned backwards to the start of the role; the figures here describe 2011 context, while the owned error belongs to the earlier 2007 review.

Reason for the move

Expanded into customer and network information after developing responsibility for recurring usage evidence.

Mandate

Lead analytical work whose definitions and source relationships remain understandable after handover.

Outcomes

• Made the object represented by a source record explicit in analytical handovers.
• Separated the size of an extract from the strength of the interpretation drawn from it.
• Chose a telecom operating role to follow those definitions into repeated organisational use.

Decisions in context

Leading engagements gave me responsibility for how other analysts explained their work, not merely whether their calculations could be reproduced. I asked the team to identify the source object and the intended conclusion before deciding that a large extract was persuasive. Clients could use the same record for different purposes, and a definition that was clear during an assignment could become ambiguous when carried into a recurring report. My expense delegation covered delivery work; the company’s fee revenue described the surrounding business. I increasingly wanted to understand what happened after the handover, particularly where telecom operations repeatedly reused the same identifiers. Moving to Navirelan was a change in accountability. It offered the opportunity to maintain the account over time, including responsibility for correcting my own interpretation when the evidence later challenged it.

Reason for the move

Joined Navirelan to take continuing responsibility inside an operator rather than finish at advisory delivery.

Mandate

Understand source definitions and check the relationship between observations and proposed conclusions.

Outcomes

• Traced analytical statements to the source records they purported to describe.
• Distinguished the presence of an identifier from evidence about the entity behind it.
• Developed the source-questioning practice later used in telecom data leadership.

Decisions in context

I entered analytical work two months after completing information studies in June 1990. The early task was often less glamorous than the final chart: determine what a row meant, which source had supplied it and whether the proposed comparison was comparing the same kind of thing. Working under an assignment manager taught me to ask those questions before becoming attached to an attractive result. I had no spending or line-management authority, and the nine-person group was the team around me rather than a team I led. The experience supplied a habit that remained useful as responsibilities grew. An identifier could make a record easy to retrieve without making its interpretation obvious. I wanted to become better at explaining that difference to the people who would use the analysis, which led naturally towards engagement leadership.

Reason for the move

Promoted into engagement leadership after progressing from supervised analysis to delivery responsibility.