How to name a product rewrite, without raising too high expectation?

Question

We are rewriting a product named « Module A » with a new technology for thousands of B2B users. It will be iso-functional. This rewrite will open new posibilities on the long run.
We would like to release this new version, while keeping the current version open, in order to gather feedback as soon as possible.
If we name this new version « Module A (V2) », it will raise too much expectation. I though about « Module A (Beta) » but it's not very clear. I guess I'm not the only one who's been through this.
How did you solved a similar problem ?
Do you have any idea/documentation?
Thanks

Antoine F. · Answer

We would like to release this new version, while keeping the current version open, in order to gather feedback as soon as possible.

We decided to add a migration banner to the new version on the header of the old module. This allows us to

keep the same module name
to set the new version as default for some users
prevent some users from downgrading to the old version

This solution was very practical, in particular to manage detractors.

Lonut · Answer

I think Beta will lower the expectations for sure. The users will understand that this is an updated version.
The way I solved this in the past in my past projects is naming Module A (V1.5). This is saying that it's not a completely new product but it's an improved one of V1.0.

JakeMc · Answer

You could go with a project codename while the new version is in initial development. Perhaps a codename that honors the existing module name in some way, or else inspires curiosity about the potential of the new possibilities that the new technology will bring.

Answered by JakeMc on November 9, 2021

How to name a product rewrite, without raising too high expectation?

3 Answers

Add your own answers!

Ask a Question