The scope carried from analysis into the boardroom

Mandate

Align the engineering-technology offer with its rights, evidence, capacity and acceptable commercial commitments

Outcomes

• Launched 41 cleared models from a 64-asset review and reduced the associated forecast
• Corrected an overbroad service description I had approved and supported agreed customer adjustments
• Deferred laboratory ownership, withdrew an unsupported portfolio claim and declined restrictive exclusivity

Decisions in context

The CEO and executive-director appointment began in April 2020. I lead six executive heads and report to the board, with responsibility for the company P&L and the approved capital programme within its reserved-decision arrangements. CFO Devika Qavzeni and CTO Omar Zeqvani retain their professional remits. The cases describe choices that altered the offer rather than merely improve an execution measure: a smaller library, corrected service terms, deferred ownership, further measurement and an exclusive proposal declined. My own approval of the early connected-service material belongs in that record. The role requires me to make the commercial, technical and financial accounts describe the same enterprise commitment. I hold one executive statutory seat, not an outside independent appointment. Preparing for another board would require a different contribution, relationship assessment and enough capacity alongside these responsibilities.

Reason for the move

Continuing enterprise leadership while assessing one possible outside board contribution

Concurrent appointment

CEO and executive director of the same company; one statutory seat, not two appointments

Mandate

Connect commercial commitments with specialist people, facilities and credible delivery windows

Outcomes

• Brought the timing of demand into operating-capacity reviews
• Separated company capability from availability for a specific client commitment
• Developed the enterprise perspective used in later capital and scope choices

Decisions in context

As COO I led 220 colleagues through four operating heads and reported to the CEO. The ₹64 crore annual operating expense described my remit within a company recording ₹108 crore FY 2014 revenue. I had to reconcile several client programmes that competed for specialist attention and facilities. A capability listed in a company presentation could be real while unavailable during the week a customer required it. I learned to ask how a commercial promise would meet the actual schedule, including the work of people whose names disappeared inside an aggregate capacity figure. The role also required attention to the limits of our service: we could provide analysis and technology without acquiring a client's equipment-approval authority. Those lessons prepared me for enterprise leadership, where the decision might be to change the offer or defer an investment rather than ask operations to absorb every mismatch.

Reason for the move

Appointed CEO and executive director in April 2020

Mandate

Build a delivery function that preserves the purpose and responsibility attached to engineering work

Outcomes

• Combined multiple client programmes into one capacity account
• Connected technical scope with commercial and rights review
• Developed service leadership beyond individual simulation projects

Decisions in context

Moving to Zevruni in September 2007 brought me from Cuttack to Vadodara and widened responsibility from projects to a service function. Forty-two colleagues worked through three leads within ₹7.2 crore annual expense, reporting through me to the COO. I needed to understand how several technically sound assignments could create a difficult operating portfolio when their demands coincided. I also learned to preserve the purpose and rights attached to work as it moved between teams. A familiar model could be useful elsewhere without every element being available for another customer. Qualified technical and legal owners remained necessary to that assessment. The function's role was to make the service deliverable and its boundaries explicit, not to turn engineering confidence into a claim of unlimited reuse or client approval authority. That broader view prepared me for the operating remit that followed.

Reason for the move

Promoted to COO in June 2013

Mandate

Deliver defined simulation work while preserving assumptions and the scope of the promised conclusion

Outcomes

• Added people and expense responsibility to analytical work
• Made changes in intended use visible in project discussions
• Learned to examine commercial scope before treating an extension as routine effort

Decisions in context

Project management added fourteen colleagues, two leads and an annual expense allocation under the engineering director. I had to explain why work that looked like a small extension could require a different assessment when its intended use changed. A calculation prepared to compare alternatives did not automatically support every later decision a client might wish to make. The team needed a clear record of the question, inputs and assumptions, while commercial colleagues needed to understand the work implied by a broader promise. I also began to notice rights questions when earlier client material appeared attractive for another assignment. My role was to identify those issues and reach the qualified owners, not settle them by personal confidence. Leading projects in that way prepared me to manage a service portfolio rather than treat each engagement as an isolated technical exercise.

Reason for the move

Joined Zevruni to lead a broader engineering-services function in September 2007

Mandate

Prepare supervised mechanical analysis with assumptions and intended use recorded

Outcomes

• Applied the mechanical-engineering degree to defined analytical tasks
• Learned to distinguish numerical precision from a broader supported conclusion
• Built the technical foundation for later project responsibility

Decisions in context

I joined the five-person project group in July 1994, immediately after completing mechanical engineering that June. Under a senior analysis engineer, I prepared calculations and simulation material without people or spending authority. The work taught me to begin with the question a model was intended to answer. A result could be internally consistent while depending on conditions unlike those in the customer's eventual application. Recording those assumptions was part of making the analysis useful, not an optional caution added after the interesting number. I did not have authority to release client equipment or certify its performance. My responsibility was to prepare work that the qualified decision-makers could examine on its actual basis. Later commercial and leadership roles added other questions, but the early habit remained: understand what the evidence supports before allowing the confidence of its presentation to widen the claim.

Reason for the move

Promoted to simulation-project manager in April 2001