Owning the consequences after the release milestone

Mandate

Make manufacturing business systems maintainable, supportable and testable beyond their initial delivery

Outcomes

• Reassessed the current need for inherited customisations
• Verified software rebuildability within authorised arrangements
• Replaced copied contact data while reporting test-coverage limits

Decisions in context

I lead eighteen colleagues through three heads, with ₹5.1 crore annual operating expense and a separate ₹2.4 crore capital allocation. The remit includes applications and continuing IT services across our office and production site. I work with business owners to decide which custom behaviour remains necessary and with suppliers to test the evidence behind continuity arrangements. I also own the quality of the account brought to the CEO when a build or test exercise leaves unresolved conditions. Product performance and operating acceptance remain with qualified specialists. I hold no shares or statutory seat, so invited board presentations are described as executive exposure. The role requires me to connect technical evidence with a decision about cost, dependence and ongoing responsibility, rather than present a completed project milestone as proof that every future obligation has been addressed.

Reason for the move

Current role; interested in manufacturing technology leadership and a compatible first outside board contribution

Mandate

Coordinate applications, infrastructure and continuing technology support

Outcomes

• Brought application ownership into upgrade planning
• Recorded recurring supplier and component dependencies
• Connected service support with the business processes it sustained

Decisions in context

The head-of-IT role widened my responsibility beyond applications to the continuing services that supported them. Thirteen colleagues worked through two leads, with ₹3.6 crore annual expense and ₹1.4 crore approved programme capital. Business managers wanted upgrades to preserve familiar behaviour, and I sometimes accepted customisation as the quickest way to obtain agreement. That avoided a difficult discussion during delivery but left a continuing support obligation. I began recording owners and dependencies more explicitly, though the later review showed that the business purpose of some modifications had still become unclear. Reporting to finance taught me to distinguish the cost of a change from the cost of carrying it forward. The CIO appointment made me responsible for bringing those implications directly to enterprise leadership, including the consequences of decisions made under my earlier remit.

Reason for the move

Appointed CIO with direct reporting to the chief executive

Mandate

Support business applications through changing processes, staff and supplier arrangements

Outcomes

• Documented owners for requested application changes
• Connected maintenance work with business-process explanations
• Built experience of responsibilities continuing after implementation

Decisions in context

Moving inside the manufacturer changed my view of completion. Seven colleagues supported applications within ₹1.5 crore annual expense, and the work continued after a release had been accepted. A manager who requested a feature could leave while its code remained, and a supplier could change the team assigned to support it. I asked whether the receiving colleagues could explain the behaviour and identify the assumptions behind it. Commercial and finance users helped define the business need; engineering and quality retained product-related decisions. I learned that useful maintenance documentation needed more than a technical description of a field. It needed the reason the company relied on that behaviour and the person authorised to reconsider it. The experience prepared me for wider IT leadership by making the long-term consequences of a convenient implementation choice visible in ordinary support work.

Reason for the move

Promoted to enterprise IT management

Mandate

Coordinate requirements, testing and handover for business-software implementations

Outcomes

• Recorded reasons for requested custom behaviour
• Made handover assumptions visible to receiving teams
• Coordinated testing with customer process owners

Decisions in context

I coordinated eight colleagues with ₹92 lakh annual team expense, while clients retained their own investment and process decisions. A release date could encourage everyone to resolve disagreement by reproducing the existing screen. That sometimes protected a necessary practice and sometimes deferred a conversation about whether the practice still served the business. I began recording the reason and owner beside a custom request, then using that account during testing and handover. The habit was not yet consistent enough, and some choices remained dependent on the original team's memory. I learned to distinguish a supplier's completion milestone from the customer's ability to maintain the result. Joining an internal applications team let me take responsibility for that later period instead of leaving at the point when another group inherited the consequences and had to make the next change.

Reason for the move

Joined Pervqathi to own continuing internal application responsibility

Mandate

Prepare requirements and test cases from understood business actions

Outcomes

• Traced requested screen behaviour to user explanations
• Prepared test cases for senior review
• Learned the distinction between a request and authorised process change

Decisions in context

I joined after computer-engineering studies and worked in a six-person delivery team without direct reports or spending approval. My task was to understand the business action behind a requested screen and prepare requirements and tests for review. A user could explain the steps they followed without knowing why an earlier design had made those steps necessary. I learned to ask for the purpose, though I sometimes accepted familiarity as sufficient because the project needed to move. Senior colleagues held design and commercial decisions. That early experience gave me an interest in the assumptions passed from one team to another and in the tests that show whether the intended behaviour survives a change. Promotion added responsibility for coordinating people and delivery resources, while leaving the customer's authority over its own process distinct from my role as an implementation supplier.

Reason for the move

Promoted to implementation leadership