A certificate can answer a different question from the customer

## Begin with the intended decision

The document in front of me had the qualities that make an executive comfortable. It was orderly, specific and prepared through a recognised internal process. I could see how the measurement had been related to its reference. I supported the release because I treated that account as enough reassurance about the product's intended use. The subsequent quality challenge did not reveal that the document was meaningless. It revealed that I had asked it to answer a question beyond the one it had actually answered.

A customer is rarely buying a measurement merely to possess a number. The number will inform a decision, an interpretation or another activity. Whether it is suitable for that purpose depends on more than the existence of a documented reference. The conditions, uncertainty and intended use matter. Qualified specialists must assess those relationships; an executive cannot settle them through confidence in the appearance of a report. My responsibility is to ensure that the relationship is examined before I allow the business to make the corresponding promise.

There is a practical objection to this approach. If every product discussion returns to first principles, development could become slow and repetitive. Teams need established methods, reusable evidence and reasonable confidence in completed work. I agree. The answer is not to discard prior work or commission an elaborate fresh investigation for every conversation. It is to identify the particular decision a proposed claim requires and establish which existing evidence addresses it, which assumptions remain applicable and which questions genuinely require further assessment.

That distinction makes the review more focused. A specialist should not have to defend the entire discipline of calibration whenever a customer asks about a product. Equally, the commercial team should not be left to infer suitability from terminology it may not fully understand. The technical leader can connect those groups by asking for an explanation in the language of the proposed use. What does the company intend to say the instrument can support? Under which conditions does the evidence support that statement? What remains uncertain?

My own error was encouraged by familiarity. I had begun my career in calibration and could recognise the seriousness of the work behind the record. That background made the document persuasive to me, but it also made me less attentive to the separate question raised by the product proposition. Experience can sharpen judgement while creating shortcuts that need challenge. A quality colleague should be able to question such a shortcut even when the CTO's earlier approval is already recorded and the launch date is visible in the business plan.

## Leave room for an indeterminate result

Our fictional review considered twenty-four qualification results. Eighteen supported the stated purpose and six remained indeterminate. The distinction between indeterminate and unsuitable mattered. We had not proved every unresolved case defective. We also had not obtained evidence that allowed us to treat those cases as suitable. A management account that offered only success or failure would have encouraged somebody to force the six into a category that made the presentation easier, while losing the actual state of knowledge.

An indeterminate result can be frustrating because it does not automatically select a commercial action. It may require more work, a narrower proposition, a different use or a decision to stop. That is precisely why the uncertainty should remain visible. The executive team needs to understand the available choices and their costs, while the responsible technical owners explain what further evidence could change the conclusion. Management can choose whether to fund an investigation; it should not choose the technical result the investigation is expected to produce.

We spent ₹64 lakh on the review and held the affected release. The expenditure did not itself establish readiness. It purchased investigation and a clearer account of the remaining questions. I kept that cost visible when discussing the outcome because it would have been misleading to present the correction as an effortless improvement. There was also a commercial consequence to waiting. A credible technical account should make those consequences understandable without using them as a reason to convert uncertainty into a favourable conclusion.

The independence of the quality voice mattered as much as the arithmetic. If the people examining the result believe that disagreement will be treated as disloyalty to an earlier executive decision, the formal review can become theatre. I needed to state that my own approval was open to correction and that the unresolved findings belonged in the record. That did not mean every challenge was automatically right. It meant the challenge would be examined on its substance rather than on the seniority of the person it contradicted.

There is a temptation to resolve discomfort through broad qualifications in the product material. Qualifications can be necessary, but they should describe a supported boundary rather than conceal an unanswered central question. If the proposed use itself remains unsupported, a general sentence about conditions may not repair the problem. The relevant engineering, quality, commercial and legal owners need to establish what can responsibly be offered. My role is to bring that conversation together and prevent a vague phrase from becoming a substitute for the missing decision.

## Make the product promise follow the review

A product claim travels farther than the meeting in which it was approved. It may appear in sales material, a proposal or a discussion led by someone who never saw the qualification evidence. The wording therefore needs to carry the material boundary in a form that remains understandable. It should not depend on every later reader remembering an informal explanation from the engineering team. The technical leader should examine how the supported conclusion will survive that journey, with the relevant communication and professional owners involved.

This does not require public release of confidential technical records. The full evidence may remain controlled while the outward statement accurately describes the permitted proposition. What matters is that the commercial language does not expand when separated from its supporting file. A useful internal approval records the relationship between the statement and the evidence, the conditions that matter and the person responsible for reconsidering it when the product or intended use changes. That is a management discipline around technical work, not a replacement for the work itself.

Directors can contribute by asking about that relationship without attempting to rerun a laboratory assessment. They can ask what conclusion management wants to rely on, whether qualified independent challenge occurred and what unresolved findings mean for the proposed commitment. They should also understand the financial and customer consequences of delay or a narrower claim. A board that sees only a green release indicator may miss the decision actually being made. A board that demands certainty where the evidence cannot supply it may create an equally unhelpful pressure.

I would not turn this experience into an argument that certificates are unimportant or that product development should wait for perfect knowledge. The point is more precise. A document can be valid and valuable while answering a different question from the one the business needs answered. Leadership requires noticing that difference, especially when a familiar document supports a decision we already want to make. The product promise should follow the examined purpose and evidence, with its remaining limits intact, rather than borrow authority from the most reassuring page in the file.