Follow the instruction across the systems that carry it

Mandate

Preserve business meaning in transaction records, customer identities, dated changes and practical use of systems

Outcomes

• Separated receipt-message retries from distinct valid instructions
• Kept distinct customer entities apart during a proposed merge programme
• Introduced separate effective and recorded dates with explicit legacy exceptions
• Funded keyboard improvements and retained assistance for four unfinished tasks

Decisions in context

I became CIO in January 2021 and now lead 72 employees through five heads, with eighteen contractors separately counted. The FY2026–27 authority comprises ₹18.4 crore operating expense and ₹6.7 crore approved change investment; it is not the employer's ₹1,540 crore gross written premium. Meena owns enterprise direction, while Dinesh and the appropriate specialists retain business and insurance decisions. I present to directors without a statutory seat. The recent cases require me to explain what a system result means before claiming a wider outcome: a resolved message is not automatically a cover decision, and a passed task is not a complete accessibility certification. I have also had to correct the date-view design I accepted. A first external board role would extend this habit of questioning the evidence while requiring induction, consent and a different relationship to executive authority from the one I hold in my current employment.

Reason for the move

Current appointment; considering a first external board contribution

Mandate

Connect technical delivery evidence with the business task and the people expected to complete it

Outcomes

• Introduced working demonstrations of exceptions alongside ordinary journeys
• Developed broader responsibility for service operations and change
• Learned to examine date meaning and practical interaction paths

Decisions in context

The head-of-IT role began in October 2015 with 41 employees, four leads and ten separately counted contractors. We worked within ₹8.6 crore annual operating expense in a 390-person insurer recording ₹780 crore gross written premium for FY ending March 2016. I became responsible for a wider set of services and the evidence used to describe their readiness. A functioning server or completed installation did not establish that a colleague could finish the intended task. I began asking teams to demonstrate late records, corrections and unfamiliar interaction paths, although my later acceptance of a simplified date view showed that the habit was not yet consistent. The role taught me to connect technical claims with the business question they were meant to answer. Promotion to CIO widened that responsibility to the enterprise account, including the ongoing support and professional decisions that remain after a project has delivered its software.

Reason for the move

Promoted to chief information officer

Mandate

Represent insurance instructions and records without treating their technical processing as contractual acceptance

Outcomes

• Learned to distinguish receipt, instruction and authorised insurance change
• Coordinated platform work with finance, operations and underwriting owners
• Built experience supporting specialist decisions through system evidence

Decisions in context

I joined Qorzuni in June 2008 after fourteen years in distribution systems. The insurer employed 210 people and recorded ₹310 crore gross written premium for FY ending March 2009. Eighteen technology employees and six contractors worked within ₹2.4 crore annual platform operating expense. The move required me to learn a different business meaning for familiar-looking records. A receipt did not automatically establish cover, and a processed instruction still needed the appropriate business authority. I worked with finance, operations and underwriting colleagues to understand those boundaries before representing them in applications. My remit covered the systems that supported their work, not the insurance decisions themselves. The role also made entity identity more consequential: a shared contact could connect organisations without making them the same customer. Promotion to head of IT gave me broader responsibility for whether the services preserved those distinctions through operation, change and the exceptions that ordinary demonstrations tended to omit.

Reason for the move

Promoted to head of IT

Mandate

Connect order, warehouse and invoicing records while preserving the business meaning of identity and sequence

Outcomes

• Examined repeated messages through the intended business instruction
• Distinguished shared contact records from customer identity
• Connected late-arriving data with the event it represented

Decisions in context

I became integration lead in September 2001, with twelve colleagues through two leads and ₹93 lakh annual expense. Jezvani employed 230 people and earned ₹72 crore revenue for FY ending March 2002. The systems we connected used similar labels for records that did not always mean the same thing. A warehouse event might arrive after an invoice update, and two buying entities might share a contact person. I learned to ask operating colleagues to explain the relationship before choosing how the integration should combine or order the data. My team did not decide commercial terms or dispatch priorities. We needed to preserve the evidence those decisions relied on. Moving to Qorzuni offered a different business context where the same habit would be useful, while requiring substantial learning about insurance authority and the distinction between a received instruction and a contractually effective change.

Reason for the move

Joined an insurer to apply integration experience to a different set of business obligations

Mandate

Monitor overnight jobs and help supervisors establish what had completed when a response was missing

Outcomes

• Learned that a missing acknowledgement did not prove an action had failed
• Maintained operating records under supervision
• Developed an interest in the meaning of repeated instructions

Decisions in context

I completed computer science in June 1994 and joined Jezvani the next month. The company had 110 employees and ₹24 crore revenue for FY ending March 1995. I worked in a seven-person systems operations group without direct reports or independent spending. Overnight distribution files taught me to distinguish a failed job from a missing acknowledgement and to record what was known before a supervisor chose the next step. Sending a file again was easy; establishing whether it represented another delivery or the same instruction required an understanding of the process around it. I did not own stock decisions, customer terms or dispatch priorities. My contribution was to monitor, document and help the responsible people reconstruct the event. Those early questions became a foundation for the integration role, where I would connect several systems and need to preserve the distinctions each operating team relied on.

Reason for the move

Promoted to integration lead