I want products that can be understood and maintained after their original development teams have dispersed. That makes repairability an important engineering concern. It also makes me cautious about the way a useful repair feature is sometimes described. A component that is easier to replace may offer a real service advantage. It does not follow automatically that the whole product has a lower environmental impact, a longer useful life or a lower total cost for every customer. Those are further propositions with their own assumptions and evidence needs.
The distinction should not diminish the design work. In fact, I think it protects it. When a modest but demonstrated improvement is burdened with a much larger unsupported promise, discussion can become a contest over the promise rather than an examination of the feature. A service team may have a clear reason to prefer a replaceable wear assembly even while the wider lifecycle comparison remains incomplete. Technical leadership should let that reason stand accurately, with the trade-offs visible, instead of treating a sweeping claim as the price of taking the improvement seriously.
Start with the service task
Our modular wear-assembly programme began with a practical difficulty. The existing design required a larger subassembly to be removed when a wear element needed replacement. The proposed route made the task more accessible. We needed to examine whether the design could support that service objective and what new responsibilities it created. The development work included the interface and the instructions, rather than treating accessibility alone as proof of a satisfactory product. A feature useful in a workshop still needs to be considered in the circumstances in which it will be installed and maintained.
The service exercise involved six technicians, each performing both tasks after familiarisation. We alternated the order across the group. Median observed times were 94 minutes for the existing route and 61 minutes for the modular one. These were twelve observations in defined workshop conditions. I wanted the result reported at that scale. It did not establish the time for every field repair, where access, wear, tools and other circumstances could differ. A customer downtime commitment would require more than the measured duration of the replacement task in this exercise.
There is a reasonable argument that such qualifications make a useful result sound timid. A commercial team needs language that communicates the benefit clearly. I agree that a result should not be buried in technical hesitation. We can say that the modular task was quicker in the workshop exercise and explain the conditions. We can describe the physical feature that makes replacement more accessible. Clear communication does not require presenting the observation as universal. The scope is part of the result, not an apology attached to it afterwards.
The programme cost C$960,000 over fourteen weeks. That expenditure covered development and the bounded service trial, not a complete lifecycle assessment. Keeping the programme's purpose clear helped determine what it should examine and what conclusion it could support. If the business wanted a broader environmental comparison, it needed to decide whether to commission the additional work. The original project should not be declared incomplete for failing to answer an unstated question, nor should its completion be used to imply that the unstated question had somehow been answered.
Keep the additions beside the benefit
The modular route added 2.4 kilograms of material and C$180 to initial unit manufacturing cost. It also created interfaces that needed appropriate examination and continued attention. These were not reasons to reject the idea automatically. They were part of the choice. A presentation that showed only the faster repair task would make the design look easier to approve than it really was. I wanted the service objective, initial additions and operating responsibilities considered together, so the company could explain why it selected the route under the intended circumstances.
Material quantity alone would not settle the wider comparison either. A heavier initial assembly might support a different pattern of replacement over time, while a lighter design might require more of the product to be replaced during a service event. The answer depends on actual assumptions about life, use and repair. I avoid making either direction of inference casually. A mass difference is a useful fact; it is not a complete environmental result. The team needs to specify what is being compared and over what period before turning that fact into a broader conclusion.
The same discipline applies to financial claims. An observed reduction in workshop task time does not automatically become a cash saving for a customer. Labour arrangements, travel, access and the timing of the service event can matter. Some customers may value a more manageable task even when it does not reduce an invoice in a simple proportion. The product should be described in terms that allow those users to assess its relevance. A manufacturer helps them more by preserving the inputs to that judgement than by supplying an attractive total built from unexamined assumptions.
I also ask who inherits the design after launch. A replaceable assembly needs identification, availability, instructions and a service route that remains understandable. If a later product revision changes compatibility, the earlier installed equipment still exists. Repairability is therefore not only a geometric feature visible in a prototype. It involves commitments that continue through purchasing, documentation and product support. A board or investment committee reviewing the programme should know that the chosen service promise has an owner beyond the team that completed the first design.
Build the evidence for the wider claim
If we want to claim a whole-life environmental advantage, we should establish a comparison suited to that question. The work would need a defined boundary and assumptions about product life, replacement frequency, materials, transport and the disposition of removed components, among other relevant factors. Specialist assessment would determine the appropriate method. I do not want a CTO's enthusiasm for a design to stand in for that work. Nor would I treat the existence of an assessment as permission to use any broader wording than its actual result supports.
The most useful improvement in our next programme is to discuss proposed public claims at the beginning. Product, service and commercial colleagues can then distinguish the evidence needed for a replacement task from the evidence needed for other assertions. This helps avoid a late conflict in which launch language has grown more ambitious than the programme's purpose. It also allows the company to decide deliberately which questions deserve investment, rather than assume that every attractive claim must be supplied by the same development budget.
I approved further introduction work on the modular route with its service result described narrowly and its additions retained. The company gave up a more expansive launch statement while keeping a useful engineering direction. I regard that as a positive exercise of leadership. A product promise should remain recognisable to the people who measured it, the people who manufacture it and the people who will maintain it. Repairability deserves attention on those terms. It does not need a claim beyond the available evidence to make it worth designing well.