Do we need a product rosetta stone?

Even before I saw Bart Muijzer's blog responding to a customer's parody, I knew that Sun doesn't always communicate our direction or product line effectively.   It must be frustrating for customers and partners.  There are many reasons for this. When an internal development product name becomes public knowledge, partners, customers and Sun engineers know the product by that name (madhatter, BrandX, APOC, Zones).  Then for various reasons (legal trademark issues, google uniqueness and inclusion in a related product stack), the product is released under different names. (Java Desktop System, BrandZ, Sun Desktop Manager, N1 Grid Containers).  To add to this confusion, sometimes product names are changed between versions or the same product acquires more than one public product name over it's lifetime (e.g. SunOS 4 == Solaris 1, Java 1.2 == Java 2.) Between product name aliases, the whispers game and FUD from competitors with much larger marketing budgets, it's no wonder things are confusing out there. So my question is, could we clear up some of the namespace confusion with a webpage showing the history and name aliases for all of our products?
Comments:

Brian, SUN doesn't need a specific 'product history page' but wares 'naming' policy that ALL employees and corporate representatives can adhere too! (Termed 'product lifecycle management') About to introduce a product improvement, mass market 'naming' convention. (Hint: GREAT ware and manufacturer, POOR sales caused by an odd product name!)

Posted by William R. Walling on May 28, 2006 at 10:42 AM GMT+00:00 #

Post a Comment:
Comments are closed for this entry.
About

bnitz

Search

Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today