From the assigned job to the conditions behind delivery

Mandate

Make industrial utility commitments consistent with operating evidence, customer dependencies and qualified authority

Outcomes

• Withdrew an unsupported efficiency interpretation while retaining measured consumption
• Kept unresolved service findings separate from commercial blame
• Narrowed a heat-recovery proposal to its supported next step
• Examined contact acknowledgements without claiming full response readiness

Decisions in context

I became COO in January 2023 and lead eighty-four operating colleagues through four heads. Our five sites serve eighteen industrial clients, with 118 employees and ₹92 crore FY26 service fees across the company. My ₹21 crore FY 2026–27 expense authority excludes electricity purchases and capital approvals. Imran leads the enterprise; Sonal and qualified owners retain engineering methods, safety and acceptance. I have no statutory seat or personal equity. The role required me to connect customer promises with the conditions under which the service could be delivered and assessed. I had to withdraw my own efficiency interpretation, support a joint complaint review, reconsider the useful demand behind an investment proposal and examine a limited stage of the duty response. Those decisions retained uncertainty and cost. They did not make me the technical authority for each operation. A future board contribution would require a different relationship with management, including the discipline to ask for an explanation without prescribing the operating answer.

Reason for the move

Current executive appointment; considering a first outside board contribution

Mandate

Connect individual site commitments with the service account presented across the operating network

Outcomes

• Examined differences between local operating observations and network claims
• Brought customer dependencies into management discussions
• Maintained specialist authority across a broader coordination remit

Decisions in context

The network appointment in July 2016 widened my responsibility from one operating group to three sites serving eleven industrial clients. The company then had eighty-two employees and ₹51 crore annual service fees. Fifty-eight operating colleagues worked through four heads within ₹11 crore non-electricity expense. Director was a functional title, not a statutory appointment. I learned how an apparently consistent network report could conceal differences in customer activity, operating conditions and the part of the service actually observed. Local teams needed enough context to explain those differences rather than merely submit comparable-looking totals. I also had to distinguish a coordination decision from technical approval, especially when a commercial promise involved several owners. The later COO appointment made me responsible for the broader management account presented through the CEO. It did not remove the limits of my engineering authority or turn a larger operating remit into a board seat. I carried forward the habit of asking which dependency a concise result had left outside its frame.

Reason for the move

Promoted to COO in January 2023

Mandate

Deliver the defined site service while coordinating supplier and customer responsibilities

Outcomes

• Learned to examine service conditions across the agreed interface
• Separated operating findings from contractual conclusions
• Developed a continuing-service perspective beyond individual maintenance assignments

Decisions in context

Joining Vezquri in September 2011 changed my relationship with the customer. I moved from a plant-services company into an operator responsible for an ongoing utility service. Vezquri had sixty employees, two sites and six industrial clients, with ₹24 crore service fees for FY ending March 2012. I led thirty-six colleagues through three supervisors within a defined ₹5.4 crore non-electricity expense account. The recurring service promise required attention to conditions on both sides of an agreed interface. A reading at our delivery point could be relevant without explaining every condition reported within a customer's operation. I learned to support joint examination while preserving access permissions and the responsible technical owners' authority. Commercial colleagues retained interpretation of contract terms. Moving into network responsibility meant carrying these distinctions across more sites without assuming that a similar report heading made the underlying situations identical. The experience later helped me recognise when an unresolved service question was being closed too quickly through a convenient allocation of blame.

Reason for the move

Promoted to lead network operations

Mandate

Coordinate regional service capacity with agreed customer work and appropriate technical authority

Outcomes

• Connected service promises with available responsibility and access
• Distinguished a contact response from completed field work
• Developed management experience beyond individual engineering assignments

Decisions in context

I became regional service manager in June 2004 after nearly seven years in engineering assignments. Nelzavi had 160 employees and ₹33 crore company revenue for FY ending March 2005. Twenty-eight colleagues worked through three supervisors, with ₹3.6 crore annual function expense and separate approval for larger commitments. The role made me responsible for coordinating the conditions behind a service promise rather than only completing my assigned technical work. Knowing an experienced person's telephone number was useful, but it did not establish that the person was available, authorised or able to reach the relevant site. Customer access and the agreed work scope also mattered. I learned to respect those dependencies when commercial urgency encouraged a simpler account. Joining Vezquri offered the opportunity to remain accountable for a continuing service rather than a sequence of assignments. The earlier coordination experience remained relevant, particularly when later duty-contact discussions risked treating an acknowledged message as evidence of a complete operating response.

Reason for the move

Joined an industrial utility operator to take continuing site responsibility

Mandate

Perform assigned engineering work under the relevant technical, safety and customer-site arrangements

Outcomes

• Learned to describe observed conditions without overstating their explanation
• Worked within assigned competence and approval limits
• Developed an interest in the management dependencies behind field delivery

Decisions in context

I completed mechanical engineering at Javqeri Institute of Engineering in June 1997 and joined Nelzavi the following month. I was one member of a six-person group, without staff responsibility or independent spending authority. The company employed seventy-five people and recorded ₹12 crore revenue for FY ending March 1998. Senior colleagues defined and reviewed my assigned work, and customer-site arrangements remained part of the conditions under which it could be performed. I learned early that an observation could be accurate without settling the whole explanation for a customer's reported problem. I also saw how scheduling, access and communication could affect delivery alongside engineering competence. Those experiences drew me towards service management, where I could help coordinate the dependencies rather than assume another team would resolve them. Promotion widened my responsibility but did not erase the need for qualified review. That distinction has remained useful whenever an executive title might tempt me to treat technical authority as an automatic part of management seniority.

Reason for the move

Promoted to regional service management