August 15, 2006

On the Difficulty of Forecasting, Particularly about the Future

I’ve been reading and listening to John Dvorak’s comments on the PC industry since 1983 or 84, when I was in business school thinking about what to do after graduation. I was interested in the potential of the PC industry, and I found Dvorak’s column the most useful for thinking about its future. Those were the days when he used a lot of bold type to emphasize his points.

What I like about Dvorak is that he tries to get behind what companies are saying/doing and comes up with an interesting perspective on what’s really going on. That leads to some projections that don’t pan out, but are interesting nevertheless. He retains this style in what he says on the Twit podcast. I met Dvorak briefly at a trade show 15 years ago. He was wandering the low-rent aisles and came across our booth. We had an antique MicroVAX there as part of a demo, which piqued his interest. He asked a thoughtful question or two about what we were up to and then moved on, belying his cranky persona.

A few weeks ago, the Twit pundits were talking about nascent Blu-ray player shipments. Someone commented that Sony may have run out of inventory because they built an initial quantity of boxes before committing to future runs, so they could gauge demand and set production levels appropriately. Dvorak responded that that was nonsense, nobody does runs any more, they do continuous production. He said that when companies introduce new products they’ve done market research and know precisely what demand will be and therefore how many to build.

Whoa! That stopped me in my tracks. I thought back to the very early days of Ipswitch, more than 15 years ago, when I met with the head of our accounting firm to talk about budgets. His principal comment: startups can project expenses pretty accurately, but when it comes to revenue, they tend to be way off. Now of course that has quite a bit to do with the fact that they are just starting out, and don’t have a basis for predicting how much or when customers will buy, but it’s been my observation that that has remained true for us as we introduce new products, and stays true even for very large companies. (Projecting sales of existing products is much more feasible.) No matter how much market research a company does, revenue projections for a new product are in the end an educated guess, which can be wildly off the mark. After all, with new products you’re trying to get consumers to change behavior or learn something new. Anyone remember Microsoft’s Bob product?

I also recall that large consumer goods companies like Procter and Gamble and Unilever (who are the real experts in market research) run all sorts of regional and local tests and still end up being blind-sided by a customer reaction to a new product because there was yet another way of characterizing the market that they had not anticipated.

As Ipswitch considers new products to develop, we use a formal process for market research, do analysis, and then define and build a product. Each time we do this we build upon what we’ve learned about the process before. After all of that, though, what we’ve done is reduce uncertainty, not eliminate it. It’s this balance of research, innovation, resource allocation, and operational management that has led to 15 consecutive years of growth for Ipswitch, and which is driving our strategy as we go forward.

But if you know someone with a crystal ball, John, please send them my way. I’d like to hire them.

Posted by Roger Greene |
digg this add to del.icio.us add to My Web Furl this page

August 04, 2006

We Aren’t Family (We Are Community)

It puzzles me how often companies characterize themselves as families. I think that’s not the case at all, no matter how tight-knit an organization is. I think of Ipswitch not as a family, but as a community.

In some ways I can see why people refer to companies as families. Employees spend a lot of time together, form friendships, and even at times fall in love and get married – which can work as long as neither person has influence over the other’s job assignments or career path. (I recall that work is one of the top places that couples meet. That’s usually in companies bigger than Ipswitch, though we did have two employees get married once.)

But calling a company a family distorts the picture, and encourages the wrong kind of thinking about what the company is all about. Companies have a purpose, which includes producing products or services and convincing customers to purchase them. Companies must also take in at least as much money as flows out, or eventually they go out of business. As part of that, managers must regularly decide on the right number and mix of people to employ, assess performance, and adjust staffing accordingly. Families are forever, no matter how poorly they get along. Siblings, parents and children, cousins, grandparents, etc. may feud and not talk for years, but they remain a family. A family doesn’t have to actively accomplish anything to stay a family. Thinking of a company as a family encourages a feeling that the company will always exist, which Andy Grove would find antithetical to his famous comment that only the paranoid survive.

Communities also have a purpose. If they fail to fulfill their purpose, they disintegrate and become a collection of individuals, who typically seek to form new communities. People in communities also form strong bonds, and can feel a deep connection with others. But the makeup of a community changes over time. People come and go, but as long as community achieves its purpose, it continues to exist. That sounds much more like a company than a family to me.

So say my sisters and me.

Posted by Roger Greene |
digg this add to del.icio.us add to My Web Furl this page