Chief Technology Officer / India
The held configurations belonged beside the successful result
- Technology and methods colleagues
- 43
- Four heads; company headcount 342
- Annual technical function expense
- ₹8.4 crore
- Separate approved development programme ₹3.1 crore
- Fabrication, methods and technology
- 35 years
- Continuous progression from June 1991
Decisions & consequences
012017 — Withdrawing the mirrored-connector claim I had accepted
I approved a connector concept for a demountable interior assembly after the original orientation showed the intended fit. The proposal extended that conclusion to a mirrored arrangement. I had accepted the visual symmetry as if it established the same interface behaviour, without sufficient examination of the alternative configurations. Joseph’s practice team asked us to test the full claim rather than repeat the most persuasive demonstration.
Twenty agreed bench mock-ups were examined against the defined fit criterion. Twelve met it and eight did not. These were controlled development assemblies, not reported failures in occupied buildings. The commercial sponsor wanted to retain the wider release description while the remaining details were adjusted. I decided that the unsupported configurations should stay outside release because the evidence did not yet justify the promise being made for them.
The revision and examination used ₹62 lakh and ten weeks. The interface design changed, and sixteen of the twenty defined mock-ups then met the criterion. Four remained held for further development. The improvement did not establish that every conceivable mirrored arrangement was now supported. We retained the configuration-specific account and the qualified technical review required before any actual project commitment.
The decision corrected my assumption about how far one successful assembly could speak for its alternatives. I did not describe the held group as a small administrative exception; it marked the boundary of the supported proposition. Project design, installation and safety requirements continued through their own qualified owners. The outcome was a narrower, more defensible technical claim and a changed acceptance practice: the alternatives named in the commercial offer need evidence of their own before a repeatable concept becomes a repeatable commitment.
2023 — Keeping different generations visible in a replacement request
A review examined forty-five requests for replacement components within a family of demountable interior systems. Twenty-eight had supported matching routes. Seventeen referred to different product generations whose interfaces had not been established as interchangeable with the proposed replacement. The parts looked related, and their commercial descriptions encouraged a common-family answer. That relationship was not enough to establish the actual pairing.
The service team wanted a simpler catalogue route so customers would not wait while the version account was reconstructed. Joseph’s team wanted the physical interface and qualified review to decide the supported answer. I backed a ₹58 lakh, twelve-week programme to examine the unresolved group and revise the replacement information. The work preserved the original product generation rather than silently recategorising older assemblies under the current description.
Nine of the seventeen unresolved requests gained approved routes through that examination. Eight remained held, producing a final account of thirty-seven supported requests and eight still requiring another answer. An approved route concerned the defined pairing and its reviewed conditions; it did not establish universal interchangeability across the product family. Actual project and installation permissions remained separate.
The outcome gave the service team a more specific proposition to discuss, including an honest boundary around the requests we could not yet support. We did not infer a measured reduction in field failures or assume that a catalogue update completed every customer’s work. My responsibility was to prevent a convenient family label from making a technical decision the evidence had not earned. Replacement compatibility had to survive the passage of time and product revision, rather than rely on the appearance of continuity in the company’s own naming system.
2025 — Revising a maintenance promise that overlooked adjacent panels
Our development account described a maintenance route for selected demountable interior assemblies. At component level the part appeared accessible, but the complete task involved its position among surrounding panels. We examined twenty-four agreed mock-up scenarios. Eighteen supported the intended service-access route, while six required unplanned disturbance of adjacent elements. The distinction concerned the maintenance proposition itself, not merely how neatly the component had been drawn.
The release sponsor wanted to describe the six cases as workarounds for the future service team. Joseph argued that the promised route had not been established in those configurations. I chose to include the later service task in the development decision and hold the unsupported scenarios. The company should not sell ease of maintenance by transferring undisclosed additional work to whoever later performs it.
A ₹67 lakh, fourteen-week programme revised the relevant arrangements and repeated the agreed examination. Twenty-two scenarios then met the defined access criterion; two remained outside release. The result was tied to those scenarios and professional review. It did not demonstrate universal field reliability, certify a building or prescribe a safe installation method for every possible setting.
The decision changed what we were entitled to say about the supported maintenance route. We retained the two unresolved scenarios rather than allow the improved total to erase them. The programme also made a later activity influence an earlier design choice: the assembly had to be considered through the task promised after installation, not only through the first successful build. That is the technical responsibility I want development teams to retain when a modular product moves from a convincing demonstration into repeated use.