Learning the work between a commitment and an examination

Mandate

Provide credible field conditions while preserving technical authority and evidence limits

Outcomes

• Resourced equipment withdrawal and differentiated review of earlier reports
• Kept restricted-access scope separate from document completion
• Supported technical priority review and limited work during weather disruption

Decisions in context

I became COO in January 2021. The current remit covers 194 operating colleagues through six heads and ₹42 crore annual expense under Minal Zheqvemi. Arvind Vezqerni owns technical judgement. Teqzenvi has 286 employees across eight offices and ₹138 crore service-fee revenue for FY ending March 2026. Founders hold 50%, an institutional investor 30% and an employee vehicle 20%, including my 0.6%. I have no statutory appointment. Recent decisions required equipment, access, review capacity and revised schedules without transferring engineering conclusions into the operating function. The company remains a pre-loss service provider, not an insurer, broker or loss adjuster. I want the next stage to translate this experience into questions about management's evidence and capacity, while recognising that collective oversight differs from directing a field programme.

Reason for the move

Continuing COO responsibility while preparing for a first outside board contribution

Concurrent appointment

Executive COO appointment only; no statutory board seat.

Mandate

Connect the appointment calendar with the conditions required to examine sites

Outcomes

• Accepted responsibility for a larger network of field assignments
• Corrected thirty-six two-site plans I had approved without adequate travel provision
• Required field and site knowledge to inform revised operating commitments

Decisions in context

I became head of field operations in April 2015. Teqzenvi then employed 231 people and recorded ₹97 crore service-fee revenue for FY ending March 2016. My remit covered 126 colleagues and ₹27 crore annual operating expense under the CEO. The role brought a larger appointment calendar and more responsibility for promises made across sites. In 2018 I approved thirty-six two-site plans whose eight hours of examination left travel outside the account. Correcting them required splitting twenty-three and resequencing thirteen, with ₹46 lakh extra expense. The mistake did not arise from a lack of familiarity with field work; it arose because I accepted a simplified programme despite that experience. It changed the evidence I expected before approval and the responsibility I took for explaining a revised date or cost.

Reason for the move

Promoted to COO in January 2021

Mandate

Arrange a growing service network without confusing scheduling authority with technical judgement

Outcomes

• Moved into a larger pre-loss property-engineering organisation
• Worked with technical leaders on the conditions needed for assignments
• Learned to separate operating completion from the evidence supporting a conclusion

Decisions in context

I joined Teqzenvi in September 2009 as service operations manager. The 173-person company recorded ₹61 crore service-fee revenue for FY ending March 2010. Sixty-three colleagues worked within ₹10.7 crore annual operating expense under the COO. The move expanded my responsibility beyond a regional calendar and required closer coordination with technical leaders. I learned that arranging an appointment did not determine whether the available evidence could support a particular engineering conclusion. Equipment, permissions and the intended scope needed to be considered with the people qualified to judge them. Operations still had a demanding role: it had to make the appropriate work possible and explain where a condition was not yet in place. The experience prepared me for field leadership while giving me a clearer view of the authority I should not assume simply because I owned delivery.

Reason for the move

Promoted to head of field operations in April 2015

Mandate

Bring field knowledge into regional appointment and resource plans

Outcomes

• Took team responsibility after six years of field coordination
• Connected route conditions and site windows with the proposed calendar
• Built the planning experience needed for a wider service-operation role

Decisions in context

In July 2002 I became regional planning manager at Zeqnemri. The firm had 147 employees and ₹34 crore revenue for FY ending March 2003. Twenty-one colleagues worked within ₹2.1 crore annual delegated expense under the operations head. I had to combine local knowledge into a programme that managers and clients could understand. Distance alone did not explain a route, and a stated appointment time did not settle access or the availability of the right equipment. Field colleagues often knew which assumption in the central plan would fail first. I learned to invite that knowledge early, although my later two-site mistake showed that the habit still needed protection under pressure. I moved to Teqzenvi to work across a broader service network and develop the connection between operating plans and technical responsibility.

Reason for the move

Joined Teqzenvi as service operations manager in September 2009

Mandate

Help arrange the people, equipment and access needed for field work

Outcomes

• Entered employment after mechanical engineering study completed in May 1996
• Learned the preparation between accepting an assignment and reaching a site
• Developed a practical foundation for later regional planning responsibility

Decisions in context

I joined Zeqnemri in July 1996 after completing mechanical engineering that May. The sixty-four-person firm recorded ₹9.6 crore revenue for the year ending March 1997. I worked under the field operations manager as one of seven coordination colleagues, without direct reports or delegated expense. My early responsibilities concerned the arrangements that allowed qualified people to carry out their work. A site address was only a starting point; access, equipment and the practical sequence still needed attention. Senior engineers owned conclusions, and my task was to support the conditions in which they could gather useful evidence. The role began a continuous thirty-year career. It remains relevant because the same physical questions persist at executive scale, even when a field programme has become a board-paper total and the COO is several steps away from the journey itself.

Reason for the move

Promoted to regional planning manager in July 2002