From measuring a component to sponsoring a product

Mandate

Connect product claims and technology choices with supported application conditions

Outcomes

• Bounded camera compatibility to examined configurations
• Compared controller development with qualified supplier alternatives
• Kept unresolved variants visible in executive decisions

Decisions in context

I lead twenty-four engineering colleagues through three leads, with ₹6.1 crore annual expense and ₹2.8 crore separately approved development capital. The remit joins product development, applications judgement and the choice of technology we build or obtain from suppliers. I report to the CEO, while quality retains a separate reporting line and acceptance responsibility. That distinction matters when a commercial opportunity depends on a configuration that is not yet qualified. I need to explain the limitation and support the resources required, rather than let my sponsorship become a substitute for evidence. The controller decision also required me to compare internal development with recurring supplier cost and dependence. I hold no shares or statutory seat. My proposed outside contribution would build on these decisions while recognising that executive technical responsibility and board oversight require different forms of participation.

Reason for the move

Current appointment; open to industrial technology leadership and a suitable first outside board contribution

Mandate

Coordinate product development with application evidence and independent quality acceptance

Outcomes

• Held preproduction units after longer-run qualification failures
• Funded correction and retesting under a stated criterion
• Changed reviews to retain operating conditions beside product claims

Decisions in context

I led eighteen colleagues through two leads, with ₹4.1 crore annual engineering expense and ₹1.7 crore approved development capital. The work connected development activity with the offer commercial teams wanted to make. I sometimes gave a successful demonstration too much weight because the introduction timetable was pressing. The 2019 stability case exposed the consequence: a ten-minute check did not support the longer-run statement I had endorsed. I accepted the hold on preproduction units and funded correction while quality retained release authority. The period taught me to give engineers permission to state what their result did not establish, including when that challenged my own earlier approval. Promotion to CTO widened the task to the technology portfolio and make-or-buy choices, where a technically attractive internal project still had to compete with other ways of meeting the business need.

Reason for the move

Appointed CTO with a wider technology-portfolio mandate

Mandate

Connect lighting behaviour with the camera and process conditions of the intended use

Outcomes

• Recorded examined camera and control combinations
• Separated component observations from application conclusions
• Brought customer operating conditions into development reviews

Decisions in context

The applications role put me closer to the image the customer needed, rather than only the lighting component we supplied. Ten colleagues worked within ₹2.2 crore annual expense. We examined how cameras, controls and operating settings affected the result and referred product and safety questions to the qualified owners. I learned that a light could appear satisfactory on its own while failing to support the intended inspection in a particular combination. The commercial discussion therefore needed a precise account of what had been examined. I also saw how difficult it was for customers to use a long qualification explanation when they needed a clear offer. My task was to make the boundary understandable without erasing it. Moving into engineering leadership let me bring those application questions earlier into development, before the design had become expensive to change or the launch statement had already been agreed.

Reason for the move

Promoted to coordinate development and applications engineering

Mandate

Coordinate design experiments, measurement and changes for industrial lighting products

Outcomes

• Made test conditions explicit in development reports
• Connected design changes with application questions
• Reviewed evidence before recommending broader product statements

Decisions in context

I led eight colleagues with ₹1.4 crore annual team expense, coordinating design work and the measurements needed to understand it. Electronic control was becoming more closely connected with the lighting application, and a component result often raised questions about the equipment around it. I worked with applications colleagues to understand those questions before treating a bench observation as a complete answer. The engineering manager retained final programme authority and the qualified process retained acceptance responsibilities. My role was to organise experiments, examine what changed and explain the evidence supporting the next recommendation. I learned that a test result becomes harder to interpret when the setup is remembered informally rather than recorded. The move to applications leadership gave me a direct opportunity to connect that discipline with the conditions customers actually wanted the lighting to serve.

Reason for the move

Joined Nerqathi for applications leadership in inspection lighting

Mandate

Support circuit development and measurements with traceable test conditions

Outcomes

• Documented the setup behind measured behaviour
• Prepared design observations for senior review
• Learned the limits of an isolated component test

Decisions in context

I started after completing electronics studies and worked in a five-person engineering group. I had no capital or release authority. The work involved circuit support, measurements and explaining observations to a senior engineer who reviewed the next design step. I learned that another colleague needed enough detail about the setup to understand the result, including conditions that had not been varied. A successful check was useful evidence, but its meaning depended on the question being asked. I also saw how easily a concise summary could lose the qualification that made the underlying account accurate. Those lessons were not applied perfectly throughout my later career, as the stability case shows. They nevertheless established the technical habit I returned to when a broader claim needed correction: identify the condition, examine the evidence and keep the remaining question visible.

Reason for the move

Promoted to development-team leadership