A service pilot can produce a result that is encouraging and still narrower than the product story we would like to tell. In our 2025 pilot, forty-eight lamps were returned. Thirty underwent lens-only repair and went back into service after qualified acceptance. Eighteen needed further housing or electrical assessment. Those figures supported an account of thirty completed repairs within a defined process. They did not establish that every returned lamp was repairable, that the remaining work was minor or that a customer could carry out the same intervention without qualified support.
The programme cost ₹56 lakh. I kept that expenditure beside the result because it described the resources we committed to understanding and supporting the service proposition. It was not a measured saving. The case also contained no assessed carbon reduction or extended-life promise. We had a practical result to explain without borrowing those additional conclusions. My responsibility as product leader was to make the useful claim understandable and resist enlarging it merely because a broader statement would be easier to promote.
A service result belongs to the units assessed
The first distinction is between the group entering a pilot and the group completing a particular intervention. Forty-eight was the number received. Thirty was the number that completed lens-only repair and qualified acceptance. The remaining eighteen had not reached the same outcome. Keeping the groups visible protects the meaning of the result without reducing the achievement of the work actually completed. It also prevents a product page from turning a mixed service population into a universal statement through a convenient headline.
The accepted thirty should not be described simply as lamps with a part changed. Qualified assessment belonged to the outcome. A physical replacement and a decision that a product can return to service are connected activities, but they are not interchangeable claims. Product communication needs to preserve that difference. Otherwise a reader may infer that the visible intervention is the whole service procedure, or that the same repair is appropriate for every unit that appears to have a similar problem.
I would not turn this account into instructions for opening or modifying a rechargeable lamp. The pilot concerned work through qualified service arrangements, with engineering and release authority retained by the appropriate owners. My product role was to understand which proposition could be supported and what customers needed to know before relying on it. Clear service communication can explain scope and next steps without pretending that a public narrative replaces assessment of an individual product.
There is also a difference between an observed result and a future commitment. Thirty accepted repairs show what happened to those units in that programme. They do not establish a universal completion time, price or outcome for subsequent returns. A customer considering service deserves an explanation of the relevant process and conditions. The organisation must decide what it can responsibly offer using its actual capabilities. The pilot gives that discussion evidence; it does not remove the need to define the offer.
The unresolved returns belong in the proposition too
Eighteen lamps required further housing or electrical assessment. I would keep that sentence in the main account rather than remove it to make the completed result appear cleaner. It does not mean those eighteen were beyond repair, nor does it mean they would eventually be repaired. The evidence stopped at a different stage. Describing that stage accurately helps the reader understand the limits of the lens-only service proposition and the work that remained with qualified specialists.
Unresolved cases can inform product choices without being converted into outcomes. They may prompt questions about service access, components or the details needed when a product enters assessment. Those questions require their own work. I would not claim that the eighteen already demonstrated a particular design defect or justified a specific engineering change. A product leader can recognise where the service offer needs more understanding while leaving cause, suitability and technical decisions with the people responsible for examining them.
The relationship with the customer matters here. Someone sending in a lamp needs to understand that an initial description may not settle the service route. A useful proposition explains that assessment can distinguish the supported lens-only intervention from other needs. That is more helpful than a blanket repairability statement followed by qualifications only when the product arrives. The point is to make the available service legible early enough for a person to form a reasonable expectation about what happens next.
I would also separate the service team's result from the commercial arrangements that may later accompany it. A pilot does not itself define every price, warranty position or replacement decision. Those matters belong to the responsible functions and the actual offer. Product leadership should bring the evidence into that conversation, including the unfinished group and programme cost. It should not describe a mature universal service commitment merely because one defined intervention has succeeded for some of the units reviewed.
A product leader must distinguish the service offer from the environmental story
Repair invites an environmental narrative, but the pilot did not measure one. Returning thirty assessed lamps to service is a meaningful physical outcome. Quantifying environmental impact would require an appropriate account of the alternatives, materials, transport, energy and subsequent use, among other relevant considerations. We had not established that account. I therefore would not attach an invented carbon figure or an assured life extension to the service result. The absence of that broader assessment does not erase the completed repairs.
The same discipline applies to financial benefit. ₹56 lakh described programme expenditure. It was not a claim that customers or the enterprise saved that amount, and the thirty repaired units did not create a measured return on the investment by themselves. A later commercial evaluation would need the evidence appropriate to its question. For the profile, the honest contribution is the decision to fund and define a bounded service proposition, with its completed and unfinished work shown together.
What I want another product leader to take from this example is a way to keep a useful result intact. Begin with the units and intervention actually assessed. Preserve the acceptance step and the authority behind it. Explain the group still requiring further examination without predicting its outcome. Keep programme cost separate from benefits that were not measured. Then describe what the evidence allows the organisation to offer or investigate next. This produces a product account that a customer and a service colleague can recognise.
The pilot strengthened our understanding of lens-only service through thirty completed, accepted repairs. It also showed why the entire return population could not be folded into that one outcome. I regard both observations as part of the product work. A service proposition earns credibility when its words follow the work closely enough to include the unfinished portion. That is the standard I would apply before adding a larger environmental, commercial or universal repair claim to a result that has not established it.