Tag Archives: idea validation

How to Test Your Business Model

How to Test Your Business Model

GUEST POST from Mike Shipulski

Sometimes we get caught up in the details when we should be working on the foundation. Here’s a rule: If the underlying foundation is not secure, don’t bother working on anything else.

If you’re working on a couple new technologies, but the overall business model won’t be profitable, don’t work on the new technologies. Instead, figure out a business model that is profitable, then do what it takes (technology, simplification, process improvement) to make it happen. But, often, that’s not what we do.

Often, we put the cart before the horse. We create projects to make prototypes that demonstrate a new technology, but the whole business premise is built on quicksand. There’s a reason why foundations are made from concrete and not quicksand. It’s because you can build on top of a base made of concrete. It supports the load. It doesn’t crack, nor does it fall apart. Think Pyramid of Giza.

Because foundations are big and expensive they can be difficult and expensive to test. For example, if an innovation is based on a new foundation, say, a new business model, building a physical prototype of the new business model is too expensive and the testing will not happen. And what usually happens is the foundation goes untested, the higher level technology work is done, the commercialization work is completed and the business model fails because it wasn’t solid.

But you don’t have to build a full-scale prototype of the Pyramid of Giza to test if a pyramid will stand the test of time. You can build a small one and test it, or you can run an analysis of some sort to understand if the pyramid will support the weight. But what if you want to test a new business model, a business model that has never been done before, using new products and services that have never seen the light of day? What do you do? In this case, it doesn’t make sense to make even a scale model. But it does make sense to create a one page sales tool that describes the whole thing and it does make sense to show it to potential customers and ask them what they think about it.

The open question with all new things is – will customers like it enough to buy it. And, it’s no different with the business model. Instead of creating a new website, staffing up, creating new technologies and products, create a one-page sales tool that describes the new elements and show it to potential customers. Distill the value proposition into language people can understand, describe the novelty that fuels the value, capture it on one page, show it to customers, and listen.

And don’t build a single, one-page sales tool, build two or three versions. And then, ask customers what they think. Odds are, they’ll ask you questions you didn’t think they’d ask. Odds are, they’ll see it differently than you do. And, odds are, you’ll have to incorporate their feedback into an improved version of the business model. The bad new is you didn’t get it right. The good news is you didn’t have to staff up and build the whole business model, create the technologies and launch the products. And more good news – you can quickly modify the one-page sales tool and go back to the customers and ask them what they think. And you can do this quickly and inexpensively.

Don’t develop the technology until you know the underlying business model will be profitable. Don’t staff up until you know if the business model holds water. Don’t launch the new products until you verify customers will buy what you want to sell.

Creating a new business model from scratch is an expensive proposition. Don’t build it until you invest in validating it’s worth building.

The worst way to validate a business model is by building it.

Image credit: Gemini

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Ideas Are Validated Forwards Not Backwards

Ideas Are Validated Forwards Not Backwards

GUEST POST from Greg Satell

In 2007, our media company in Ukraine completed its IPO and would soon be valued at $100 million. For a rough and tumble organization that, just a few years before, was a relatively small business, it was exhilarating. We had big plans and were eager to execute them. It was a “damn the torpedoes, full speed ahead” moment.

We also had an innovative strategy that we thought was a clear winner — a bet on Ukrainian language media. Although the Russian language was dominant at the time, we thoroughly researched the idea and found that a large part of the market said they preferred Ukrainian. To grab the opportunity, we launched three major brands in a year.

It was a disaster. Although the first launch was cause for concern, we were moving so fast the other two were too far along to stop. Then the 2008 global financial crisis hit and we were soon struggling to stave off bankruptcy. It was a brutal lesson. You can research an idea, but you never really know what you have until you’ve actually tested it in the marketplace.

The Rule Following Paradox

The Philosopher Ludwig Wittgenstein famously wrote, “no course of action could be determined by a rule, because every course of action can be made out to accord with the rule.” He meant that every rule is subject to some interpretation and, given varying contexts, interpretations are bound to vary.

That’s essentially what happened to us. We did our research and combed through all the evidence. Television and advertising was, by law, in Ukrainian and not Russian. Consumer surveys consistently showed that a significant portion of the Ukrainian public preferred Ukrainian language media. There were plenty of signs that we were on to something.

