Following the consequence after the application handover

Mandate

Preserve operating meaning through disconnection, integration and supplier transition

Outcomes

• Reconciled selected disconnected events without recording new physical activity
• Exposed two business-function dependencies in a supplier-exit rehearsal
• Kept qualified operating decisions separate from technical completion

Decisions in context

The CIO role widened my responsibility from running applications to explaining what the enterprise could rely on when their familiar context changed. Roshan owns operations and Ajay retains enterprise authority. The disconnected-work exercise required my team to preserve earlier events when their records arrived later. The supplier rehearsal required us to test business functions rather than infer independence from exported files. In both cases I had to explain the limits alongside the positive technical result. Three leads coordinate 23 colleagues within the continuing information function. I want operating owners to recognise the account the system supplies and know which question it has not answered. The work should make their decisions easier to evidence without allowing IT to assume technical suitability or commercial authority simply because a programme has reached its own completion milestone.

Reason for the move

Current CIO appointment; preparing for a potential first outside-board role

Concurrent appointment

Enterprise information employment without a statutory appointment

Mandate

Combine systems without discarding the operating distinctions they carry

Outcomes

• Approved the local-number import later requiring correction
• Led an eight-week review of 24 selected physical devices
• Preserved earlier references while establishing distinct equipment identities

Decisions in context

The equipment import tested a principle I should already have understood. Local numbering worked within separate contexts, but I approved its use as a shared enterprise identity. Six numbers had each described two devices, and the selected import collapsed 24 physical items into 18 records. We spent ₹37 lakh over eight weeks repairing the identity account and preserving the earlier references needed to interpret history. That correction did not establish whether any device was suitable for use. Qualified owners retained that decision. The experience made me more careful about an integration that appears successful because it produces a cleaner view. I had to ask whether the operating subject had survived the change. Promotion widened the situations in which I was responsible for that question, including interrupted work and supplier arrangements whose technical success could conceal an unresolved business dependency.

Reason for the move

Promoted to CIO with enterprise-wide information accountability

Concurrent appointment

Enterprise information employment without a statutory appointment

Mandate

Follow application decisions into the continuing operating account

Outcomes

• Connected system records with the equipment and events they described
• Worked with operating owners on the limits of technical status
• Retained business decisions outside implementation authority

Decisions in context

Moving into an operator changed what happened after an implementation handover. I could see how colleagues used the record in continuing work and which assumptions became embedded in a familiar screen. A complete field could look like an operating approval even when it only established that the application had accepted a value. I worked with Roshan’s colleagues to keep those meanings separate. Sixteen people and ₹2.8 crore annual expense gave me a defined systems remit, not responsibility for vehicle or charging suitability. This period matters because it shows that the later equipment-identity mistake did not arise from an entirely new problem. I had already seen how a technically consistent account could be misunderstood. The larger role required me to apply that lesson when integration seemed convenient and the enterprise wanted a single view.

Reason for the move

Promoted to lead the wider IT function

Concurrent appointment

Enterprise information employment without a statutory appointment

Mandate

Understand the receiving context before combining client records

Outcomes

• Examined where departmental identifiers were actually unique
• Asked operating owners to explain the subject of shared fields
• Kept client approval distinct from technical implementation

Decisions in context

Clients often wanted separate departmental applications to become one coherent system. The request sounded technical, but the difficult questions concerned meaning. A field could be unambiguous within one team and ambiguous when another team began to rely on it. I learned to ask the receiving owner what the record described and which decision it was meant to support. Eleven colleagues worked within ₹1.5 crore annual expense, while client owners retained their operating authority. We could implement an agreed design without becoming the people authorised to decide every business consequence. I wanted to follow those consequences for longer than a project assignment allowed. Joining Derlashi gave me continuing responsibility for the systems account, including the uncomfortable possibility that a design I had accepted would need correction after users had begun to treat it as established fact.

Reason for the move

Joined an operator to retain responsibility after the project handover

Concurrent appointment

Enterprise information employment without a statutory appointment

Mandate

Help users explain the mismatch between a system field and their intended work

Outcomes

• Recorded user questions before proposing an application change
• Escalated conflicting interpretations to authorised colleagues
• Learned to separate consistent data from a supported business meaning

Decisions in context

I joined the support group the month after completing computing studies. Eight people helped users describe application problems and passed changes to authorised colleagues. I did not own a budget or approve client business rules. The useful habit was to listen for the meaning a user attached to a field before assuming that the request concerned a faulty screen. Two people could use the same word for different subjects, or rely on a shared number that was only unique in one context. The application could be internally consistent while the work around it remained misunderstood. That experience shaped my interest in handovers: what the next person thinks has been established is part of the system’s consequence. Later responsibility gave me more influence over those assumptions and a greater obligation to explain when my own approval had preserved the wrong one.

Reason for the move

Promoted to lead applications work and a defined practice budget

Concurrent appointment

Enterprise information employment without a statutory appointment