From source descriptions to the model behind a service

Mandate

Preserve catalogue identity and evidence while making the service's supported claims explicit

Outcomes

• Reversed a work-based merge before the trial output reached customers
• Kept unresolved permission entries outside a supported service set
• Required confirmed contributor roles instead of prominent-name substitution
• Expanded the language description to preserve plurality and uncertainty

Decisions in context

I became CDO in May 2021 and report to Priya. Thirty-nine data colleagues work through five leads within ₹6.7 crore FY 2026–27 expense, including the ₹2.4 crore improvement programme. Qarzemi has 190 direct employees and ₹66 crore FY 26 revenue. My remit concerns data representation, stewardship and the evidence the service can use; clients and qualified advisers retain permission decisions, with Devika coordinating the relevant clarification. The role has required me to reverse my own recording-consolidation approval and explain why a smaller supported set can be more defensible than a complete-looking one. It also requires attention to contributor and language meanings that a convenient field can erase. I have no equity or statutory seat. My prospective board contribution would connect those experiences with oversight of a specialist service's promises, after broader governance preparation and a review of the practical demands of an appointment.

Reason for the move

Continuing chief data responsibility while examining the preparation needed for a first board contribution

Mandate

Connect client descriptions, catalogue expertise and service definitions without losing their meaning

Outcomes

• Developed responsibility for definitions across catalogue teams
• Distinguished role meaning from name consistency in credit work
• Brought source evidence into discussions of language descriptions

Decisions in context

The December 2015 appointment widened my remit beyond the delivery of individual metadata assignments. Qarzemi employed 124 people and recorded ₹38 crore revenue for FY ending March 2016. Twenty-five colleagues worked through four leads within ₹4.1 crore annual operating expense. I reported to the chief operating officer and worked across definitions used by clients, catalogue specialists and service systems. The same field name could carry different assumptions about a contributor or an item. My task was to make those assumptions discussable before they became a product constraint that specialists were expected to work around. The experience gave me a stronger view of stewardship as a business responsibility, though it did not prevent my later consolidation mistake. Moving into the CDO role made me accountable for how the enterprise approved such model choices and explained their consequences, rather than only how individual teams maintained their records.

Reason for the move

Appointed to the company's chief data role

Mandate

Organise music catalogue assignments while preserving the evidence and specialist decisions behind supplied descriptions

Outcomes

• Learned the distinct work and recording relationships used by the service
• Developed coordination between data operations and rights specialists
• Made source clarification part of assignment planning

Decisions in context

I joined Qarzemi in March 2009 and moved to Guwahati. The company had seventy-one employees and ₹18 crore revenue for FY ending March 2010. Thirteen data colleagues worked through two leads within ₹1.6 crore annual expense, reporting through me to the operations director. Music brought a richer set of relationships than I had encountered in general catalogue services. I needed to learn from people who understood recordings, contributions and the evidence accompanying a proposed use. A general facility with data did not make me qualified to resolve those questions alone. I coordinated assignments so that clarification could happen before an uncertain description became a delivered assertion. Stewardship leadership later extended that work across the company's definitions and service systems. I took the promotion because the recurring difficulties were increasingly about what the organisation meant by its data, not simply the completion of a particular catalogue task.

Reason for the move

Promoted to lead cross-company data stewardship

Mandate

Supervise evidence-based catalogue corrections and make unresolved descriptions visible to assignment owners

Outcomes

• Developed responsibility for team coordination and delegated expense
• Separated supported corrections from convenient field completion
• Explained unresolved descriptions before assignment closure

Decisions in context

From June 2003 I supervised nine colleagues through two leads within ₹47 lakh annual function expense. Jemqoli employed eighty-four people and reported ₹13 crore revenue for FY ending March 2004. I reported to the head of catalogue operations and began to see how different teams could use a shared field name while assuming different meanings. The work required more than checking whether an entry was filled. I had to ask what supported the correction and whether the proposed completion would conceal an unresolved description. Production schedules still mattered, and I learned to explain the consequence of holding an entry rather than simply insist that evidence work take as long as it wished. The music-services opportunity offered a more specialised setting for those questions. I wanted to develop responsibility in a field where the relationships behind a catalogue were central to the service rather than incidental to it.

Reason for the move

Accepted a specialist music metadata operations role in Guwahati

Mandate

Prepare assigned descriptions and cross-references for senior review using the available source evidence

Outcomes

• Learned to test repeated titles against the described object
• Prepared source-linked descriptions under senior review
• Developed the catalogue foundation for later supervisory work

Decisions in context

I joined Jemqoli in July 1997 after completing information science in June. The business had thirty-eight employees and ₹4.9 crore revenue for FY ending March 1998. I worked in a six-person reference group under a senior cataloguer, without reports or delegated expense. My assignments involved descriptions, cross-references and the source material that supported them. A repeated title could look like an obvious duplicate until the underlying item showed why the entries needed to remain distinct. Senior review taught me to treat that resemblance as a question rather than a conclusion. I also learned to retain the basis of a correction so that another colleague could understand it later. Promotion to supervision brought a different responsibility: helping others make those distinctions while accounting for time, expense and the pressure to close assignments. It was the beginning of my interest in how an organisation defines completion.

Reason for the move

Promoted to reference-data supervision