From a component drawing to the promise of repetition

Mandate

Make repeatable technical promises depend on the interfaces and later tasks actually supported

Outcomes

• Kept product-generation differences visible in replacement decisions
• Included complete maintenance tasks in development acceptance
• Retained unsupported configurations outside the release account

Decisions in context

Forty-three colleagues work through four heads within ₹8.4 crore annual expense and a separate ₹3.1 crore approved development programme. I report to Renu Zeqvalthi and work with Joseph Qavzerli across the technical practice. The replacement review required us to preserve product-generation differences even when the service catalogue encouraged a simpler family answer. The maintenance review brought later panel access into the earlier design decision. Both depended on a clear account of what the evidence supported and which cases remained held. My beneficial 0.06% holding is included within the employee allocation, and I have no statutory director appointment. Project design, installation and safety permissions retain their qualified owners. A future outside seat would need separate preparation and assessment, with technical leadership contributing to collective scrutiny rather than becoming a substitute for the receiving company’s own professional authority.

Reason for the move

Current appointment; considering technical leadership and a prepared first outside-board role

Concurrent appointment

Technical employment; no statutory directorship

Mandate

Define which assembly configurations the technical evidence permits us to support

Outcomes

• Withdrew the mirrored-connector assumption I had approved
• Kept four configurations held after interface revision
• Changed acceptance to examine the alternatives named in the offer

Decisions in context

Thirty-two colleagues worked within ₹5.9 crore annual expense as I took wider responsibility for the methods behind a repeatable assembly. In 2017 I approved a connector concept whose original orientation fitted but whose mirrored alternatives had not been sufficiently examined. Twelve of twenty agreed bench mock-ups met the criterion; eight did not. We used ₹62 lakh and ten weeks to revise and examine the interface, after which sixteen were supported and four remained held. The cases were development configurations rather than installed-building failures. I changed the acceptance account so an attractive original example could not silently establish every alternative in the proposed offer. Promotion to CTO later extended that discipline across product generations and maintenance tasks, where a familiar appearance or accessible component could create another unsupported assumption about the complete technical proposition.

Reason for the move

Promoted to CTO with enterprise technology responsibility

Concurrent appointment

Technical employment; no statutory directorship

Mandate

Connect component definitions with rearrangement, replacement and later access

Outcomes

• Examined interfaces beyond the first installation view
• Connected technical development with service requirements
• Kept project-specific decisions distinct from product-family descriptions

Decisions in context

I joined with twenty-two engineering colleagues and ₹3.7 crore annual expense. Demountable interiors carried a proposition about future change as well as initial assembly, so the technical account needed to follow rearrangement, replacement and access. A component could meet its drawing while the promised later task still lacked a supported route. I worked with practice colleagues to establish which conditions belonged to the product and which required a project-specific decision. The role made commercial language about modularity more concrete because each apparently simple benefit depended on an interface or sequence that someone had to examine. My later connector error did not come from ignorance of that principle. It came from allowing one persuasive configuration to stand for alternatives that still required their own evidence, precisely when the business wanted a simple and repeatable development story.

Reason for the move

Promoted to Head of Technical Methods

Concurrent appointment

Technical employment; no statutory directorship

Mandate

Keep component versions and fabrication constraints connected before repetition

Outcomes

• Tracked which drawing revision belonged to the reviewed component
• Distinguished naming continuity from physical compatibility
• Raised interface assumptions before production commitments

Decisions in context

Twelve colleagues worked within ₹1.8 crore annual expense as I moved from supervised preparation into design coordination. The work connected component definitions with the conditions under which an assembly would be fabricated and reviewed. A familiar part number could conceal a changed interface, while a clean drawing set could still contain assumptions that had not been reconciled across disciplines. I learned to ask which revision belonged to the actual component being discussed rather than rely only on the name used in the meeting. Joining Drezqalni gave me a continuing responsibility for the consequences after development, including replacement and service. That move also made the customer’s later task harder to treat as someone else’s concern. I wanted the technical account to remain useful after the first assembly had ceased to be the main question.

Reason for the move

Joined an interior-systems enterprise for continuing development responsibility

Concurrent appointment

Technical employment; no statutory directorship

Mandate

Preserve the connection between an individual part and the assembly it must serve

Outcomes

• Prepared drawings under qualified supervision
• Supported component and assembly checks
• Learned to distinguish drawing conformity from intended assembly function

Decisions in context

I joined in June 1991 after completing mechanical engineering the previous month. Seven people formed the engineering group, and I prepared drawings and supported checks under qualified supervision. I did not independently approve client designs. The workshop made interface differences tangible: two acceptable-looking components did not necessarily create the intended assembly when brought together. I learned to ask what the whole arrangement was supposed to do before treating a part-level result as sufficient. The role also taught me to preserve the assumptions behind a drawing so a later reviewer could understand the configuration being discussed. Design coordination expanded those questions across revisions and fabrication decisions. The early lesson remained relevant much later, when my own enthusiasm for a mirrored connector concept caused me to accept a broader assembly claim than the evidence actually supported.

Reason for the move

Promoted into design coordination

Concurrent appointment

Technical employment; no statutory directorship