Sorry, can you elaborate on your question here, I am not sure by what you are trying to ask.
While I agree that on a practical note, it doesn’t matter. However with Aidan’s point on language, I definitely agree that language matters a lot, especially with dealing with all sorts of backgrounds, esp. with those who may not understand the role of product managers and don’t understand how PMs don’t really ‘manage’ people. (well product managers do and they don’t in MANY ways.)
But on the other hand, I personally think people need to be managed/guided and a lot of people also WANT to be managed/guided (if you have experienced great management, you know what I am talking about ~ great product leadership makes the whole team happy and productive - and most importantly WIN together as a team) We shouldn’t shy away from calling it product management just because there are aversions to not wanting to feel to be ‘managed’. (In many cases, my hypothesis is that these aversions are the result of extremely poor management and sometimes complete lack of product management in some cases). But yes, happy to put this aside for the great good so we can share more of the PM love. I think such aversions can be remedied and also part of our effort to improve the coordination of various teams in the space (which potentially starts with the conversation of “So… What is product management? What is it not?” my guess is that many are not aware, PMship can be arcane at times).
For those reasons, I can see both sides to why we should keep and also change the name. I lean towards keeping the name but I also agree that a different name could provide significant social advantages. Happy to keep the name but also happy to align with a new one if there is rough consensus.