Following the application beyond its technical handover

Mandate

Preserve business meaning and document status through corporate-system changes

Outcomes

• Required table relationships to survive document conversion
• Connected source withdrawal with the staff-search experience
• Kept business and professional ownership beside technology acceptance

Decisions in context

Four technology leads coordinate thirty-two employees, while five external specialists are counted separately. The annual operating envelope is ₹5.7 crore and the approved change programme a distinct ₹1.9 crore. I report to the CEO without a statutory appointment. Commercial-services head Nirmala Vazqerli helps connect the technical evidence with the business interpretation. The table programme required more than checking that all figures were present, and the withdrawal exercise required more than removing source files. Both showed how completion could be claimed at one technical boundary while the user’s experience still contradicted the owner’s decision. I ask the relevant business owners to define what must remain true, then make acceptance examine that meaning. Corporate systems do not confer authority over gas operations, contractual interpretation or record-retention decisions; those boundaries remain part of the mandate rather than disappear inside a technology delivery claim.

Reason for the move

Current role; considering corporate-systems leadership and a prepared first non-executive contribution

Concurrent appointment

Executive employment only; no statutory directorship

Mandate

Make corporate-system acceptance reflect the business meaning after transformation

Outcomes

• Withdrew use of affected reminders after a date-conversion error
• Corrected the calendar interpretation with contract owners
• Changed my own release review beyond transfer completion

Decisions in context

I led twenty-four colleagues within ₹3.8 crore annual operating expense. The broader remit included the acceptance of corporate-system changes that several functions depended on. In 2019 I approved a contract migration because its transfer checks looked complete. The receiving display shifted twenty-four of eighty reviewed dates a day earlier after date-only fields passed through timestamp handling. We stopped the affected reminder use and corrected the representation with the contract owners. The display error did not itself amend the agreements, but it could still encourage an inappropriate action. I changed my approval practice to ask what the field meant before deciding that a technically consistent conversion was suitable. Promotion to CIO expanded that lesson to other transformations, where preserved values or completed source actions could similarly fail to preserve the experience the business needed.

Reason for the move

Appointed CIO with enterprise-wide information leadership

Concurrent appointment

No statutory seat

Mandate

Connect application delivery with the owners of contracts, schedules and service records

Outcomes

• Brought business owners into acceptance discussions
• Clarified professional authority behind system records
• Followed applications beyond the supplier handover

Decisions in context

The move into the client organisation gave me fifteen colleagues and ₹2.1 crore annual technology expense. Applications supported contracts, schedules and metering-service administration, but the systems team did not own every professional conclusion represented in those records. I worked with the relevant business functions to define acceptance in terms they could recognise. That required listening when a technically correct explanation did not answer whether the work was usable. The continuing relationship also exposed questions that a supplier handover could leave unresolved: who maintained a document’s status, who interpreted a date and who decided whether a changed presentation still supported the task. I did not always apply those lessons well enough, as the later calendar error showed. This role nevertheless established the shared-ownership approach that I returned to when defining a stronger acceptance standard as a technology head and CIO.

Reason for the move

Promoted to lead the wider corporate technology function

Mandate

Translate business interpretation into acceptance questions the delivery team could test

Outcomes

• Connected application demonstrations with the user’s actual task
• Distinguished technical explanations from business acceptance
• Identified questions that needed continuing client ownership

Decisions in context

Nine developers and analysts worked within ₹92 lakh annual delivery expense. I coordinated their work while the client retained its programme budget and business approvals. The important conversations often concerned a small field or document rather than a large technical feature. Developers could describe precisely how a transformation worked, yet users could still object that the result no longer meant what they expected. I learned to treat that objection as an acceptance question rather than a request for a better explanation of the code. I wanted to follow the applications after delivery, because ownership of meaning continued when the supplier project ended. Joining Zarqevli offered that opportunity and required me to work with the people responsible for the contracts and service records over time, including the changes that would later challenge our original assumptions.

Reason for the move

Moved to the client side to manage continuing business systems

Mandate

Trace visible application results to the meaning of the source fields

Outcomes

• Prepared business forms under technical supervision
• Asked users about assumptions behind ordinary fields
• Learned to distinguish record handling from professional interpretation

Decisions in context

I started in June 1998 after completing computer-science studies. Seven people formed the application group, and my assigned development work carried no authority over a client’s contractual or accounting interpretation. Forms and records seemed straightforward until two users explained the same label differently. I learned to trace a visible result back to its source and ask what the field was supposed to represent. That habit was technical, but it also depended on listening to people whose work the application supported. A successful transformation could be consistent with the specification while still resting on the wrong assumption. Team leadership later required me to help colleagues recognise that distinction before handover. The early experience remains relevant when I ask whether a calendar date, table relationship or document status survives the systems that process it.

Reason for the move

Promoted to application team leadership