Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Wednesday, April 16, 2008

Blue Ocean Strategy & Technology Innovation

I can't count the number of times I've heard marketers rant on to say that technology has nothing to do with innovation and that Blue Ocean Strategy somehow supports this notion.

Summarizing: Blue Ocean Strategy puts customer value at the center of any new offering. Customer value is never defined in terms of raw technology, but the technology is catalytic to the value: the value will never get realized without the technology.

Let's examine some examples:


  • The Wii wouldn't be without its small, inexpensive accelerometer driving the Wii remote. The accelerometer allows the creation of the magic wand: no accelerometer = no magic wand. However, Nintendo is not marketing accelerometers.

  • Google reads a users mind to return relevant search results. However, these results are driven by a brilliant search algorithm and massive data centers. No brilliant algorithm and no enormous infrastructure = no mind reading web search. However, the end users never see the technology.

  • The Toyota Prius is an engineering masterpiece. A user drives around with more computing power than the entire world had not long ago powered by computer-designed technology no human with a slide-rule could ever have mastered. No computers to design and run the Prius = no magic high mileage car. However, end users never see the technology.

  • Even the Blue Ocean Strategy case studies in the book all have technology driving them. Starbuck's uses extremely sophisticated GIS systems and water filtration technology, Cirque du Soleil low noise, portable power generation and stage technology, the NYPD well documented crime tracking software; the list is endles...

All of these ... virtually every Blue Ocean business has one element in common: catalytic technology that is invisible to the end user. Blue Ocean Strategy demands the technology in itself rarely, if ever, has value but the value the technology brings to the consumer does. And, in almost all case studies, no technology means much less value. There are exceptions, but they're extremely rare.

I'll give marketers who say the technology doesn't matter the benefit of the doubt that they're not just trying to cover-up their own unwillingness or inability to learn about the technology driving their industry. However, when these people pipe-up and start shouting that "technology doesn't matter" tell them that they're absolutely wrong. It's just that technical innovation must be defined in terms that drive utility to the end user, but that doesn't mean the technology is unimportant.

Quoting the book "[acting] on the assumption that bleeding-edge technology is equivalent to bleeding-edge utility for buyers ... is rarely the case." Blue Ocean Strategy, pg. 120. That doesn't mean technology doesn't matter; it means the technology must always be described for it's utility and value to the buyer.

There would be no Nintendo Wii, Google, or Toyota Prius without extremely sophisticated new technology. The NYPD would be chasing down muggers aimlessly, Cirque du Soleil wouldn't be the same without the dramatic lighting, and Starbucks wouldn't magically be located in great locations. Just because the end-user never sees, understands, or appreciates the technology doesn't mean the business/product developer doesn't need to.

Thursday, April 10, 2008

Blue Ocean Strategy: Adding Value to Value Innovation

Blue Ocean Strategy is comprised of two primary pieces. I've focused the last few posts on the managerial components, because most people don't pay attention to those. But this is a blog for product and business developers, and most are focused on the concept of value innovation.

To reiterate, value innovation involves finding the key factors of an offering then eliminating and reducing factors that consumers can live without. Some of the cost savings used to eliminate and reduce are used to raise and create key factors that make an offer truly compelling and unleash a business that makes competitors irrelevant. Think the Nintendo Wii, Google's search engine, the Toyota Scion, and the entire open-source movement.

I've found the biggest challenge to the implementation of Blue Ocean Strategy is the accurate identification of the key factors and then having the guts to eliminate and reduce those key factors. If you do not eliminate and reduce substantive key factors, you are not practicing Blue Ocean Strategy. The whole point is to be able to create a Wii then sell it profitably for $250 at retail, while your red ocean competitors make machines that people want less and that sell for considerably more while taking a large loss.

