From implementing the rule to answering for its meaning

Mandate

Preserve business meaning, usable service and accountable ownership across the enterprise information estate.

Outcomes

• Examined whether a deposited source archive supported a practicable maintenance route.
• Retained unsuccessful portal tasks and an assisted route after a bounded usability review.
• Moved an enterprise change away from a conflicting finance deadline.
• Supported a priced and bounded customer-interface retirement extension.

Decisions in context

The CIO appointment brings thirty-eight employees through five leads and coordination of nine external specialists. I report to the CEO, with ₹5.6 crore annual operating expenditure and a separate ₹2.4 crore change programme. The enterprise's seven plants have 31 MW thermal cooling capacity, not electricity-generation capacity, and their engineering authority remains outside my remit. My cases focus on the business proposition carried by information services: what a deposited archive enables, whether a customer can finish a task and what a receiving team needs before a change proceeds. The company records ₹78 crore FY 2026 revenue; that figure is not my budget. I hold 0.3% of total equity within the employee vehicle and no statutory seat. A possible outside role would require an appointment-specific relationship and capacity review rather than treating senior executive responsibility as evidence of independence.

Reason for the move

Current appointment; considering a first outside contribution after preparation and relationship review.

Mandate

Develop enterprise platforms with a clear account of the business decisions represented by their interactions.

Outcomes

• Accepted responsibility for approving a receipt labelled as a confirmation.
• Separated accepted requests from pending business decisions in the corrective account.
• Retained later dispositions and the cost of redesign without claiming cooling delivery.

Decisions in context

I led twenty-six employees and coordinated six external specialists with ₹4.2 crore annual function expenditure. Director was a functional title and did not include a statutory appointment. In 2018 I approved a request interface whose confirmation message represented technical receipt, while a customer could reasonably read business acceptance into it. The later ninety-six-request review showed seventy-four accepted and twenty-two still awaiting a decision. I retained my part in that approval instead of describing the correction as somebody else's wording mistake. The response included ₹46 lakh of review and redesign, with qualified business owners assessing the implications of the earlier messages. The role taught me to ask who could make the promise a system appeared to communicate. That lesson informed the broader CIO remit, but the later promotion did not remove the original failure from my account.

Reason for the move

Appointed CIO with broader responsibility for enterprise information services.

Concurrent appointment

Director denoted the enterprise-platform function; no statutory board seat was held.

Mandate

Connect enterprise applications to commercial and administrative responsibility as the service business developed.

Outcomes

• Established closer discussion between application owners and receiving business teams.
• Separated enterprise-system responsibility from engineering control.
• Developed a clearer account of change requirements before the platform director appointment.

Decisions in context

Joining the cooling-services business moved my work closer to the consequences of a continuing customer relationship. The company then had 118 employees and ₹21 crore FY 2009 revenue, with a smaller portfolio than the seven plants described today. I led seventeen systems colleagues with ₹2.7 crore annual expenditure. The work required discussion with commercial and administrative owners about what an application event meant in their process. I was responsible for the business systems, not for plant control or engineering acceptance. That boundary mattered because a customer-facing record could concern a service whose delivery required decisions outside the technology function. The appointment broadened my understanding of enterprise responsibility without making me an operating engineer. It also exposed the difference between deploying a change and giving its receiving team the time, explanation and practical route needed to use it.

Reason for the move

Promoted to direct enterprise platforms as responsibility broadened.

Mandate

Coordinate application delivery and support around business requirements and the receiving team's ability to use a change.

Outcomes

• Developed people and expenditure responsibility beyond individual development work.
• Brought business deadlines into application change discussions.
• Learned to examine the meaning of a completion claim across functions.

Decisions in context

The applications-manager appointment introduced responsibility for twelve colleagues and ₹1.6 crore annual function expenditure. The employer's 220 employees and ₹67 crore revenue described the wider enterprise, not the size of my remit. I worked with business owners whose reporting cycles and service commitments did not necessarily fit a technology release calendar. A technically finished change could still ask a receiving team to absorb work at the wrong moment. I learned to make that dependency visible before describing the programme as ready. The role also required a clearer account of what support would remain after initial delivery. I wanted to follow those questions within an operating enterprise rather than only through discrete application assignments. The September 2008 move offered that perspective and a broader team, while keeping engineering and commercial authority with their respective owners.

Reason for the move

Moved into a cooling-service enterprise to carry responsibility for the continuing business use of systems.

Mandate

Turn an agreed business requirement into a precise and supportable application behaviour.

Outcomes

• Learned to clarify what a user meant by a completed process.
• Developed discipline in explaining rules and exceptions to an application lead.
• Built practical experience before taking responsibility for a delivery team.

Decisions in context

I began work in June 1992, after completing the computer-science degree in May. The first employer had eighty-four people and ₹14 crore FY 1993 revenue. As an individual developer under an application lead, I had neither a staff remit nor spending authority. I learned to ask what the person requesting a feature meant by apparently familiar words such as received, accepted or complete. Those distinctions affected the rule the application implemented and the expectation its response created. The work also taught me to explain an exception before hiding it inside a technical solution. I did not yet carry the broader business accountability of my later roles. Retaining that limited scope makes the subsequent progression more credible and also exposes a useful contradiction: understanding precise language early in a career did not prevent me from approving an imprecise customer confirmation years later.

Reason for the move

Promoted into applications management after sustained development and coordination experience.