Thirty-one years of asking what belongs on either side of a link

Mandate

Maintain explainable party relationships and data evidence for separately owned insurance and service decisions.

Outcomes

• Clarified 54 financing-party mappings and retained 18 unresolved cases after a 360-policy review.
• Separated 120 repeat deliveries from 2,280 distinct submission events in a 2,400-arrival review.
• Recommended an assisted matching pilot with both false links and missed matches visible.
• Supported 225 purpose-specific role connections while withholding 15 that lacked the required evidence.

Decisions in context

My appointment brought responsibility for 64 colleagues and the relationships between the data function and other professional owners. Five heads coordinate the work, including Rina's stewardship responsibility. I report to Anil Qezvathri and manage ₹14.2 crore annual function expense, while insurance judgement, funding decisions outside that delegation and access authority remain separately owned. The party-role, ingestion, matching and service-connection cases illustrate what this distinction means in practice. A corrected reference does not amend a policy; a matching score does not authorise adverse action; a known person does not automatically acquire a new permission. I hold 0.15% of total equity through the employee vehicle and have no statutory seat. Executive presentations give me experience of explaining data decisions to a board, without making me a director. I would carry those boundaries into any discussion of an outside appointment rather than borrow the employer's full scale as personal authority.

Reason for the move

Current role; examining a possible first outside board contribution after employer and appointment-specific review.

Mandate

Connect information across functions while preserving the meaning of parties, references and relationships.

Outcomes

• Withdrew the 2019 automatic shared-contact merge after the 920-pair review.
• Separated 610 supported links, 230 different-party pairs and 80 unresolved pairs.
• Funded ₹62 lakh correction and accepted a six-week delivery delay.

Decisions in context

The director title described a functional appointment, without a statutory board position. I led 31 colleagues and was expected to make information easier for operating teams to combine. That ambition contributed to my 2019 error: a shared telephone seemed a practical way to reduce apparent duplication, and I supported it before sufficiently examining what the contact represented. Rina's review showed why the register could not be improved by making different people look like one. I authorised the correction and explained the delay to the delivery sponsor. The six-week postponement did not make the existing navigation problem disappear, and the eighty unresolved pairs still required work. I learned to put that continuing cost into the recommendation rather than portray withdrawal as a complete solution. Promotion to CDO carried the lesson forward: the data function must be able to challenge the meaning of its own integration proposal before it asks others to trust the resulting account.

Reason for the move

Promoted to CDO with an enterprise data remit in November 2021.

Mandate

Keep customer, contact and related-party references useful without substituting data labels for insurance interpretation.

Outcomes

• Documented separate roles for policyholders, assisted contacts and financing relationships.
• Introduced a review route for party links whose evidence did not support a settled classification.
• Brought operating owners into source-to-reference mapping discussions.

Decisions in context

Joining an insurer meant living with the reference after the first reconciliation was delivered. Sixteen colleagues maintained information used by teams with different professional responsibilities. A service contact might help someone locate a policy without being the contracting party. A financing institution could appear for a reason that the data team was not authorised to reinterpret. I began involving operating owners before proposing a common category, because a technically convenient field could ask the next reader to assume too much. The work was not a mandate to decide cover or claims. It was responsibility for making the relationship account useful to those who held that authority. My ₹2.4 crore annual expense supported stewardship, not an insurance fund. The next appointment expanded the reach of these questions across integrations, and it also exposed the risk that my enthusiasm for a simpler shared account could outrun the evidence beneath it.

Reason for the move

Moved into wider information integration after developing cross-function stewardship experience.

Mandate

Review matching instructions and explain unresolved relationships in client information assignments.

Outcomes

• Required matching instructions to identify the relationship being asserted.
• Kept unresolved pairs visible in delivery reviews rather than forcing a common value.
• Developed team supervision and expense responsibility alongside analytical work.

Decisions in context

As reconciliation lead I had to explain the cases that a matching exercise could not settle, as well as the ones it could. Thirteen colleagues worked within ₹1.2 crore annual function expense. Clients retained their own record and business decisions; our recommendation did not become permission to alter every system in which a reference appeared. I learned to ask for the intended use before agreeing that two fields could be treated as equivalent. This sometimes made a delivery discussion longer, because a client wanted a clear answer while the source supported several interpretations. I wanted the uncertainty to be useful, with an owner and a next step, rather than a vague disclaimer at the end of the report. The move to Vezqerthi followed from that interest. I wanted to see how the relationship would be maintained and challenged after the assignment closed, not only whether the first delivery passed its acceptance check.

Reason for the move

Joined an insurer to take continuing stewardship responsibility beyond service assignments.

Mandate

Compare supplied references and preserve their source context under supervisory review.

Outcomes

• Learned to distinguish a common attribute from evidence of a common party.
• Recorded unresolved differences for supervisory assessment.
• Built source-tracing habits before taking responsibility for a team's recommendations.

Decisions in context

I joined one month after completing statistics, with an interest in patterns and limited experience of how business records were created. I was one of seven junior analysts, without staff or a budget. Supervisors reviewed our comparisons and asked us to explain what the source actually described. A service reference and a contracting-party reference could look similar while answering different questions. I learned to retain the original account and record uncertainty instead of choosing whichever value made a combined table look complete. The work required patience with ordinary operational detail, including the reasons people used shared contacts or supplied information through another person. Over time I took more responsibility for explaining a comparison to colleagues and clients. That preparation led to the 2002 promotion. It did not make me immune to the later shared-contact mistake; the career illustrates how a familiar principle can still be neglected when a larger delivery ambition becomes persuasive.

Reason for the move

Promoted to reconciliation lead after taking responsibility for review and explanation.