From supporting applications to examining what they authorise

Mandate

Make enterprise information services preserve the permissions, relationships and evidence on which the business relies

Outcomes

• Owned the access assumptions carried by a reusable customer workspace
• Separated software usage evidence from commercial entitlement
• Retained incomplete project relationships in the supplier-exit account
• Restricted a research assistant after source review

Decisions in context

I became CIO in January 2022 and now lead thirty-six colleagues through four leads. The company has 310 employees and seven industrial clients, with ₹176 crore FY26 service fees. My ₹6.8 crore operating expense and ₹2.7 crore change programme are defined FY2026–27 responsibilities, not the enterprise's entire expenditure. Rekha leads the business; Yusuf and qualified owners retain engineering, operating and safety authority. I hold no statutory seat or personal equity. The recent decisions required me to examine what systems allowed people to see, buy, transfer or believe. I had to own the customer-workspace permission error and my premature confidence in a research demonstration. Other cases challenged a convenient interpretation of software usage and a migration file count. The results retained expense and unfinished work rather than establish universal success. An external board contribution would require me to use that experience through collective scrutiny, without assuming that another company's technology and operating decisions become mine to direct.

Reason for the move

Current executive appointment; considering one first external board contribution

Mandate

Connect technology purchasing and service transitions with the business's continuing information needs

Outcomes

• Examined the commercial meaning behind technology counts
• Connected supplier transitions with usable project records
• Developed broader responsibility for the evidence in executive technology reports

Decisions in context

The head-of-IT appointment began in July 2016. Vornqemi had 220 employees and five industrial clients, with ₹94 crore service fees for FY ending March 2017. Twenty-seven technology colleagues worked through three leads within ₹4.5 crore annual operating expense. I became more involved in the account surrounding a technical delivery: the requirement behind a purchase, the records a supplier would return and the work remaining after a project announced completion. I learned that an accurate count could still answer the wrong management question. A file total did not necessarily show that users could interpret the transferred record, and a low activity peak did not settle a commercial entitlement. Those were questions to examine with the relevant business and professional owners, not a reason for technology to make every conclusion itself. Promotion to CIO widened my responsibility for how such distinctions reached the executive team and directors, including the assumptions in proposals I had personally supported.

Reason for the move

Promoted to CIO in January 2022

Mandate

Support enterprise records while preserving customer information boundaries and specialist authority

Outcomes

• Learned the continuing information obligations of an industrial service
• Separated a corporate document from permission to operate
• Worked with business owners on the meaning of access and project context

Decisions in context

I joined Vornqemi in September 2009 after thirteen years in project applications. The company had 115 employees, three industrial clients and ₹31 crore annual service fees. Eighteen colleagues worked through two leads within ₹2.1 crore function expense. The move brought me into a business that remained responsible for a service over time, rather than only supplying a system implementation. Customer documents, project records and commercial material could sit beside one another without sharing the same intended audience. I learned to ask who was entitled to use a record and which specialist owned its meaning. A corporate application could help someone find engineering material without authorising the person to act on it. The later head-of-IT remit expanded the scale of those decisions and the supplier relationships involved. It also made me responsible for explaining why a standard technical arrangement sometimes needed a distinct business decision before it could be reused safely in another customer setting.

Reason for the move

Promoted to head of IT

Mandate

Manage application delivery and support with an explicit account of user needs and service obligations

Outcomes

• Connected software requirements with the tasks people needed to perform
• Examined what information should remain usable after a service change
• Developed management responsibility while completing further study

Decisions in context

I became application manager in June 2002. Lorqethi employed 182 people and recorded ₹48 crore revenue for FY ending March 2003. My remit covered fourteen colleagues through two leads and ₹87 lakh annual operating expense. I completed a part-time postgraduate diploma in information systems in November 2003 while continuing in the role. Managing delivery required a more careful account of what the customer had requested and what the proposed service actually included. I could not assume that every user needed the same capability or that a supplier's demonstration explained the conditions of the eventual agreement. I also became interested in what happened after implementation, when a project record had to remain useful beyond the original team. Moving to Vornqemi gave me continuing responsibility inside a service operator rather than a provider's project boundary. The earlier experience remained valuable whenever a later technology purchase or transition was being judged mainly by the appearance of its first successful demonstration.

Reason for the move

Joined a thermal-services operator to own continuing business systems

Mandate

Support assigned applications while referring business permissions and document meaning to their accountable owners

Outcomes

• Learned to distinguish a valid system change from an authorised business action
• Recorded questions that required a project owner's interpretation
• Developed interest in the agreements behind software use

Decisions in context

I completed computer science at Zavqeri Institute of Technology in June 1996 and joined Lorqethi in July. The firm had eighty-four employees and ₹16 crore revenue for FY ending March 1997. I contributed within an eight-person support group, without staff or spending authority. Project managers and technical specialists owned the work represented in the applications. My early lesson was that a status or access request could look straightforward on a screen while carrying a decision the support team was not authorised to make. I learned to explain the technical behaviour and bring the question back to the appropriate owner. That habit was more useful than pretending that familiarity with the application made me competent to settle every disagreement about its contents. Promotion to management gave me a broader responsibility for the service and the people delivering it. It also reinforced the need to preserve the distinction between helping an organisation use its information and assuming authority over every action that information might inform.

Reason for the move

Promoted to application manager