Following the system into the work it supports

Mandate

Make enterprise systems support qualified service decisions with appropriate evidence, access and recovery assurance

Outcomes

• Revised a partner-ranking rule after a sixty-scenario road-context review
• Recovered fifty unreadable attachments while retaining ten pending fresh requests
• Corrected twenty overbroad partner views and held two cases outside access pending review
• Extended recovery testing to a defined working journey, retaining six manual-fallback cases

Decisions in context

I became CIO in February 2021 and report to Mira. Twenty-six IT colleagues work through four leads within₹6.8 crore FY 2026–27 operating expense, with₹2.4 crore separately approved capital. The company employs 284 people and coordinates with 180 independent workshops. Arun leads operations, and qualified owners retain service acceptance, technical work and route decisions. My responsibility includes explaining where a system recommendation or assurance remains incomplete. The route-context programme required me to revisit a rule I had approved. Attachment, partner-view and recovery reviews brought different evidence and owners into the technology account. I hold no personal or vehicle interest, and my executive appointment is not a statutory directorship. A prospective board role would require preparation for collective responsibility and a wider enterprise perspective, not simply another setting in which to make the same technology decisions. I would bring practical scrutiny of the meaning attached to a favourable system result.

Reason for the move

Continuing CIO responsibility while considering a first external board contribution

Mandate

Connect service applications with telephony, information access and enterprise continuity

Outcomes

• Brought application and telephony dependencies into a wider technology account
• Developed responsibility for common service-platform assumptions
• Supported a distance-based recommendation whose operating limits I later revisited

Decisions in context

The enterprise IT role began in January 2015. Veqmethi employed 176 people, worked with 118 independent workshops and recorded₹71 crore FY 2016 revenue. I led twenty-two colleagues through three leads within₹4.2 crore annual expense and reported to the CEO. The scope extended beyond the main service application into telephony, access arrangements and continuity. I learned to ask how separately managed components supported one working journey. I also gained influence over defaults used across the organisation. The straight-line partner ranking was one I supported because it appeared easy to explain. Its later correction showed that transparency about a calculation does not establish its sufficiency for an operating decision. The role prepared me for CIO responsibility by connecting technical investments with the claims made about the enterprise's service, while leaving actual dispatch and technical work with the qualified operating owners.

Reason for the move

Promoted to CIO with enterprise-wide information responsibility

Mandate

Develop and support the service information platform used to coordinate service requests with operating partners

Outcomes

• Connected application records with the decisions operating colleagues needed to make
• Kept partner availability and technical suitability separate from directory presence
• Developed platform support around the complete service question

Decisions in context

I joined Veqmethi in October 2008 and moved to Kolhapur. The enterprise had seventy-two employees, fifty-two independent partner workshops and₹24 crore FY 2009 revenue. Seventeen IT colleagues worked through two leads within₹1.4 crore annual expense, and I reported to the head of technology. The setting made the limits of a directory entry particularly clear. A listed partner could be geographically nearby without being available or appropriate for a particular request. The platform needed to help operating colleagues understand those distinctions rather than silently convert presence in a system into acceptance of a service. I worked on the relationship between records, the people using them and the decisions they still had to make. The appointment broadened my understanding of technology's operating context and led to responsibility for the enterprise dependencies surrounding the service application.

Reason for the move

Promoted to head of enterprise IT

Mandate

Lead application delivery and support with acceptance connected to users' actual work

Outcomes

• Developed responsibility for working applications beyond service-desk resolution
• Examined the assumptions embedded in common processing defaults
• Connected acceptance questions with the receiving business colleague's task

Decisions in context

In April 2002 I became applications lead at Tevqemi. The company employed 105 people and recorded₹22 crore FY 2003 revenue. Twelve colleagues worked through two leads within₹75 lakh annual function expense, and I reported to the head of applications. The role moved me from recording and routing support questions to responsibility for the applications behind them. I learned that a default could look technically reasonable while leaving an important business choice unresolved. Acceptance therefore needed to include the receiving user's task, not merely a successful transaction or an opened file. I worked with colleagues who could explain the practical conditions under which a result would be useful. The move to Veqmethi followed my interest in carrying that responsibility within a service enterprise over time, rather than examining its operating consequences only through the boundaries of individual client projects.

Reason for the move

Joined a service enterprise to take continuing responsibility for its operating platform

Mandate

Understand, record and route system-support requests to the colleagues authorised to resolve them

Outcomes

• Learned to distinguish a closed support entry from a restored working task
• Recorded uncertainty instead of turning incomplete evidence into a confident update
• Developed a foundation in the relationship between application behaviour and user needs

Decisions in context

I joined Tevqemi in July 1995 after completing my computing degree in June. The company had forty-two employees and₹7.2 crore FY 1996 revenue. I worked in a seven-person support group under the service-desk manager, without reports or spending authority. The work required listening to a caller's account before deciding which technical category might explain it. I learned to record what was known, what remained uncertain and which colleague could authorise the next step. A closed entry could still leave the user's actual task blocked, so I became interested in the relationship between the support measure and the work it was meant to restore. That early perspective did not give me authority over every system decision. It gave me a disciplined way to ask questions and a foundation for the application responsibility I assumed in 2002.

Reason for the move

Promoted to applications lead