Every product manager knows the drill: business case approved, use cases completed, product requirements documented, then comes the dreaded "what are we going to call it".
As soon as this moment is reached in a product life cycle, suddenly everybody has an opinion. Personally I think that it is easier to pick a name for your unborn baby - at least generally there are only two people that have to agree (with a little advice thrown in from others of course, but you are under no serious obligation to comply with their wishes).
As soon as this moment is reached in a product life cycle, suddenly everybody has an opinion. Personally I think that it is easier to pick a name for your unborn baby - at least generally there are only two people that have to agree (with a little advice thrown in from others of course, but you are under no serious obligation to comply with their wishes).
Advice / instructions will be issued
by exec's in the management hierarchy, sales, marketing etc. And for
the most part this will be driven by personal bias, opinion and
nothing much else. I have yet to see a substantive or rational reason put
forward for any product name - generally the biggest ego rules. But there is light at the end of the
tunnel!
