Blue Ocean Strategy & Customer Development – Making Products That Sell

Author: tracysigler | Posted: March 18th, 2011 | | Tags: , , , | No Comments »

The more we work on strategy at AVLM HQ the more I become aware of the overlap of Blue Ocean Strategy and Customer Development. Both are attempts to get at what customers really want so you can develop products they will really buy.

Customer Development interviews for us, so far, have followed Ash Maurya’s methodology of asking potential customers to react to, and rank order what we hypothesized as the main pain points for marketing their businesses. We also ask them if they have other challenges we haven’t listed. The process from there involves creating a “minimum viable product,” getting feedback, possibly through follow-up interviews, and then iterating over and over. That’s a major over-simplification, but good enough for now.

Blue Ocean Strategy is possibly less “greenfield” than Customer Development (as I understand it) in that it begins by looking at the typical “value curve” for a given business category and aims to diverge, significantly. The value curve is a simple chart created by plotting various customer buying criteria such as price, features, etc. on a high-to-low axis. In a nutshell, you want to approximate the industry norms, then create a value curve of your own that diverges by eliminating what customers don’t want and adding what they do.

You get to this new value curve by answering four questions. From the book Blue Ocean Strategy:

  • Which of the factors that the industry takes for granted should be eliminated?
  • Which factors should be reduced well below the industry’s standard?
  • Which factors should be raised well above the industry’s standard?
  • Which factors should be created that the industry has never offered?

This is where I think the Customer Development process of interviewing prospective customers can help. At least that’s how we’re approaching it. Real world prospects are telling us what they must have and will pay for, and what they don’t care about. That’s fantastic, but the “create” question is where I think the real value will be uncovered.

 

Customers may not be able to tell you what they really want because they haven’t even imagined it yet. As helpful and Customer Development and Blue Ocean Strategy are, I’m certain that creating any world-changing value innovation is going to take more than using the prescribed frameworks. Timing? Luck? Vision? Any of those will certainly help.


Customer Development and Getting Punched in the Face

Author: tracysigler | Posted: February 24th, 2011 | | Tags: , , , , , , , , | 2 Comments »

Yesterday Kevin and I “got out of the building” and conducted our first “customer development” interview with someone we know, who has a business in a market we are targeting as part of our growth strategy.

My short, simplistic explanation of Customer Development is “asking prospective customers what they really want and then giving it to them, initially in the simplest version of the product worth doing.”

Much of our education on the topic came from two great ebooks:

The Entrepreneur’s Guide to Customer Development
A “cheat sheet” to The Four Steps to the Epiphany

By Brant Cooper & Patrick Vlaskovits
Foreword by Steven Gary Blank

Running Lean
A systematic process for iterating your web application from Plan A to a plan that works
By Ash Maurya

Cooper and Vlaskovits explain it this way:

Customer Development is a four-step framework to discover and validate that you have identified the market for your product, built the right product features that solve customers’ needs, tested the correct methods for acquiring and converting customers, and deployed the right resources to scale the business.

We are doing this because we’re trying to develop a product that is genuinely innovative in meeting our customers’ needs. Up to this point we’ve put a lot of thought into customer development, created our hypotheses to test, made a list of friendly contacts to interview first, and carefully composed our script for the meetings.

From our very first interview we learned that we may not even be asking the right questions. Moreover, prospective customers may not care at all about what we are already working hard to deliver. For example, in-depth reporting and analysis may put them to sleep and the metrics they care about may be much simpler to monitor.

Our hypothesis contained what we believed were the three major pain points our “minimum viable product” would attempt to alleviate. But this interviewee considered one of them irrelevant. Oof! I mean, great! Now we won’t waste time on that. If we get similar responses over the next several interviews we will “pivot,” to use a term from the “lean startup” movement, and point our next Minimum Viable Product in a different direction.

Like Mike Tyson said: “Everybody has a plan until they get punched in the face.” Our first interview was a haymaker that connected. But if we hadn’t put together a testable hypothesis in the first place, and got in the ring we wouldn’t have learned anything. Scarred but smarter.

The authors of The Entrepreneur’s Guide to Customer Development say that if you learn only one thing from their book it should be: “Question your assumptions.” We are definitely doing that, and I can’t wait to get more input from other prospective customers.

We’ll be posting more about customer development, our experiences with it, and related topics like “Blue Ocean Strategy” in the near future.