Following the service obligation through five operating roles

Mandate

Carry continuing service responsibility beyond the convenient internal completion point

Outcomes

• Established a controlled review route for bank-detail changes
• Funded alternative existence-verification support
• Kept unresolved customer cases in operating reports

Decisions in context

The COO role brings six operating heads and 214 colleagues within my remit, supported by ₹37 crore annual service expense. I report to the CEO and present operating recommendations to directors when invited, without a statutory seat. The instruction-change programme required a clear separation between a received request, verified authority and the status of an existing payment. The verification programme required suitable alternatives for people unable to use the ordinary attendance route. Both involved professional owners whose responsibilities could not be replaced by an operating preference for speed. I want the report to show where the customer still needs help and who can act next. My beneficial interest through the employee vehicle is disclosed because executive responsibility and ownership create relationships that would matter in any proposed outside contribution. They do not disappear when the conversation moves from service operations to board suitability.

Reason for the move

Current appointment; considering a life-insurance operating mandate and a prepared outside contribution

Concurrent appointment

COO appointment without a statutory directorship

Mandate

Connect processing status with the evidence of the customer outcome

Outcomes

• Corrected my interpretation of a transmitted payment file
• Separated confirmed credits, returned instructions and pending status
• Funded reconciliation without blindly repeating uncertain payments

Decisions in context

Four heads led 121 operating colleagues within ₹19 crore annual expense by the end of this appointment. The 2019 payment account exposed an error in my own definition of completion. I had accepted the transmitted file as evidence that all 24,000 instructions were paid. The bank-return evidence supported three distinct populations, and the returned and pending groups required different action. Correcting the report meant more than changing a label. We needed capacity to reconcile, communicate and obtain the right authorisation before another instruction was sent. Finance retained its payment responsibilities, while operations owned the service work that the earlier report had made less visible. The experience prepared me for COO responsibility by changing what I asked of a summary: the final line had to preserve the unresolved obligation, even when almost all of the routine processing had succeeded.

Reason for the move

Promoted to COO with broader enterprise-service responsibility

Mandate

Provide clear next steps without confusing assistance with entitlement authority

Outcomes

• Connected recurring service work with professional owners
• Separated changed instructions from continuing arrangements
• Developed exception follow-up around customer needs

Decisions in context

Thirty-eight colleagues worked within ₹5.4 crore annual function expense when I entered the insurer. The service role sat beside financial, actuarial and contractual responsibilities that I needed to understand without claiming as my own. Customers expected continuity, and a new request could affect an arrangement that had worked for years. I learned to ask exactly what was changing, what evidence supported the request and which part of the existing instruction remained valid. The operating team could explain a route and organise assistance, but could not create entitlement through a reassuring response. That distinction helped me work with professional colleagues when an unusual case did not fit the ordinary process. Leading wider operations later meant ensuring that the capacity for such follow-up survived alongside the pressure to process large volumes and report concise completion figures.

Reason for the move

Promoted to coordinate wider policy-service and payment operations

Mandate

Make handover states and unresolved records understandable to the responsible client

Outcomes

• Organised capacity for exceptions beside routine volume
• Distinguished transmission from reconciliation
• Preserved client authority over corrected instructions

Decisions in context

I led fourteen colleagues within ₹88 lakh annual delivery expense. Clients retained their funds and approval rules, while our team had to make the record handover dependable. A file could leave our desk and still require acceptance or reconciliation elsewhere. I learned to organise attention around the unresolved items rather than assume the size of the successful batch described the whole service. The work also required discipline about authority: we could identify a mismatch without deciding on a replacement payment or changing the client’s instruction ourselves. Moving into Zerqavni offered a chance to follow the continuing customer relationship from inside the organisation carrying the obligation. I wanted to understand what happened after the processing task, while retaining the caution that a missing confirmation should be investigated rather than converted into an unsupported claim of failure or success.

Reason for the move

Joined a life insurer to lead continuing annuity service

Mandate

Keep the reference and unresolved state clear through the next handover

Outcomes

• Prepared schedules under supervision
• Checked references across processing records
• Learned to separate missing evidence from an assumed outcome

Decisions in context

I began after completing mathematics studies in May 1990. In a seven-person records group I prepared schedules and checked references for senior review. The assignment gave me no authority to move client funds or alter an instruction. It did show how a small mismatch could stop a record joining the next stage, even when the surrounding batch looked complete. I learned to preserve the reference and the unresolved question so the responsible owner could investigate. A missing confirmation might have several explanations; my task was not to choose the one that made the report easiest to finish. Later management work expanded my responsibility for the process, but that early distinction remained relevant. The 2019 completion error was a reminder that seniority does not protect a leader from overlooking a discipline first learned in a junior role.

Reason for the move

Promoted into processing-team management