Given that analysis, our course seemed clear. We should not only launch Ukrainian language products, we should proceed at a rapid pace so that we could move out ahead of the pack. Surely, once competitors saw how big the opportunity was, they would pounce and our opportunity would be squandered.

Except that there was no opportunity. We weren’t acting on facts, but our interpretation of them and that interpretation was horribly, drastically wrong. To make matters worse, all this was happening as the Ukrainian media market was hitting its peak and the world was about to head off a cliff into the worst financial crisis since the Great Depression.

Survivorship Bias

Business school professors and consultants gain fame—not to mention large fees—when they are able to define a novel concept or success factor. If you are able to isolate one thing that organizations should do differently, you have a powerful product to sell. A single powerful insight can make an entire career, which is probably why so many cut corners.

For example, in their study of 108 companies, distinguished INSEAD professors W. Chan Kim and Renée Mauborgne found that “blue ocean” products, those in new categories without competition, far outperform those in the more competitive “red ocean” markets. Their book, Blue Ocean Strategy, was an immediate hit, selling over 3.5 million copies.

Bain consultants Chris Zook and James Allen’ book, Profit from the Core, boasted even more extensive research encompassing 200 case studies, a database of 1,854 companies, 100 interviews of senior executives and an “extensive review” of existing literature. They found that firms that focused on their ”core” far outperformed those who strayed.

It doesn’t take too much thinking to start seeing problems. How can you both “focus on your core” and seek out “blue oceans”? It betrays logic that both strategies could outperform one another. Also, how do you define “core?” Core markets? Core capabilities? Core customers? While it’s true that “blue ocean” markets lack competitors, they don’t have any customers either. Who do you sell to?

Yet there is an even bigger, more insidious problem called survivorship bias. Notice how “research” doesn’t include firms that went out of business because there were no customers in those “blue oceans” or because they failed to diversify outside of their “core.” The data only pertains to those that survived.

The Problem With Case Studies

The gold standard for research is randomized, double blind trials in which some of the subjects receive some sort of intervention, a control group gets a placebo and no one, not even those conducting the study, know which subjects are in which group. This design minimizes the chance of bias affecting results.

Yet this type of design is impractical for studying real businesses that are competing in the marketplace. So researchers largely depend on case studies in which participants are interviewed after the fact. These can be helpful in that they offer first-person perspectives of events and their context, but have obvious problems.

First, much like in Wittgenstein’s rule-following paradox, a lot is left up to interpretation. There are rarely more than a half-dozen people interviewed and they tend to be insiders. We almost never hear from competitors, customers or lower level employees. Then the researchers themselves bring their own biases to what they see and hear.

There are also issues with survivorship bias. Clearly, key players will be much more forthcoming about successes than failures. So we tend to hear about strategies that worked when, for all we know, those same strategies may have failed in other organizations and other contexts. There’s simply no real way for us to know.

Incidentally, researchers did a series of case studies on our company and I was struck by how much they depended on who was interviewed. While there wasn’t anything factually wrong, a different sample of perspectives would have led to very different interpretations.

Adopting A Bayesian Strategy

Traditionally, strategy has been seen as a game of chess. Wise leaders survey the board of play, plan their moves carefully and execute flawlessly. That’s always been a fantasy, but it was close enough to reality to be helpful. Organizations could build up sustainable competitive advantage by painstakingly building up bargaining power within the value chain.

Yet as Mike Tyson pointed out, “everybody has a plan until they get hit.” We can research and plan all we want, but the real world is a messy place. The facts, as we see them, are really just interpretations of the data we have available to us. Invariably, there are other data we’re not seeing and, even that which we have in front of us, can be interpreted in multiple ways.

That’s why we need to take a more Bayesian approach to strategy, in which we don’t pretend that we have the “right strategy,” but endeavor to make it less wrong over time. As Rita Gunther McGrath has put it, it’s no longer as important to “learn to plan” as it is to “plan to learn.” We need to be more iterative, see what works and change course as needed.

Today, instead of thinking about strategy as a game of chess, we’d do better to envision an online role-playing game, in which you bring certain capabilities and assets and connect with others to go on quests and discover new things along the way. Unlike chess, where everyone knows that their objective is to capture the opponent’s king, we need to expect the rules to change over time and adapt accordingly.

— Article courtesy of the Digital Tonto blog
— Image credit: Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.