Tom Petrocelli's take on technology. Tom is the author of the book "Data Protection and Information Lifecycle Management" and a natural technology curmudgeon.
This blog represents only my own views and not those of my employer, Enterprise Strategy Group. Frankly, mine are more amusing.

Friday, January 30, 2009

Products, like living things, have a lifecycle. We conceive of new ideas and birth new products from them. They then begin to mature, finally to begin the slow decline to death. The period when they are in decline, past their maturation period is, hopefully, a long one. When it takes a long time for a product to reach end of life, we call that the long tail and boy is it sweet. You get free money, basically.

Sometimes, however, it doesn't work that way. It may be that there is one critical customer who still loves the product and wants a few more. Perhaps the folks who conceived of and built it have an emotional attachment to it. Often, there is this trickle of revenue associated with it that no one wants to give up. That is the most usual problem and the fact that the support costs are exceeding the profit on the product don't seem to work into anyone's calculations.

No one wants to invest in these products. It is recognized that they are old and other products have supplanted them. So they neither grow nor die. They are Zombie Products! (big B-movie scream here).

You know what I'm talking about. The product that is balanced between life and death. It lives in a netherworld, not moving forward nor toward end of life. The living dead!

Zombie products represent a real problem. They cost real money to make, stock, and support. Parts can become scarce as suppliers end of life their old products. They don't make the kind of margins that are needed to maintain the business. They don't even show the company well - if someone see a Zombie product they may get a negative impression of the company and its products.

So what does one do when there are Zombie products shambling about? Do what you always do to zombies - shoot them in the head. By that I mean, you have to kill them. No matter what it takes, you have to kill them! If the first shot doesn't take them out, try again and again. They must be killed.

Friday, January 16, 2009

When I was a young whippersnapper the main interface for computing was the command line. Either you knew the commands or you were... well, a loser. There was a certain thrill to having the arcane knowledge of the command line, something denied mere mortals. Like programming in C. It made us wizards!

The graphical user interface (GUI) gave the power of the computer to the common man. No longer did one need to understand the beast to control it. While this led to the great democratization of the computer (not to mention the ubiquity of computing devices) it also took some of the fun and mystery out of being a computer guru.

Now, we seem to be traveling back to that earlier time. A bunch of products has popped up recently that reintroduce the command line to computing. The first is Ubiquity, an extension for Firefox. You bring up the Ubiquity box by using a command key (also a bit retro but appropriate) and type in commands to do things like get the weather or google that company you think might hire you. The results are displayed in a nice little chunk of interface that goes away when you navigate away.

A similar (and freeware) product is Start++. It transforms your Vista Start Menu search bar into a command line that accesses the same type of information as Ubiquity. Type “ g something” to google something. The initial results are displayed in the Start Menu box or it can launch your browser and display the results there. The commands are very similar to Ubiquity.

So why revert back to the command line, other than for old times sake? Efficiency mostly. Let's say I want to get the weather in Saskatoon. Assuming your browser is open (and let's be honest, who doesn't have a browser open 24X7), you need to select Bookmarks or Favorites, navigate to the page you have bookmarked as you favorite weather site and wait for it to load. Next, you have to enter in the city you want to get the weather for (Saskatoon, Saskatchewan), and hit enter. With a command line tool, you get to skip some steps and simply type in “ weather Saskatoon, Saskatchewan”. That's only little more typing and gets the same result much faster. The power of a command line is that you can get what you want much more quickly and efficiently.

That assumes you know the commands and therein lies the problem with command lines. You have to know the commands and they are not always intuitive. For example, with Ubiquity, you can check your calendar by typing in “ check-calendar”. Simple enough if you know (and remember) it. Wouldn't “ calendar” or even “ check calendar” be more intuitive? Definitely. I'm sure there are a dozen good reasons for choosing one command over another but it often doesn't make sense to common people.

While I like the ability to use command lines for short cuts, I don't see it being a hit outside the geek community. Few people want to remember lists of commands nor do they want to type long and convoluted strings to get something done. Ultimately, these command line tools will never be mainstream and only be of interest to programmers and sysadmins who do this sort of thing continually.

Let's not forget that there was a reason we got away from command lines in the first place.

About Me

I am an experienced computer technology industry executive. Most recently, I was the Senior Analyst for Social Enterprise at Enterprise Strategy Group. Before that I was the Senior Vice President for Enterprise Software at IP.com. I'm a veteran of over 26 years in the technology arena. My background encompasses more technology and marketing than I can list here. Besides, why bore you with the details.
This blog represents my own views and not those of my employers. You should listen to our analysts. They're very smart people.