From checking a page to questioning a product promise

Mandate

Keep product representations traceable to their sources and make material uncertainty visible to users and decision-makers.

Outcomes

• Funded reading-order corrections without inferring a collection-wide quality rate
• Preserved provenance behind reviewed duplicate relationships
• Kept exact, year-only and ranged dates distinct during migration
• Withheld a search-answer feature after unsupported outputs appeared

Decisions in context

The CDO appointment made me accountable for the way evidence travels from specialist work into a product decision. I lead thirty-eight colleagues through three heads, with operating expense separated from the platform programme. That structure requires clear decisions about what the team can authorise and what belongs to the collection owner. I have learned to explain a data-quality finding without allowing its numerical precision to imply more than the review established. The most difficult discussions concern an attractive feature or a simple migration path whose convenience would conceal uncertainty. I present those choices to the chief executive and, where appropriate, directors. I am responsible for the clarity of the account and the work within my remit, while the client retains decisions about historical interpretation, access and disposition. Board presentations do not give me a director's vote.

Reason for the move

Current role; exploring a first board contribution alongside executive work.

Mandate

Make descriptive meaning and transformation history consistent across the product's collection workflows.

Outcomes

• Connected specialist collection judgements with product requirements
• Improved visibility of source expressions and later interpretations
• Supported technical collaboration through the 2019 ownership change

Decisions in context

Leading the metadata platform brought me into regular discussion with engineers, implementation teams and collection specialists who used different language for the same problem. I had to make the consequence of a modelling choice understandable without turning every disagreement into a technical argument. Twenty-six colleagues worked through two managers, with a ₹5.3 crore annual expense budget. We examined how an interpretation could remain traceable when a record moved between workflows. The ownership change in 2019 broadened collaboration with Hozurei, but did not change who owned the client's collection decisions. I became more careful about distinguishing a shared technical capability from permission to use material for another purpose. The CDO role followed an increasing need to connect those questions with the promises the company made about its products and services.

Reason for the move

Promoted to CDO as responsibility expanded into company-wide data evidence and product commitments.

Mandate

Develop models that preserve collection meaning across import, search and display.

Outcomes

• Brought source interpretation into model reviews
• Distinguished qualified values from genuinely absent data
• Worked with implementation teams to preserve context during migration

Decisions in context

I joined Nerzhavi because a software model could carry a good decision into many future collections, but it could also repeat a bad assumption at scale. I led twelve colleagues with a ₹1.8 crore function budget under the head of product engineering. The work required us to understand why a collection specialist qualified a date or maintained two related descriptions. Those were not automatically inconsistencies to remove. We discussed how the product should preserve the source expression and make later interpretation visible. I learned to ask what a user would infer from the final screen, not merely whether the imported record matched a technical schema. That habit helped me work across engineering and implementation, and it became the basis for the broader metadata-platform role I took in July 2017.

Reason for the move

Promoted to lead metadata platforms across the growing product organisation.

Mandate

Help collection owners turn descriptive practice into consistent, inspectable digital records.

Outcomes

• Learned to distinguish related items from duplicate descriptions
• Documented the basis for specialist metadata decisions
• Progressed into leadership of a nine-person team

Decisions in context

At Veshrali I moved from checking the fidelity of a processed page to understanding the description attached to it. Collection staff could explain why two similar entries referred to different items or why a date should remain qualified. I began as an analyst and became metadata lead in 2009, managing nine colleagues and a ₹1.1 crore annual function budget. The leadership task was to make those decisions consistent enough for a team to apply while preserving the cases that required specialist judgement. I did not become the authority on every collection's history. Instead, I learned to record who had made an interpretation and what supported it. Nerzhavi offered a chance to bring that discipline into software design, where a field definition could affect many projects rather than one processing assignment.

Reason for the move

Joined a software product company to influence the models used across multiple collections.

Mandate

Check the relationship between source pages, searchable text and record associations.

Outcomes

• Compared processed text with the corresponding scan
• Identified page-order and association problems beyond file completeness
• Developed a habit of checking what a search user would actually see

Decisions in context

My first appointment began two months after my mathematics degree. I worked in an eight-person processing team and had no budget authority. The practical task was to check whether a scan, its searchable text and its place in the record still corresponded. I learned that producing the expected number of files did not establish that a reader could use them correctly. A column might be read in the wrong order, or a page might be associated with the wrong description. Those errors made the difference between a technically complete delivery and a useful one. I became interested in the assumptions that linked the page to its catalogue entry, which led me towards metadata work. Moving to Veshrali gave me a chance to examine that meaning with collection specialists rather than focus only on the processing output.

Reason for the move

Moved into metadata work to understand the meaning attached to digitised material.