Two pilot counts do not automatically make a comparison

## Identify the question each pilot answered

Seven of twenty-four assemblies failed the agreed criterion in our slurry pilot. A revised dry-application group had two failures among twenty-four. The numbers invited a simple story: the later group looked better. But the applications and conditions differed, so those counts did not establish a matched improvement. I wanted the development discussion to begin with that limitation. A result can be encouraging and still fail to support the comparison that a commercial presentation would like to make from it.

The proposed product programme had included both dry mineral handling and a slurry use. Each involved a wear-ceramic proposition, but the shared material description did not make the operating conditions interchangeable. The relevant question was whether the evidence supported introduction for the intended application. That question needed a qualified account of what had been examined, not a percentage calculated from two groups simply because both happened to contain twenty-four assemblies. Equal group size is not the same thing as an equivalent comparison.

I asked the team to keep the application, conditions and acceptance criterion alongside each result. Those details were not an appendix for specialists to rescue later. They determined what management could infer from the work. A director reading only the two failure counts could reasonably assume that the revised design had been tested against the same duty. If that assumption was wrong, the paper needed to prevent it. The responsibility for clear interpretation sat with the people presenting the result, not with a reader expected to discover the missing qualification.

Commercial colleagues wanted a broad launch because interest existed in both applications. I understood the attraction. A wider proposition could make the development effort easier to explain and create more opportunities for the sales team. The technical account could not be expanded to match that ambition. The slurry route had failed its criterion. The dry route needed its own qualification account, including the two failures. I did not want one group's result to become a convenient way of avoiding the unresolved question in the other.

## Narrow the promise before the launch

We funded a one-crore-twenty-lakh-rupee examination programme and supported a narrower dry-application introduction route through the qualified process. The slurry route remained unsuitable for launch. Sales proposed proceeding more broadly with a limitation in the accompanying description, on the basis that further development could continue alongside delivery. I declined that approach because the unresolved question concerned the central intended use. A qualification that materially changes the proposition should shape the launch decision itself, rather than sit behind an expansive headline.

The decision meant giving up pursuit of eight crore sixty lakh rupees of indicative slurry enquiries at that point. I kept the word indicative in the account. These were not firm orders, recognised revenue or a realised financial loss of that amount. Their existence showed commercial interest and an opportunity the narrower route would not pursue immediately. Inflating that status would have made the engineering choice sound more dramatic, but it would also have weakened the board's understanding of what the business was actually deciding to forgo.

The dry application did not receive an unconditional endorsement because the slurry route had been declined. Its own examination and release requirements remained. Quality head Mala Norsheli retained acceptance authority, and the two failures stayed in the record. I wanted management to see that a narrower claim can still need careful qualification. The decision was not a choice between a failed broad proposition and a flawless narrow one. It was a choice about which route the available evidence could responsibly support for further introduction work.

This distinction also affected the next development brief. Work on slurry use could continue only with a justified question, resources and a clear account of what would change the decision. It should not continue invisibly inside the dry launch budget because the original commercial story had included it. Separating those commitments helped the team understand what the approved programme was expected to achieve. It also protected the dry route from being described as a temporary compromise whose boundaries could be ignored as soon as a promising enquiry appeared.

## Preserve the work the result has not done

An examination programme produces evidence under conditions. It does not automatically establish the whole future product story. I wanted our report to state the work still required and the claims not made. That included avoiding a matched percentage improvement from the two pilot groups and avoiding a broad performance statement across every wear application. The boundaries made the evidence more useful because the receiving reader could understand what it supported. A result with a defined scope is more actionable than a larger claim whose limitations must be reconstructed later.

For a board, the question is whether the product promise has an evidence account that matches it. Directors do not need to select the detailed test method or overrule a quality decision. They can ask whether the conditions represent the intended application, whether the comparison is like for like and what commercial commitment depends on the unresolved part. They can also ask whether the programme cost includes the qualification work still needed. Those questions keep oversight focused on the enterprise choice while respecting the professional authority of the technical owners.

The case also changed how I prepare the commercial discussion at the start of development. I now want the proposed public claim stated early enough that the team can examine what evidence it would require. A broad claim may be possible, but it could demand a programme the business has not funded or a range of conditions it has not considered. Discovering that gap only when the launch language is ready creates unnecessary pressure to stretch the result. A clearer initial proposition gives both engineering and sales a more honest basis for planning.

Our outcome was a narrower dry-application route after one crore twenty lakh rupees of examination work, with slurry introduction declined and its indicative enquiries kept in their proper commercial category. The seven and two failure counts remained attached to different pilot conditions. That account is less dramatic than a single improvement percentage, but it explains the decision management made. Development leadership should help a company say precisely where its confidence comes from. The value of an experiment is not increased by asking it to answer a question it was never designed to settle.