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.
Popular Posts
Thursday, April 10, 2008
Blue Ocean Strategy: Adding Value to Value Innovation
Posted by
Michael Olenick
at
9:37 AM
0
comments
Labels: blue ocean strategy, business development, dell, google, linux, microsoft, nintendo, product development, toyota, value innovation
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.
Posted by
Michael Olenick
at
11:39 AM
0
comments
Labels: alternative industries, blue ocean strategy, business development, google, pregnancy calendar, product development
