The useful boundary around a product family

The universal case was an attractive proposition. A smaller catalogue would be easier to explain, and a rental colleague could hold fewer variants while serving more requests. I supported that direction because I could see its manufacturing and commercial advantages. What I had not adequately tested was the breadth of the word universal. A shared outer casing did not mean that every instrument inside it needed the same support. When six configurations failed to meet our defined assessment, the result challenged the premise I had approved rather than merely the details of its implementation.

Start with the equipment inside the promise

A product family exists because several uses share something important. That commonality can justify common tooling, parts or service arrangements. It does not erase the differences that remain. In transport cases, the contents and their supported arrangement matter alongside the exterior. A catalogue may organise products by a convenient visual category while the engineering question concerns weight distribution, contact and the conditions of use. I do not offer a packing method here. The leadership question is how a company decides which differences its standard product can responsibly accommodate and which require another answer.

Our 2022 assessment covered eighteen defined equipment configurations. Twelve met the agreed criteria and six did not. These were observations within a chosen assessment, not a universal forecast of damage on real journeys. The distinction prevents both exaggeration and dismissal. We could not claim that twelve successful configurations proved the entire offer, but neither did six unsupported configurations establish that common architecture was worthless. The evidence gave us a more useful development question:which parts of the shared design remained appropriate, and where did a different support arrangement or a separate product decision become necessary?

The commercial head proposed retaining the universal description and addressing the exceptions through special packing instructions. I understood the attraction. Customers had already heard the simple proposition, and a complicated choice could make a sale harder. Rental stock planning also benefits from fewer variants. An engineering leader should take those consequences seriously rather than assume that technical precision is free. Yet a commercial advantage cannot establish physical suitability. If the user must discover a substantial exception after selecting the case, the business has placed the burden of interpreting its promise at the wrong point in the relationship.

Treat the objection as a design question

Meera's concern was that the six exceptions would become a permanent dependence on local improvisation. She wanted the product architecture to carry more of the answer. I recommended a₹64 lakh programme covering development and tooling for a modular family. The aim was not to make the catalogue complicated for its own sake. It was to retain useful common elements while giving the intended configurations a clearer engineering basis. That required accepting that the original universal offer might narrow, even if the programme produced a better product.

The revised assessment supported sixteen of the eighteen configurations. Two remained outside the standard range and needed a separate bespoke decision. We did not hide them in an average or suggest that a careful customer could simply work around the exclusion. A standard offer should describe the use the enterprise is prepared to support. The boundary is part of the product, not an admission that the development team has failed to understand ambition. It tells commercial and rental colleagues where their ordinary process ends and another qualified assessment must begin.

This distinction also affects the next development decision. A company can decide to fund work on the remaining configurations, decline them or serve them through a different arrangement. Each option has a cost and a commercial consequence. What it should not do is treat the unresolved status as a small editorial problem that disappears when the brochure becomes more confident. The evidence did not establish those two applications, and the executive account needed to preserve that fact while explaining why sixteen supported configurations still represented a useful business opportunity.

My own role in the first proposal mattered. I could have asked the team why its universal insert had not delivered, as though the breadth of the promise were somebody else's choice. That would have missed the management decision. I had supported the simplification before the intended range was sufficiently established. Acknowledging that made it easier to discuss a modular alternative without turning every added part into an argument about who had been wrong. We were revising the proposition in response to evidence, rather than requiring engineering to rescue a word I wanted to keep.

Let the standard offer retain its edge

The revised family did carry additional work. Rental colleagues needed to identify the relevant configuration, and manufacturing had to manage more variation than the universal concept implied. Those costs belong beside the assessment result. A narrower promise is not automatically the best commercial strategy;it needs to be judged against customer needs, stock requirements and the resources needed to support it. In our case, I considered the clearer range worth that complexity. The paper explained the trade rather than presenting modularity as an engineering virtue that required no business argument.

Testing itself also needs a boundary. A successful defined assessment is evidence about the configuration and conditions examined. It does not certify an instrument's condition, establish every route's handling environment or eliminate the need for qualified judgement in the actual use. When a product or its relevant configuration changes, the earlier evidence may not answer the new question. The leadership discipline is to keep the supported claim connected to its basis. That can be done without burying customers in technical detail or pretending that every decision must await perfect knowledge of every possible journey.

For a board, the useful inquiry concerns the relationship between development evidence and the range management intends to sell. Which applications were examined? What remains outside the offer? How will commercial colleagues recognise those boundaries, and what will happen when a valuable customer asks for an exception? Directors need not choose an insert or inspect a drawing. They can ask whether the investment proposal contains an honest account of the product's scope and whether the economics depend on serving uses that the engineering programme has not established.

I would start the next family proposal with a map of intended uses and meaningful exclusions before celebrating the reduction in part numbers. That would bring customer knowledge, testing and rental work into the same early discussion. Common architecture can be powerful when the commonality is real. The lesson I carry from this case is to let the evidence define how far the promise travels. A product becomes easier to trust when the people selling, making and using it can all recognise the same boundary around what it is intended to do.