A product range can look simpler in a presentation before anything becomes simpler for the customer. Several catalogue lines are placed beneath one family name. A successor receives a clear introduction. The development programme appears easier to explain. Meanwhile, installed equipment still has its earlier configuration, service history and practical constraints. I want an industrial portfolio discussion to hold those two accounts together, because the appearance of simplification can conceal a transfer of work from the product team to someone else.
In the fictional Qivaren Industrial review of 2023, we examined seventy-two variants. Forty-eight were candidates for six common platform families, while twenty-four special-duty variants required separate assessment. We funded CNY 42 million in six family development programmes and retained the special-duty group outside the common proposition. That was a decision about development scope. It was not six completed launches, universal interchangeability or proof that the service burden of the earlier equipment had disappeared.
## Count the exceptions before celebrating the common family
Qiaorong Ke wanted a successor story that sales colleagues could explain with fewer qualifications. That was a worthwhile objective. A customer should not need to understand the manufacturer's entire development history to find a suitable product. Excessive variants can complicate selection and make a simple need unnecessarily difficult to discuss. I did not oppose the common-family work. I wanted its scope stated accurately enough that the people using the proposition would know where it applied and where another assessment was still required.
The twenty-four variants were therefore part of the main decision, not an appendix to be resolved after approval. Their existence did not prove that each deserved permanent protection. A special-duty description can preserve an outdated choice as easily as it can identify a continuing requirement. Engineering, service and customer colleagues needed to examine the actual basis. Until that work was complete, however, placing the variants outside the common proposition was more defensible than allowing the candidate group to speak for every item in the catalogue.
A family can organise development without establishing that its members substitute for one another. Product language often compresses that distinction because the broader phrase is easier to remember. I wanted the programme account to separate a proposed architecture from the conclusion that a particular customer can replace particular equipment. The latter requires its own technical and contextual examination. A CPO can coordinate the range decision and its explanation while recognising that engineering validation and quality release retain their accountable owners.
Keeping the exceptions visible also changes how cost is discussed. The CNY 42 million funded a defined programme, with the continuing portfolio work still acknowledged. It was not a saving created by reducing the number of names in a slide. A future benefit might justify the investment, but the account should identify that benefit as proposed until there is evidence of it. I would rather give the reader a clear development choice and its limits than attach an attractive financial result that the fictional record does not contain.
## Treat retirement as a transition with named responsibilities
The 2015 sunset decision offers another way to examine the same institutional problem. The account covered 480 installations. Three hundred and sixty had a planned migration path, while 120 could not complete the proposed transition within twelve months. The first proposal sought to end the old range on that timetable so product and service attention could concentrate on its successor. I accepted the strategic attraction but asked what the end date meant for the identified group unable to move within it.
We retained a twenty-four-month service bridge for those 120 installations and CNY 16 million programme expense. This was a bounded response to a defined population. It was not a promise to maintain every old product indefinitely, and it did not establish that all 480 installations later migrated. The 360 planned paths also remained plans until their relevant work was completed. I wanted the account to preserve those stages, because a retirement programme becomes misleading if every customer with a proposed route is presented as already having taken it.
Service colleagues had to explain the work behind the bridge, while commercial owners retained responsibility for actual customer terms. The product office could not promise support merely by describing it as part of a roadmap. Parts planning, specialist availability and the assessment of a transition all had responsible owners. A board or executive reader needed enough of that account to understand what the organisation was choosing to retain. The detail should support a decision without pretending that a public leadership case can reproduce or authorise the operational programme.
There was a real cost to the choice. Keeping attention on the earlier range delayed some of the simplicity that supporters of the original timetable wanted. That objection should stay in the story. A transition bridge can be justified without being effortless or commercially ideal. The leadership question is whether the institution understands the consequences it has selected, including the work that continues after the successor becomes available. Describing the bridge only as a customer-friendly action would omit the difficult part of the portfolio judgement.
Nor does this case imply that every retirement deadline should be extended. A different installed base, obligation or successor route may support a different decision. I would ask for the population and constraints to be explained before applying the analogy. The useful practice is to examine how the proposal relates to the equipment still in use. It is not to turn one earlier accommodation into a rule that prevents an industrial company from ever ending a product line.
## Describe the development decision at its actual stage
The family programme and the sunset bridge reached different kinds of decision. One funded development while retaining exceptions; the other changed a transition timetable for a particular customer group. Neither should be described as a completed operating outcome merely because the executive discussion reached agreement. I want a portfolio narrative to say what was approved, what became available and what customers actually adopted as separate stages. Each statement then has evidence appropriate to its meaning.
This is especially useful when a leader prepares a public account of the work. A phrase such as simplified the range can conceal several possible accomplishments. The person may have changed the organisation of the catalogue, funded a common design, retired particular items or completed customer migrations. Those are all potentially meaningful, but they are different. Naming the actual change gives a search reader more to assess than asking one confident verb to cover a whole programme whose later results are unspecified.
I would expect the same precision in a board discussion. Directors can ask whether the new proposition leaves an unresolved service commitment and which executive owns the answer. They need not prescribe the technical remedy or negotiate individual customer arrangements. Their scrutiny should help the institution recognise what its portfolio decision depends on. My experience could contribute to that questioning, with the financial, engineering and operating evidence supplied by the appropriate colleagues rather than inferred from the product title alone.
All organisations, costs and installations in this essay are invented. The argument is that a product range belongs to a continuing relationship with equipment in use. A shorter future catalogue can be a valuable objective. It becomes a sounder proposition when the development stage, exceptions and transition work remain visible beside it. I would judge simplification by the explanation the next responsible person receives, including the customer who must live with the change after the presentation has ended.