I've seen too many value curves where people simply identify a plethora of key factors and raise them. This is a predicable recipe for what is, at best, a mediocre offering and at worst a disaster. The focus groups and internal marketers will probably be happy: "hooray -- this 'new' thing is like the old one's but there's more of it." But the market will, at best, shrug. Think Microsoft Vista, Yahoo search, or Dell's relentless pursuit to gut their respective companies. [In all fairness, I just purchased a pre-configured Ubuntu laptop from Dell. The fact the sell such a thing suggests they're once again trying, but it took me an hour to complete my purchase once I made my buying decision, thanks to an ineffective, frustrating, and ultimately useless phone-tour of India].

Ensure the "value" in value innovation: use the Four Actions Framework to eliminate and reduce key factors that consumers don't care about. Is Blu-Ray movie playing cool? You betcha. Do the movies look great? Sure they do. The physics and high-definition graphics are slick: they're so real an early PS3 critic said the absence of real-life made basketball players look like zombies. Still -- even with, or maybe despite all the neat gadgetry -- my kid still doesn't seem to have much interest in a PS3 or XBox360, despite that he loved his PS2. His attention is entirely on the Wii.

Saturday, April 5, 2008

Blue Ocean Strategy: Seeing through the clutter

As the original Clinton campaign would have put it, "it's the six-path framework, stupid." Seriously ... a lot of people ask how to actually use Blue Ocean Strategy to make a new business. I've written a longer post that goes into each specific step, but realized that I skipped an executive summary that may be even more important.

Summarizing the 240 page academic book into one sentence: use the six-path framework to find the key factors of a business through the lens of customers and non-customers, then use the four actions framework to redefine the market boundaries of that business while adhering to tipping-point leadership and fair process to increase the chances your organization will be able to execute your new business. OK ... it was a run-on sentence, and it greatly oversimplifies. Still, it's a start.

As a product/business developer I'll take things a step farther. Listen to the Harry Chapin song "Six String Orchestra" where a young man dreams of being a great singer. In reality, he can't play his instrument and receives nothing but negative feedback from everybody around him. But in his mind, he hears the beautiful songs of the future, knowing that he'll have to do the hard work, practice a lot, and find the right people to make music with.

Product and business development is like that. I once had an early version of a product that went on to do great generously described as a "mud hut" by a seasoned software developer. He wasn't being negative: just saying that he understood my vision but that a lot of work is needed to turn that vision into reality.

Some people will disparage or sabotage your ideas out of petty jealousy, or because they fear their livelihood or relevance will be threatened either by the business you create, or the fact you (and not they) created it. But I've found many aren't acting in bad faith: they just don't understand where you're going and don't have the brainpower to see the end of the path.

Blue Ocean Strategy helps you not only figure out where that path should lead to, but gives us a series of powerful tools that help communicate that to others. Blue Ocean Strategy provides a roadmap, but isn't magic: you, the product and business developer have to figure out where that road is leading to and push your organization down that path.

The six-path framework is how you, the person trying to redefine a business or industry, find those key factors that are vital to the success of your business: it's the music you hear in your head, that you know you're capable of.

In the search for key factors, it's not uncommon to quickly jot down a list of factors: don't do this. Remember the old software engineering term GIGO: Garbage In, Garbage Out. The process of identifying and isolating key factors should be long and painstaking: there's nothing easy about it. You should really be uncomfortable with the key factors you eliminate and reduce. Making things worse, the longer you've been in the industry the more difficult the process will be, because you'll be steeped in the standard boundaries by which companies are already competing.

But if you use the six-path framework to find those key factors, then apply the four actions framework against them, you'll find that music you knew was there will come alive in real life. You'll invent a Wii, create the Prius, or launch the next Google. But never underestimate the amount of raw effort that went into each of these individual efforts, or that must go into yours if it has a chance of succeeding.

Tuesday, March 4, 2008

Across Alternative Industries: From commercial printing to a pregnancy calendar

One of the six paths towards value innovation is to look across alternative industries. Let's take a brief quote from the book: "alternatives include products or services that have different functions and forms but the same purpose."

One of my inventions is the online pregnancy calendar. It's become relatively common now, but I built the first pregnancy calendar -- a website which contextualizes information during fetal development -- in early 1996 when my wife was pregnant with our son.

I'd like to say the pregnancy calendar was a well thought out and brilliant invention. The truth isn't quite as glamorous, but is more valuable from an understanding of where to look for new business ideas...

At the time I was working for Merrill Corporation on a print production control system. Merrill (a great company, and worth an entire separate post) is a leader in the creation of compliance documents for the securities industry. Way back when this meant printing books of financial disclosures to be mailed to investors and government agencies. These books would have to be produced at the last minute, changing with market conditions, then distributed around the country to Merrill's various print plants.

At the time I was looking for a method to allow the different print plants to coordinate scheduling the print jobs. They had a primitive Unix-based system but scheduling is an inherently graphical function, so they relied mainly on white-boards. The web browser had been invented not long before and table support was relatively new. I had the thought to use HTML tables to show production schedules that could be viewed and manipulated from different plants around the country.

As a learning exercise, at home, I wanted to see if it was possible to dynamically generate calendars in HTML. Once I created my test calendar I needed to populate the cells with data. The house was filled with pregnancy books and I thought it'd be neat to see how my son was developing tied to real dates.

So I pulled out data from all the pregnancy books and arranged them into a text-based database using their relative offsets. For example, "Day 8 -- Blastocyst cells separate: a baby head and tuchas form." I finished it, half tongue and cheek, and gave it to my wife, who gave it to friends, and on to other friends. Next thing I knew my learning project was on CNN, and being written about in the WSJ, NY Times, and lots of other media.

Most importantly, had I not started to look at industrial print plant scheduling I would never have cooked up the idea of a dynamically generated pregnancy calendar. I'm sure that somebody else would have eventually, but it wouldn't have been me: I would've missed the market. By looking across alternative industries -- even inadvertently -- I accidentally created a category killer that continues to dominate the online landscape to this day.

End note: For those who realized it while reading ... yes; I may have been the first to render calendars with contextualized content in HTML tables. Was I actually the first? Who knows. Could I have patented that? I hope not, but the way the PTO was recklessly issuing patents back then, probably. Would I do things any differently today with the patents? Nope. Even though I was told "sell this at a discount, or we'll make a knockoff" I still believe that software patents are rarely justified. Larry Page's brilliant Page Rank algorithm is the type of breakthrough that may make them acceptable, but nothing less than that. In any event, I suspect Google would've been just fine without the patents; the hassles from patent trolls is outweighed by the benefit to genuine innovators.