Following a design through its working life

Mandate

Connect product architecture, repair capability and the return journey with a supported commercial offer

Outcomes

• Replaced a universal proposition with sixteen supported configurations and two explicit exclusions
• Established separate eligibility and release decisions for a corner-repair process
• Retained handling effort alongside measured empty-volume improvement
• Opened nineteen reviewed repair-drawing requests while withholding thirteen

Decisions in context

I became CTO in March 2021 and report to Irfan. Thirty-one engineering colleagues work through four leads within₹5.2 crore FY 2026–27 expense, with₹1.8 crore capital separately approved. Veznoru has 215 employees and₹92 crore FY 26 revenue. Meera leads testing, and qualified product, manufacturing, handling and contract owners retain their approvals. The role connects engineering choices with the range we sell and the service needed after a case leaves the workshop. I revised a universal-case premise I had supported, kept held repairs visible and asked that empty-volume benefits retain their handling cost. My responsibility includes explaining those choices to the board through the CEO. It does not make me a statutory director or confer authority over a customer's instrument. I hold no personal or trust interest. A future board contribution would draw on these decisions while requiring a wider financial, legal and enterprise perspective.

Reason for the move

Continuing technical leadership while preparing for a first external board contribution

Mandate

Develop case families with the repair and return requirements of the rental business in view

Outcomes

• Brought rental-return observations into product-development discussions
• Connected product variation with stock and service requirements
• Developed an engineering account of repairability beyond component replacement

Decisions in context

The head-of-product-engineering appointment began in June 2015. Veznoru employed 162 people and recorded₹61 crore FY 2016 revenue. Twenty-three colleagues worked through three leads within₹3.6 crore annual expense, and I reported to the CEO. The wider scope required me to understand the rental business around the physical case. A product could perform its outward role yet create awkward repair or empty-return work. I brought those observations into development rather than treating them as questions to be solved after release. That did not transfer rental or transport authority to engineering. It made their requirements part of the technical proposal. I also learned how a shorter catalogue could conceal meaningful differences between customers' equipment. The experience prepared me to take CTO responsibility with a more complete view of the product's working life and the commercial assumptions attached to its design.

Reason for the move

Promoted to CTO with enterprise technical responsibility

Mandate

Develop reusable case designs with testable requirements and a clear account of intended contents

Outcomes

• Connected returned-product observations with development questions
• Distinguished visible damage from qualified assessment of the complete case
• Made intended equipment configurations explicit in design discussions

Decisions in context

I joined Veznoru in September 2009 and moved to Hubballi. The company had seventy-eight employees and₹19 crore FY 2010 revenue. Fourteen engineering colleagues worked through two leads within₹1.5 crore annual expense, and I reported to the technical director. Reusable cases offered a longer relationship with the product than the component projects I had previously known. A returned case could reveal questions about its use, but a visible mark was not a complete explanation of what had happened. I learned to ask qualified colleagues how the condition should be assessed and what the observation could legitimately tell development. The role also brought the intended contents into the design conversation. Similar outer dimensions did not establish identical support requirements. That combination of physical evidence and clear limits became a foundation for the broader engineering responsibility I assumed in 2015.

Reason for the move

Promoted to head of product engineering

Mandate

Lead product-family development while keeping customer variation and manufacturing requirements explicit

Outcomes

• Examined the commercial and technical consequences of combining product variants
• Connected drawing acceptance with manufacturing and inspection needs
• Developed responsibility for engineering choices beyond individual component work

Decisions in context

In April 2003 I became product-engineering lead at Qevnali. The enterprise employed 118 people and recorded₹24 crore FY 2004 revenue. Eleven engineers worked through two leads within₹92 lakh annual expense, and I reported to the head of engineering. I moved from responsibility for my own drawings to choices affecting a product family. Common parts could make purchasing and production easier, but the uncommon requirement still needed an answer. I learned to examine whether a proposed simplification removed unnecessary complexity or merely moved it to a customer or receiving workshop. Manufacturing and inspection colleagues helped make that distinction practical. I chose the move to Veznoru because I wanted to follow a physical product through a longer working life, including its returns and repairs, rather than assess my contribution primarily at the point when the original design package was handed over.

Reason for the move

Joined a reusable-product enterprise to follow designs through repeated use

Mandate

Translate agreed mechanical requirements into drawings that could be manufactured and inspected

Outcomes

• Learned to connect a drawing with the work of its receiving workshop
• Recorded unresolved requirements before treating a design as complete
• Built a foundation in manufacturing and inspection questions

Decisions in context

I joined Qevnali in July 1997 after graduating in June. The company had forty-two employees and₹8.1 crore revenue for FY 1998. I worked in an eight-person design group under its manager, without reports or delegated spending. My task was to develop drawings from agreed requirements and respond to the questions raised by manufacturing and inspection colleagues. I learned that a complete-looking document could still leave the receiving person unsure about the intended use or acceptance of a part. Asking that question early was more useful than defending the drawing after the ambiguity reached the workshop. This was an individual engineering role, not authority over the company's production or commercial decisions. It gave me a practical foundation in how design information becomes physical work, and prepared me to lead a small product-engineering team from 2003.

Reason for the move

Promoted to product-engineering lead