Learning the service behind the technical response

Mandate

Connect technology evidence with complete authorised insurance work

Outcomes

• Made offline freshness and verification limits explicit
• Assigned continuing ownership for service-certificate renewal
• Revised test material and examined the actual exported document before release

Decisions in context

I became CIO in January 2021. The current team comprises eighty-two employees through six heads, plus sixteen contractors counted separately. My authority covers ₹22.6 crore annual operating expense and ₹8.3 crore approved change investment, with finance responsible for accounting classification. I report to Faisal Zeqvenmi and work with Leena Qezvemni on operating consequences. The insurer has 740 employees across eighteen branches and ₹1,680 crore gross written premium for FY ending March 2026. Ownership is 58% domestic investor, 27% industrial group and 15% employee vehicle, including my 0.4%. I hold no statutory seat. Recent work asks whether a status, test count or preview supports the conclusion management draws from it. I want a future board contribution to carry those questions into collective judgement without becoming a parallel channel for directing technical delivery.

Reason for the move

Continuing CIO leadership while considering a first outside non-executive contribution

Concurrent appointment

Executive CIO role without a statutory directorship.

Mandate

Develop enterprise technology delivery and evidence of usable service recovery

Outcomes

• Expanded responsibility beyond individual platform delivery
• Corrected my service-readiness claim after a database-only recovery test
• Retained nine assisted tasks after the broader 240-task retest

Decisions in context

I became head of IT in April 2015. Nevqemzi employed 590 people and recorded ₹1,090 crore gross written premium for FY ending March 2016. Sixty-eight technology colleagues worked within ₹14.2 crore annual operating expense under the CIO. The role required me to explain enterprise readiness to people who depended on the service rather than its individual components. In 2019 I described a database restore as successful recovery, only to find forty-eight of 240 invented tasks could not retrieve attachments. The broader retest produced 231 passes and nine still assisted. I keep the mistake visible because experience did not stop me from giving a valid technical result too much meaning. The correction strengthened my expectation that a readiness statement should describe the work exercised and the limitation still present, with its continuing support cost.

Reason for the move

Promoted to CIO in January 2021

Mandate

Make authorised insurance work usable through dependable enterprise platforms

Outcomes

• Moved from distribution integration into insurance systems
• Learned the professional decisions represented by platform records
• Connected technical delivery with operating and specialist requirements

Decisions in context

I joined Nevqemzi in September 2008. The 320-person insurer recorded ₹410 crore gross written premium for FY ending March 2009. Thirty-seven technology colleagues worked within ₹6.4 crore annual operating expense under the CIO. The move required learning how insurance professionals interpreted the records our systems presented. A technical status could describe a process without settling coverage or a claims judgement. Underwriting, claims, actuarial and legal colleagues retained those mandates. I learned to ask what authorised work a platform needed to enable and which conditions the interface should preserve for the person using it. My integration background helped with dependencies, but the new sector required more than connecting systems correctly. It required understanding the professional meaning carried through those connections and resisting the temptation to simplify that meaning merely because one representation was easier to implement.

Reason for the move

Promoted to head of IT in April 2015

Mandate

Connect technical exchanges with the work expected by the receiving process

Outcomes

• Accepted team responsibility after systems-analysis experience
• Examined dependencies beyond a successful technical response
• Built the integration judgement used in the later insurance-platform role

Decisions in context

I became integration lead in July 2004. Vezqenmi had 210 employees and ₹67 crore revenue for the financial year ending March 2005. Twenty-four colleagues worked within ₹1.8 crore annual operating expense under the technology head. The role brought responsibility for exchanges between systems whose owners understood completion differently. A response could confirm that one component had accepted a message while the receiving colleague still lacked something necessary to continue. I learned to ask who owned the next condition and how the service would explain an incomplete state. That habit later helped in insurance, although the professional meaning of the work required new learning. I left for platform management because I wanted to connect those integration questions with a broader enterprise service rather than treat each interface as an isolated technical achievement.

Reason for the move

Joined Nevqemzi as platform manager in September 2008

Mandate

Understand the work behind system requests and support usable information flows

Outcomes

• Entered employment after computer-science study completed in May 1998
• Learned to follow a technical response into the receiving workflow
• Developed the foundation for later integration leadership

Decisions in context

I joined Vezqenmi in July 1998 after finishing computer science that May. The ninety-two-person business recorded ₹18.6 crore revenue for FY ending March 1999. I was one of eight technology colleagues under the systems manager, without direct reports or delegated spending. Early assignments involved understanding requests from people whose work did not stop when a screen or connection responded. I learned to ask what they needed next and whether the system result actually supported it. Senior colleagues owned technical approval and operating decisions; I contributed analysis and support within that responsibility. The appointment began a continuous twenty-eight-year career. Its influence remains in my preference for demonstrations that follow a complete task, even when the technology has become more complex and the readiness statement is being made to an executive team rather than a colleague at a distribution desk.

Reason for the move

Promoted to integration lead in July 2004