A new product name still has to answer an old customer's question

## Understand what the old reference still does

We reviewed twenty-eight legacy product references that had accumulated different naming habits. Experienced colleagues could often explain them from memory. A newer purchaser could find the same range difficult to navigate. Marketing wanted a clearer family structure, but sales colleagues asked what would happen when an older enquiry arrived using a familiar reference. That question changed the brief. The programme had to make the new description easier to understand without making the customer's existing history harder for the business to recognise.

An old name may appear in an internal request, a previous quotation or a customer's own record long after a campaign has moved on. Removing it from a fresh presentation does not remove it from those conversations. I did not want the new system to treat every older reference as an inconvenience caused by somebody failing to read the latest material. The business had helped establish those names. It therefore needed a usable route from them to the revised explanation, including a clear account of what had changed and what had not.

The alternative was to leave all twenty-eight references unchanged and improve the surrounding guidance. That approach had merit because recognition itself has value. A familiar industrial reference can help a buyer reach the right colleague quickly. But familiarity was uneven, and some names created avoidable confusion. We chose a partial revision: eighteen references received new names, while ten remained with clearer descriptors. The programme cost ₹42 lakh. The choice required more explanation than a single clean replacement, but it retained useful recognition where a new label was not the strongest answer.

The route between old and new references was part of the work, not an administrative appendix. It helped a commercial colleague interpret the customer's language before deciding which question should go to a technical owner. That continuity mattered because the buying conversation did not begin from the same place for every person. One purchaser knew the older range; another arrived through a newly published description. The revised system needed to serve both without assuming that either person's reference alone settled what product or application was appropriate.

## Separate recognition from suitability

A clearer family name can create a new risk of interpretation. If two references sit together in a revised structure, a reader may assume they are interchangeable or suitable for the same use. The marketing programme did not establish that. Technical colleagues retained application and compatibility decisions, while operations retained the relevant availability account. The name should make the next question easier to ask. It should not answer a specialist question merely because the revised family looks orderly on a page.

We therefore reviewed descriptions with the people responsible for the underlying product account. Their participation was not an invitation for every technical detail to become a headline. It was a way to understand which distinctions the simplified explanation must preserve. A good family structure can reduce unnecessary complexity while keeping the difference that changes a buying decision. Marketing's responsibility is to make that difference intelligible. It is not to decide that the difference has become unimportant because a shorter name would produce a more attractive layout.

This is why I resist treating a naming programme as a purely visual refresh. The work can change how people interpret the range, what they ask for and which assumption they carry into the next conversation. Those effects deserve a commercial and technical account. At the same time, the programme should not become so elaborate that nobody can use it. The practical aim is a clear explanation with an accessible route to the responsible specialist, including the older reference when that is where the customer's understanding begins.

The ten retained names were useful evidence of the method. We did not rename every reference to demonstrate that a programme had happened. Some names already helped the conversation and needed a clearer descriptor instead. The eighteen revised references had a different problem. Preserving that distinction made the decision more credible to sales colleagues who would carry the explanation. It also prevented the project from equating the amount of visible change with the amount of useful work. A restrained decision can be harder to present than a complete relaunch but better suited to the actual range.

There was no claim that the renaming created new availability, changed compatibility or improved product performance. Those outcomes would need different evidence and authority. I wanted that boundary visible because a successful explanation can easily acquire a broader commercial story as it moves through presentations. A buyer understanding the intended family is a worthwhile result. It does not establish that the family contains a suitable product for the buyer's use, that the item can be delivered when required or that an order will follow.

## Use the explanation exercise without overstating it

In a later exercise with forty-eight participants, thirty-nine identified the intended family and nine needed assistance. The result helped us examine the revised explanation. It was not a matched before-and-after study because we did not have an equivalent earlier exercise. I therefore did not calculate an improvement attributable to the naming work. A number becomes less useful when its presentation asks it to support a comparison the underlying method cannot make. The appropriate account was the observed result in this defined exercise, with the remaining need for help still visible.

The nine participants mattered. Their difficulty was a reason to ask where explanation remained unclear, not a reason to treat the whole programme as unsuccessful or to exclude them from the story. They might have interpreted a descriptor differently, started from an older reference or needed a specialist distinction explained. The next step was to examine the actual questions raised. An honest exercise should help the team decide what to improve. It should not become a ceremony in which any result must be made to validate the preferred creative choice.

Management also needed to see the expenditure and the alternative. Forty-two lakh rupees supported a partial revision and continuity work. Keeping all names with additional guidance would have been a different choice, with its own cost and limitations. We chose a mixed route because the problems differed across the range. The explanation exercise offered useful information about that route, but it did not prove the entire economic case. Commercial follow-up would need to preserve the distinction between clearer navigation, technical fit and eventual buying outcomes rather than collapse them into one success claim.

In a board role, I would ask how a proposed change preserves the business history customers still use. Directors do not need to choose product names. They can examine whether management understands the interpretation it is changing, the specialist boundaries involved and the evidence behind its reported outcome. The question applies beyond naming: when a company simplifies its offer, what existing knowledge must remain reachable? My experience makes me attentive to that continuity. A new explanation should help the next buyer enter the conversation while allowing an established customer to remain understood in the language the business previously taught them.