From thermal project records to an installed-product commitment

Mandate

Connect product evidence, application boundaries and installed support life with enterprise investment decisions.

Outcomes

• Replaced a ₹3.2 crore broad tooling proposal with a ₹1.1 crore limited stage that retained the prototype's added 180 kilograms.
• Supported a seal-material change with ₹54 lakh programme cost, ₹2,400 additional cost per body and a twelve-week delay.
• Distinguished seventeen current monitoring values from six held last readings in a selected review.
• Funded a controller transition whose forty-four-unit pilot recorded thirty-one completions and thirteen pending reviews.

Decisions in context

The CTO remit brings product development, monitoring and long-term support into the same enterprise conversation. I lead four engineering leads and their teams, with research and change work included within the stated annual expense. Recent decisions have required me to retain costs that a single performance measure can obscure: body mass, recurring material expense, visible monitoring gaps and the work of supporting installed configurations. Leena and Joseph retain their enterprise and operating roles, while qualified owners make the relevant product and vehicle approvals. I want the engineering account to show what the evidence supports and what still needs a decision. The role has strengthened my ability to discuss a technically attractive proposal without treating its benefit as the whole business case. It has also made the customer's installed life a central part of development, rather than a service question considered only after manufacture.

Reason for the move

Current technology-leadership responsibility; exploring a first company-board contribution.

Mandate

Lead product development and connect demonstration evidence with the intended commercial offer.

Outcomes

• Led twenty-two colleagues within ₹3.9 crore annual expense.
• Accepted responsibility for a fifteen-minute load-ready description based on an air measurement.
• Withdrew the broader claim after retaining the seventy-three-minute thermal-mass observation.
• Supported ₹58 lakh of redesign and qualification with the actual application boundary explicit.

Decisions in context

As head of engineering I became responsible for a larger product programme and the claims made from its evidence. The 2018 demonstration exposed a mistake in my own judgement. I had supported a load-ready description even though the shorter measured time concerned air, while an instrumented thermal mass took longer under the defined exercise. Withdrawing the proposition required more than a technical correction because commercial colleagues had already prepared to explain it to customers. I learned to place the intended use beside the measured quantity before deciding what a result could support. The later offer retained its application boundary and the responsibilities of qualified customer and product owners. This period shaped my approach to technology leadership: a convincing demonstration should create a more precise question, not pressure the enterprise to defend a promise that its evidence has not established.

Reason for the move

Appointed CTO with broader product, monitoring and installed-support responsibility.

Mandate

Develop body designs with the intended load, vehicle and service conditions in view.

Outcomes

• Managed twelve colleagues within ₹1.8 crore annual expense.
• Brought thermal, mass and service questions into product-development discussions.
• Worked with qualified application owners while keeping the manufacturer's role distinct from carrier or cargo certification.

Decisions in context

Joining Tazqerwi brought me closer to a complete engineered product and its life after delivery. A refrigerated body had to fit the intended vehicle and load while remaining maintainable under the customer's actual service conditions. I led twelve colleagues and reported to the head of engineering. The work required a clearer distinction between a component property and the behaviour of the assembled product in a defined use. I learned to involve operating and qualified application owners before a convenient development assumption became part of the design. My responsibility was the product-engineering team within the stated expense, not approval of every vehicle or cargo. The role gave me a broader view of the dependencies around thermal work and prepared me to lead programmes in which manufacturing, commercial and service consequences needed to be discussed together.

Reason for the move

Promoted to lead engineering across the product programme.

Mandate

Connect technical proposals with the manufacturing and service conditions of the customer application.

Outcomes

• Led six colleagues within ₹48 lakh annual team expense.
• Kept assessment conditions attached to technical recommendations.
• Escalated application questions that extended beyond the supplier team's authority.

Decisions in context

The project lead role added responsibility for a team and for explaining the consequences of its recommendations. I worked under the engineering director and coordinated six colleagues across regional assignments. A change could improve a measured property while adding a requirement elsewhere, such as a manufacturing variation or a different service arrangement. I learned to keep those consequences in the proposal rather than assume the customer would absorb them after accepting the technical result. The work also showed the limits of a supplier assignment: some questions could only be settled by the owner of the complete application. I became interested in a role where I could follow those dependencies for longer and understand the installed product. That interest led to Tazqerwi, where thermal design would become one part of a wider vehicle-body responsibility.

Reason for the move

Joined a vehicle-body enterprise to follow product decisions through manufacture and support.

Mandate

Prepare and interpret technical records within the conditions and authority of the assigned project.

Outcomes

• Joined after completing the mechanical-engineering degree in May 2000.
• Supported measurements and technical records under a project engineering manager.
• Kept unresolved application questions visible rather than extend a component result beyond its evidence.

Decisions in context

I began in July 2000 with supervised thermal-engineering work and no delegated budget. The immediate task was to understand a measurement well enough to explain what it represented, including the conditions attached to it. I prepared records, examined reported behaviour and helped the project manager identify questions that required further work. A technically useful result did not automatically settle the customer's complete application, and I had no authority to certify it. That distinction became a foundation for later responsibility. I learned to resist the temptation to supply a broader answer merely because the available number was clear. The early role was modest in organisational scope, but it established a habit of keeping the evidence and its limits together. It also taught me that asking a precise question can be more valuable than presenting a confident conclusion too early.

Reason for the move

Promoted into project leadership with a small engineering team.