Steve Blank Customer Development

Checklists for Chaos, The Path to Success

Posted on October 28, 2010 by steve blank

In a startup the search for a business model is chaotic, unpredictable and uncertain. Yet the Customer Development process uses a series of checklists to ensure that you walk through the Customer Discovery and Validation steps. In addition it explicitly calls for synchronization and confirmation of the steps by the entire team.

Surely a checklist and discussion gets in the way of progress in a fast moving startup? Here’s how using it helped E.piphany rather than hindered it.

Tell Them What You’re Hearing
When E.piphany was a small struggling startup in Mountain View, we had a weekly Friday afternoon beer and wine fest, no different than what hundreds of other startups were doing. (Insurance companies in the valley should check the accident rates for Friday traffic.) The company headcount was mostly engineers accomplishing the impossible on a regular basis while a few of us were outside the building trying to do what we would call today Customer Discovery and Validation.

A Checklist for Chaos
While all startups are chaotic, we had been through enough of them (E.piphany was my 8^th) to realize that we could understand our potential customer better if we had a standard checklist and process of how to approach complex enterprise sales. These started with the business model hypotheses in Customer Discovery (who’s the customer, channel, pricing model, etc.)

Customer Hypothesis Checklist

I remember that for the first few weeks of the company, my partner Ben and I would give the usual rah-rah platitudes about how great things were going to motivate the engineers. Then one week Ben turned to me and said, “Why don’t you really tell them what you’re doing and what you’re hearing.” Uh oh. Thinking about all the ups and downs of sales in a startup and twists and turns in strategy and positioning I wondered if it would be demoralizing. “Do you think they can handle the truth?” We talked about it and realized our motto for our weekly meeting would be, “Don’t panic when we change the strategy. Only panic if we ask you to rearchitect the product.” (Today’s version would be “Don’t worry when we pivot the business model, only panic if we ask you to develop the product with a Waterfall methodology.”)

Sharing the Checklist
Soon after, our Friday’s meetings would start with me describing the highs and lows of the week: who we called on, what they said and what happened (essentially walking engineering through the series of checklists as we went through Customer Discovery and Validation. And what I had to report was mostly us getting a “not interested” or “we don’t get it” from a prospective customer.

Almost immediately the most unexpected things started happening at our Friday meetings.

Don’t Treat Them Like Mushrooms
First, I thought that not pumping up engineering every week would demotivate the team. Reality turned out 180 degrees from what I expected. Engineering was much smarter. When it became clear that my partner and I were not going to treat them like mushrooms (keep them in the dark and feed them sx!t) but let them know what was really going on, they engaged on a much different level.

You’re Explaining it Wrong
Second, as I was reporting on my sales calls a few of the engineers realized that I was describing technical professionals in large companies who were just like them. When I detailed how I was explaining the product, our own engineers said, “You’re explaining it wrong. Even I wouldn’t buy it from us if you told me that.” The first time I heard that I was speechless. Who the hell were these engineers telling me how to market and sell our product? My first instinct was to cycle through all the “my business card says I’m the expert here and you just write code.”

Then I realized – they were right. Our engineers were just like the customer, and if they didn’t think our product description made sense, no one else would. So in front of the entire company, I threw out our positioning and we started to discuss how to better articulate what we were doing. (I think we invented our meta-data architecture diagram that Friday.) It was great to realize that instead of just me trying to figure out customer feedback, that every Friday I’d have the collective wisdom of engineering engaged.

Confirming the Checklist
Synchronizing our Discovery and Validation had a third benefit. Engineering now felt that they had a stake in making the process better and took a great interest in that mysterious and elusive “customer.” Soon engineers were spending lots of time talking to customers. More importantly they had a vested interest in getting the process right.

Synchronizing the Discovery and Validation checklists with the entire company made us collectively smarter, faster and gave us a shared understanding of our objective – build great products that customers wanted.

Checklists and synchronization were part of the reason why we grew from $0 to $125 million in three years.

Lessons Learned

Customer Discovery and Validation in any type of startup requires a series of checklists (see Appendix B of the Four Steps to the Epiphany)

The checklists require the team to share their findings for confirmation and synchronization

Listen to the post here: Download the Podcast here

Filed under: Business Model versus Business Plan, Customer Development, E.piphany | 12 Comments »

Entrepreneurship as a Science – The Business Model/Customer Development Stack

Posted on October 25, 2010 by steve blank

Over the last 50 years engineers have moved from building computers out of individual transistors to building with prepackaged logic gates. Then they adopted standard microprocessors (e.g. x86, ARM.) At the same time every computer company was writing its own operating system. Soon standard operating systems (e.g. Windows, Linux) emerged. In the last decade open source software (e.g LAMP) emerged for building web servers.

Each time a standard solution emerged, innovation didn’t stop. It just allowed new innovation to begin at a higher level.

In this post I want offer a solution stack for Entrepreneurship. It’s the combination of Business Model Design and Customer Development.

Business Model Design
Today every business organization from startup to large company uses the words “business model.” Some use it with certainty like they know what it means. Others use it with an implied question mark realizing they don’t have a clue to its components.

Alexander Osterwalder and Yves Pigneur defined a business model as how an organization creates, delivers, and captures value. More importantly they showed how any company’s business model could be defined in 9 boxes. It’s an amazing and powerful tool. It instantly creates a shared visual language while defining a business. Their book “Business Model Generation,” is the definitive text on the subject. (And their forthcoming Business Model Toolbox is a killer iPad app for business strategy.)

Business Model Canvas

Yet as powerful as the Business Model Canvas (a template with the nine blocks of a business model) is, at the end of the day it was a tool for brainstorming hypotheses without a formal way of testing them.

Business Model Design Gets Dynamic, Customer Development Gets Strategic
One of the key tenets of Customer Development is that your business model is nothing more than a set of untested hypotheses. Yet Customer Development has no structured and systematic way of describing a business model.

In the last year I found that the Osterwalder Business Model canvas could be used for something much more than a static planning tool. I realized that it was the launch-pad for setting up the hypotheses to test, and a scorecard for visually tracking iterations and Pivots during Customer Discovery and Validation.

Meanwhile on the other side of the world Alexander Osterwalder was coming to the same conclusion: tying the two processes together would create a “strategy stack for entrepreneurship.” We got together this weekend (along with our partners Alan Smith and Bob Dorf and my student Max Marmer) to try to integrate the two.

Business Model Design Meets Customer Development
In its simplest form the way to think about the intersection of the two processes is that you start by designing your business model. Next, each one of the 9 business model canvas boxes then directly translates into a set of Customer Discovery hypotheses that are described in Customer Development and the Four Steps to the Epiphany.

Business Model Design meets Customer Development

Pivots and Iterations
Many entrepreneurs assume that the assumptions in their original business model (or business plan if they wrote one) will be correct. Confronting the reality that one of these hypotheses is wrong (finding out you have the wrong sales channel, revenue model, target market or customer) creates a crisis.

Pivots are Business Model Insights

Tying Osterwalder’s Business Model Canvas with the Customer Development process turns these potential crises into learning opportunities called the Pivot. Customer Development forces you to get out of the building and discover and validate each one of the assumptions behind the business model. A Pivot is when reality leads you to change one or more business model hypotheses. The result is an updated business model not a fired VP of Sales.

The Pivot turns a failed business model hypotheses into insight.

The Business Model/Customer Development Stack
We’ll have more to say about combing these two methodologies in future posts.

Lessons Learned

Business Model design is the standard for describing a business model

Customer Development is the standard for testing business model hypotheses

The two are the strategy stack for entrepreneurship

Filed under: Business Model versus Business Plan, Customer Development, Customer Development Manifesto | 65 Comments »

Who’s An Entrepreneur-Talk with the Kauffman Foundation

Posted on October 21, 2010 by steve blank

The Kauffman Foundation is the leading private funder of economic research related to growth and innovation in the United States. (Translation: They write checks for $100 Million dollars a year.) The Churchill Club, Silicon Valley’s largest public affairs organization, invited Carl Schramm, president and CEO of the Kauffman Foundation and I to talk about entrepreneurship. (The official title of the talk was Fresh Perspectives on Entrepreneurial Innovation and Economic Growth.) Rich Karlgaard, publisher of Forbes and co-founder of the Churchill Club refereed the event.

Carl has been been shaking up the staid world of academic entrepreneurship research for over 8 years as the head of the foundation. I think the expectation was that putting the two of us together would see the fur fly.

Instead of a brawl it turned out to be collegial, entertaining and informative.

BTW, the definition of entrepreneurship I describe at 2:50 into the video is described in detail in the post “You’re Not a Real Entrepreneur.”

Here’s a 6 minute excerpt from the talk.

Listen to the post here: Download the Podcast here

Filed under: Customer Development | 2 Comments »

Strategy is Not a To Do List

Posted on October 7, 2010 by steve blank

I had breakfast with two of my ex-students from Singapore who were building a really interesting startup. They were deep into Customer Discovery and presented a ton of customer data on the validity of their initial hypothesis – target customers, pricing, stickiness, etc. I was unprepared for what they said next. “We’re going to do a big launch of our product in three weeks.” I almost dropped my coffee. “Wait a minute, what about the rest of Customer Development? Aren’t you going to validate your hypotheses by first getting some customers?”

Without any sense of irony they said, “Oh, our investors convinced us to skip that part, because our customer feedback was all over the map and our schedule showed us launching in three weeks and they were worried that we’d run out of cash. They told us to stay on schedule.” Now I was confused, and I asked, “Well what do you guys believe – Customer Development or launch on a schedule?” Without missing a beat they said, “Oh, we believe both are right.”

I realized I was listening to them treat Customer Development as an item on their
To Do list.

Suddenly, I had a massive case of déjà vu.

Can You Pull This Off
I was VP of marketing at Ardent, a supercomputer company where a year earlier I had a painful and permanent lesson about Customer Discovery. I was smart, aggressive, young and a very tactical marketer who really hadn’t a clue about what strategy actually meant.

One day the CEO called me into his office and asked, “Steve I’ve been thinking about this as our strategy going forward. What do you think?” And he proceeded to lay out a fairly complex and innovative sales and marketing strategy for our next 18 months. “Yeah, that sounds great,” I said. He nodded and then offered up, “Well what do you think of this other strategy?” I listened intently as he spun an equally complex alternative strategy. “Can you pull both of these off?” he asked looking right at me. By the angelic look on his face I should have known that I was being set up. I replied naively, “Sure, I’ll get right on it.”

Ambushed
25 years later I still remember what happened next. All of sudden the air temperature in the room dropped by about 40 degrees. Out of nowhere the CEO started screaming at me, “You stupid x?!x. These strategies are mutually exclusive. Executing both of them would put us out of business. You don’t have a clue about what the purpose of marketing is because all you are doing is executing a series of tasks like they’re like a big To Do list. Without understanding why you’re doing them, you’re dangerous as the VP of Marketing, in fact you’re just a glorified head of marketing communications.”

I left in daze angry and confused. There was no doubt my boss was a jerk, but unlike the other time I got my butt kicked, I didn’t immediately understand the point. I was a great marketer. I was getting feedback from customers, and I’d pass on every list of what customers wanted to engineering and tell them that’s the features our customers needed. I could implement any marketing plan sales handed to me regardless of how complex. In fact I was implementing three different ones. Oh…hmm… perhaps I was missing something.

I was doing a lot of marketing “things” but why was I doing them? I had approached my activities as simply as a task-list to get through. With my tail between my legs I was left to ponder; what was the function of marketing in a startup?

Strategy is Not a To Do List, It Drives a To Do List
It took me awhile, but I began to realize that the strategic part of my job was two-fold. First, (in today’s jargon) we were still searching for a scalable and repeatable business model. My job was to test our hypotheses about who were potential customers, what problems they had and what their needs were. Second, when we found these customers, marketing’s job was to put together the tactical marketing programs (ads, pr, tradeshows, white papers, data sheets) to drive end user demand into our direct sales channel and to educate our channel about how to sell our product.

Once I understood the strategy, the To Do list became clear. It allowed me to prioritize what I did, when I did it and instantly understand what would be mutually exclusive.

Good Luck and Thanks For the Fish
My students were going through the motions of Customer Development rather than understanding the purpose behind it. It was trendy, they had read my book and to them it was just another step on the list of things they had to do. They had no deep understanding of why they were doing it. So they were at a crossroads. Since their investors had asked them to launch now, what happened if their initial assumptions were wrong?

As they left I hoped they would be really lucky.

Lessons Learned

Entrepreneurs get lots of great advice.

Most of it is mutually exclusive.

Don’t do it if you can’t explain why you’re doing it.

Or else it all becomes a To Do list.

Listen to the post here: Download the Podcast here

Filed under: Ardent, Customer Development | 22 Comments »

Why Pioneers Have Arrows In Their Backs

Posted on October 4, 2010 by steve blank

First-Mover Advantage is an idea that just won’t die. I hear it from every class of students, and each time I try to put a stake through its heart.

Here’s one more attempt in trying to explain why confusing testosterone with strategy is a bad idea.

First mover advantage – great bad idea
The phrase “first mover advantage” was first popularized in a 1988 paper by a Stanford Business School professor, David Montgomery, and his co-author, Marvin Lieberman.[1]

This one phrase became the theoretical underpinning of the out-of-control spending of startups during the dot-com bubble. Over time the idea that winners in new markets are the ones who have been the first (not just early) entrants into their categories became unchallenged conventional wisdom in Silicon Valley. The only problem is that it’s simply not true.

The irony is that in a retrospective paper ten years later (1998), [2] the authors backed off from their claims. By then it was too late. Using this idea to differentiate themselves as the hot new Silicon Valley VCs, some of his former business school students made this phrase their rallying cry. Soon every other VC was using the phrase to justify the reckless “get big fast” strategies of dot-com startups during the Internet Bubble.

Fast Followers – a better idea
In fact, a 1993 paper by Peter N. Golder and Gerard J. Tellis had a much more accurate description of what happens to startup companies entering new markets.[3] In their analysis Golder and Tellis found almost half of the market pioneers (First Movers) in their sample of 500 brands in 50 product categories failed. Even worse, the survivors’ mean market share was lower than found in other studies. Further, their study shows early market leaders (Fast Followers) have much greater long-term success; those in their sample entered the market an average of thirteen years later than the pioneers. What’s directly relevant from their work is a hierarchy showing what being first actually means for startups entering new or resegmented markets:

*Innovator*	First to develop or patent an idea
*Product Pioneer*	First to have a working model
*First Mover*	First to sell the product	47% failure rate
*Fast Follower*	Entered early but not first	8% failure rate

The Race to Fail First
What this means is that first mover advantage (in the sense of literally trying to be the first one on a shelf or with a press release) is not real, and the race to be the first company into a new market can be destructive. Therefore, startups whose mantra is “we have to be first to market” usually lose. What startups lose sight of is there are very few cases where a second, third, or even tenth entrant cannot become a profitable or even dominant player. (The rules are different in the life-sciences arena.)

Ford vs. GM, Overture vs. Google
For example, Ford was the first successfully mass produced car in the United States. In 1921, Ford sold 900,000 Model Ts for 60 percent market share compared to General Motors 61,000 Chevys, a 6 percent market share. Over the next ten years, while Ford focused on cost reductions, General Motors built a diverse and differentiated product line. By 1931 GM had 31% of the market to Ford’s 28%, a lead it has never relinquished. Just to make the point that markets are never static, Toyota, a company that sold its first car designed for the US market in 1964, is poised to surpass GM as the leader in the US market. The issue is not being first to market, but understanding the type of market your company is going to enter.

If the car business is too removed from high tech as an example, how about the story of Overture. In 1998 Goto.com, a small startup (later Overture, now part of Yahoo!), created the pay per click search engine and advertising system and demo’d it at the TED conference.

It was not until October 2000 that Google offered its version of a pay per click advertising system -AdWords -allowing advertisers to create text ads for placement on the Google search engine.

Google is a $25 billion dollar company with most of its revenue from AdWords.

Overture was acquired by Yahoo for $1.6 billion.

Implicit Customer Discovery and Validation in Fast Followers
Why do fast followers win more often? It’s pretty simple. First Movers tend to launch without really fully understanding customer problems or the product features that solve those problems. They guess at their business model and then do premature, loud and aggressive Public Relations hype and early company launches and quickly burn through their cash.. This is a great strategy if there’s a bubble occuring in your market or you are going to bet it all on flipping your company for a sale. Otherwise the jury is in. There’s no advantage. [4]

Astute fast-followers recognize that part of Customer Discovery is learning from the first-mover by looking at the arrows in their backs. Then avoiding them.

Lessons Learned

Believing in First Mover Advantage implies you understand your business model, customers problems and the features needed to solve those problems.

That’s unlikely.

Therefore you’re either going to burn through your cash or pray that the hype can help you can flip your company.

None of the market leaders in technology were the first movers

[1] Montgomery, M. Lieberman.1988 “First Mover Advantage.” Strategic Management Journal, Volume 9, Issue S1, pages 41–58, Summer 1988.

[2] Montgomery, M. Lieberman “First-mover (dis)advantages: retrospective and link with the resource-based view.” Strategic Management Journal Volume 19, Issue 12, pages 1111–1125, December 1998

[3] P. N. Golder and G. J. Tellis. 1993. “Pioneer Advantage: Marketing Logic or Marketing Legend?” Journal of Marketing Research, 30(2):158–170.

[4] Did First-Mover Advantage Survive the Dot-Com Crash? . M. Lieberman 2007

Listen to the post here: Download the Podcasts here

Filed under: Customer Development, Market Types, Marketing | 47 Comments »

Less is More, More or Less

Posted on September 27, 2010 by steve blank

In Customer Development the goal of a minimum feature set is to pare the features of the first product release to the minimum necessary for early customers.

But finding what those “minimum” features are can be an adventure.

All the Data and Not a Drop to Think
We started Epiphany to solve the “too much data but not enough insight” problem. During the 1990’s large corporations had bought different software applications to automate each part of their enterprise – finance, customer support, manufacturing, sales, etc. Yet the data these applications collected were accessed via reporting tools from the IT organization. More importantly, the data existed in “virtual silos” with each functional system walled off from the other. The finance system didn’t talk to the sales system which didn’t know the manufacturing system even existed. (Queries like – compare the sales data of green dresses versus the blue ones, with how many of each does manufacturing have in inventory, and what does finance say the gross margin by region of these product are – would be hard to answer because it required combining data from three incompatible applications.) It might take days or even weeks to get a report. And if that question led to another one, add more days or weeks to get the next answers back. And once you got the data you asked for, it still took weeks or months for a marketer to tease out any customer insight and trends from the data. And if you actually want to respond to shifting customer behavior by running a new marketing campaign (ads, email, etc.,) it would again take weeks or months.

An Epiphany
Initially our engineering team designed three products to solve these problems: an On-Line Analytical Processing (OLAP) tool – think of it as a multi-dimensional Excel to search through reams of customer data, data mining tools to search for patterns in customer data, and a campaign manager to combine all the data and generate customer specific ads/emails. And underneath these products was our own data warehouse (a place to store all this different data) and our own tools to Extract, Transformation and Load (ETL) customer information from existing enterprise applications like SAP, PeopleSoft, Oracle Financials, etc. And back then the radical notion was that you could view this information anytime and anywhere through this new technology called a web browser.

You’re An Idiot
As a founder my first job was Customer Discovery – getting out of the building to listen to customers and see whether our understanding of what problems customers had was correct, and if so whether our product as spec’d would solve that problem. Over time one of our hypothesis was that our product should be a great fit for companies who had lots of customers, tons of data on them and wanted to quickly come up with new marketing campaigns.

We had put together an advisory board, and one of our advisors was the VP of Database Marketing at Schwab. She was incredibly generous with her time and said that our system might work in their application. She introduced me to five other Database Marketing executives who essentially said, “If you get a system working at Schwab, we’ll have to buy one as well.” You couldn’t get much better than that. I thought we had found our first Earlyvangelist and first market.

But each time we met and she looked at the technical details of our system, and politely told me I was an idiot and my engineering department was even dumber. It took two meetings before I finally got what she was trying to tell me – we understood her problem all right, but our architecture was missing the most important feature to solve it. Our database schema didn’t include “householding” and without this feature was she could never buy our system. (Householding means recognizing that two or more people at the same physical address live together. This feature was crucial to direct marketers who did not want to send multiple ads to the same address.) Our data warehouse didn’t have the concept of householding in its schema. And no amount of sales and marketing hand waving was going to fix the problem.

Founder Too
My engineering co-founder and I had a great relationship. If I thought I discovered a customer with a feature we were missing he was coming out to hear it himself. Just don’t waste his time on the first “getting to know you” meetings. We had agreed that Schwab and the database marketing application sounded like the right fit for the technology so he was as eager as I was to figure out what we were missing. So now, a week later, he’s in San Francisco with me listening to the Schwab VP of Database Marketing and her engineering team go into a deep technical dive about what our software needed to do. My partner asked five or ten questions, everybody nods and the meeting was over.

What Do You Mean Page 6?
We got back into my car for the drive back from San Francisco to our office in Silicon Valley. 5 miles goes by and we’re talking about the weather. 10 miles goes by and he’s talking about his kids, and 20 miles goes by and we’re talking about my kids. Finally, unable to stand it any longer, I ask, “Ben, what are we going to do about the Householding feature that Schwab asked for?” In an innocent and deadpan voice, he replied, “Well just take a look at page 6 of our spec.” I had to think for another couple of seconds until I said, “What do you mean page 6? Our spec only has 5 pages!”

He looked at me and smiled as he said, “Not any more.”

Our first order from Schwab came the next week.

We had just iterated the product and refined the minimum feature set.

A week later we sat down to figure out what other feature we would toss out to make room for this one.

Lessons Learned

Founders’ start with a hypothesis of what the minimum feature set is.

Your customers teach you which features actually matter by whether they will buy.

You swap (not add) features as you learn what will optimize market share of earlyvangelists.

Filed under: Customer Development, E.piphany | 8 Comments »

Panic at the Pivot – Aligning Incentives By Burning the Boats

Posted on September 23, 2010 by steve blank

It’s a paradox, but early sales success in a startup can kill its chances of becoming a large successful company. The cause is often sales and marketing execs who’ve become too comfortable with an initial sales model and panic at the first sign of a Pivot. As a result they block new iterations of the business model that might take the company to the next level.

Fairchild
As I was reading a history of the startup years of Fairchild Semiconductor, I realized that a problem I thought was new – sales as an obstacle to Pivots – had occurred 50 years ago at the dawn of what would become Silicon Valley.

Fairchild, the first successful semiconductor company in the valley, was founded on two technical innovations: manufacturing transistors out of Silicon instead of the then conventional Germanium, and using a diffusion manufacturing process which enabled the production of silicon mesa transistors in batches on assembly line. (While this might sound like Greek to you, it was a revolution.)

Early on, the young company made a dramatic technical pivot when it discovered a way to build silicon planar transistors that dramatically improved reliability. (This was an even bigger revolution.) This increased reliability qualified Fairchild’s transistors for military weapons systems (airborne electronics, missile guidance systems, etc.) With orders from military subcontractors arming the cold war, Fairchild’s sales skyrocketed from $500K in 1958 to $7M in 1959 to $21M in 1960.

By the end of 1960, Fairchild was at the top of its game. In less than three years from the day it started, the company had pivoted its technology process, sales had done a masterful job of Customer Discovery and had found a sweet spot in the market and its fabrication plants were busy turning out as many transistors and diodes as they could make.

What could go wrong?

It was when engineering Pivoted again. And this time sales revolted.

The Revolution Will Not Be Televised
When Fairchild engineers realized that its planar process of manufacturing individual transistors could now be connected together on a single piece of silicon, the Integrated Circuit was born. Engineering thought this could dramatically change the way electronic systems were built, but the head of sales tried to kill the Integrated Circuit program, loudly and vociferously. Engineering was confused, why didn’t the Fairchild salesforce want a revolutionary new product line?

Over My Dead Body
From the point of view of the sales organization this new family of integrated circuits were a major distraction. The Fairchild sales team was on a roll executing a known business model – selling planar diodes and transistors into an existing market. In the transistor market, the problem was known, the customer was known and the basis of competition was known (technical features, price and delivery schedule.)

Integrated circuits were different. Unlike transistors, no one in 1960 was clamoring for the new technology. Integrated circuits were a new market. It wasn’t clear exactly what problem the product would solve, or who the customer was. In fact, the most likely customers, computer designers were openly hostile as they saw integrated circuits doing what they were supposed to be doing – designing circuits. So selling integrated circuits meant a search for a business model.

This meant that a high testosterone sales team that was busy “executing” as order takers and deal makers had to put on a different hat and become educators and consultative engineers. No way.

You Get What You Incent
What the engineers also didn’t know is that the head of Sales of Fairchild had cut a great deal on his compensation package. He was paid 1% of gross sales. While this made sense in the first few years when Fairchild was a startup, now it had unintended consequences. His salesmen were also compensated on a commission basis. Why would they want a product they had to force customers to take when they had existing products that were making them rich?

The VP of sales’ incentives led him to stifle any innovation that got in the way of selling as much of the current technology as he could – even if it meant killing the future of the company. Luckily for Fairchild and the future of the semiconductor and computer business, he quit when his compensation plan was changed.

The Land of the Living Dead
I see this same pattern in early stage startups. Early sales look fine, but often plateau. Engineering comes into a staff meeting with several innovative ideas and the head of sales and/or marketing shoot them down with the cry of “It will kill our current sales.”

The irony is that “killing our current sales” is often what you need to do. Most startups don’t fail outright, they end up in “the land of living dead” where sales are consistently just OK but never breakout into a profitable and scalable company. This is usually due to a failure of the CEO and board in forcing the entire organization to Pivot. The goal of a scalable startup isn’t optimizing the comp plan for the sales team but optimizing the long-term outcome of the company. At times they will conflict. And startup CEO’s need a way to move everyone out of their comfort zone to the bigger prize.

Burn The Boats
In 1519 Hernando Cortes landed in the Yucatan peninsula to conquer the Aztec Empire and bring their treasure back to Spain. His small army arrived in 11 boats. As they landed Cortes solved the problem of getting his team focused on what was ahead of them – he ordered them to burn the boats they came in. Now the only way home was to succeed in their new venture or die.

Pivots that involve radical changes to the business model may at times require burning the boats at the shore.

——

Every chip company in Silicon Valley is descended from Fairchild.

Lessons Learned

Sales organizations may get too comfortable to early.

Sales execs execute to their compensation plans.

Pivots are not subject to a vote in the exec staff meeting.

CEO’s and their boards make the Pivot decisions.

To force a Pivot burn the boats at the shore.

Listen to post here:

Download the Podcast here

Filed under: Customer Development | 13 Comments »

Job Titles That Can Sink Your Startup

Posted on September 13, 2010 by steve blank

I had coffee with an ex student earlier in the week that reminded me yet again why startups burn through so many early VP’s. And after 30 years of Venture investing we still have a hard time articulating why.

Here’s one possible explanation – Job titles in a startup mean something different than titles in a large company.

You Can’t Always Get What You Want
I hadn’t seen Rajiv in the two years since he started his second company. He had raised a seed round and then a Series A from a name brand Venture firm. I was glad to see him but it was clear over coffee that he was struggling with his first hiring failure. “I’ve been running our company, cycling through Customer Discovery and Validation and the board suggested that I was running out of bandwidth and needed some help in closing our initial orders. They suggested I get a VP of Sales to help.”

It was deja vu all over again. I knew where this conversation was going. “Let me guess, your VC’s helped you find a recruiter?”

“Yeah, and they were great. They helped me hire the best VP of Sales I could find. The recruiter verified all the references and he completely checked out. He was in the top 1% club at (insert the name of your favorite large company here.) He’s been in sales for almost 15 years.”

I listened as he told me the rest of the story. “I thought our new Sales VP would be out in front helping us lead Customer Validation and help us find the Pivot. That was the plan. We had talked about it in the interview and he said he understood and agreed that’s what he would do. Even when we went out to dinner before we hired him he said, he said he read the Four Steps and couldn’t wait to try this Customer Development stuff.”

“So what happened,” I asked, though I was betting I could finish the conversation for him (since I had made the same mistake.) “Well, he’s completely lost at the job. When we ask him to call on a different group of customers all he wants to do is call on the people already in his rolodex. When a customer throws us out he wants to get on to the next sales call and I want to talk about why we failed. He says great sales people don’t do that, they just keep selling. Every time we iterate even a small part of our business model or product he gets upset. When we change the company presentation it takes him days to get up to speed to the smallest change. He’s finally told us we got to stop changing everything or else he can’t sell. He was supposed to be a great VP of Sales. I’m probably going to fire him and start a search for another one, but what do I do wrong?”

“Nothing,” I said, “You got what you asked for. But you didn’t get what you need. The problem isn’t his, it’s yours. You didn’t need a VP of Sales, you needed something very different.

Companies Have Titles to Execute a Known Business Model
I offered that in an existing company job titles reflect the way tasks are organized to execute a known business model. For example, the role of “Sales” in an existing company means that:

there’s a sales team executing
a repeatable and scalable business model
selling a known product to
a well-understood group of customers
using a standard corporate presentation
with an existing price-list and
standard terms, conditions and contract

Therefore the job title “Sales” in an existing company is all about execution around a series of “knowns.”

We Use the Same Title For Two Very Different Jobs
I asked Rajiv to go through this checklist. Did he have a repeatable and scalable business model? “No.” Did he have a well understood group of customers? “No.” Did he have a standard corporate presentation? “No.” etc. Did he and his recruiter say any of this when they put together the job spec or interviewed candidates? “No.”

Then why was he surprised the executive he hired wasn’t a fit.

Startups Need Different Titles to Search For an Unknown Business Model
In a startup you need executives whose skills are 180 degrees different from what defines success in an existing company. A startup wants execs comfortable in chaos and change – with presentations changing daily, with the product changing daily, talking and with analyzing failure rather than high-fiving a success. In short you are looking for the rare breed:

comfortable with learning and discovery
trying to search for a repeatable and scalable business model
agile enough to deal with daily change, operating “without a map”
with the self-confidence to celebrate failure when it leads to iteration and Pivots

That means the function called Sales used in a large company (and the title that goes with it, “VP of Sales”) don’t make sense in a startup searching for a business model. Sales implies “execution,” but that mindset impedes (majorly screws-up) progress in searching for a business model. Therefore we need a different job function, job title and different type of person. They would be responsible for Customer Validation and finding Pivots and searching around a series of unknowns. And they would look nothing like his failed VP of Sales.

I suggested to Rajiv his problem was pretty simple. Since he hadn’t yet found a repeatable and scalable business model, his startup did not need a “VP of Sales.” The early hire he needed to help him run Customer Validation and Pivots has a very different skill set and job spec. What Rajiv needed to hire was a VP of Customer Development and part ways with his VP of Sales.

I suggested he chat with his investors and see if they agreed. “I hope they don’t make me hire another “experienced” VP of Sales,” he said as left.

Lessons Learned

Companies have titles which reflect execution of known business models

Early stage startups are still searching for their business model

Individuals that excel at execution of a process rarely excel in chaotic environments

We burn through early VP’s in startups because the job functions we are hiring for are radically different, but we are using the same titles.

Startups need to use different titles to indicate that the search for a business model requires different skills than executing a business model.

Filed under: Corporate/Gov't Innovation, Customer Development | 53 Comments »

Why Product Managers Wear Sneakers

Posted on September 2, 2010 by steve blank

I gave a talk last night to the Silicon Valley Product Management Association. It’s a San Francisco Bay Area forum for networking, jobs and education for over 500 Product Management professionals. This is one of the Silicon Valley organizations that remind you why this is a company-town whose main industry is entrepreneurship, (and a great example of an industry cluster.)

The published title of the talk was, “How to Create a $100M Business and Out Innovate your Competition.” I read that and thought, “If I knew how to do that I would have been a VC.” So instead I gave a talk I called, “Why Product Managers Need Sneakers.”

The gist of the talk was to observe that:

startups are not smaller versions of large companies
startups search for a business model, large companies execute an existing one
the skills that talented product managers bring to a large company are at best not transferable to a startup (and at worst destructive)
product managers in a startup can either be an asset or an albatross.
They’re an albatross if they perform as they do in a large company, and believe that they “own” customer interaction, feedback to engineering and authoring market requirements documents.
They’re an asset to a startup if they understand that their job is to get the founder outside the building and in front of customers.
They can be the scorekeepers in Customer Discovery and Validation as the company iterates and pivots the business model and refines the minimum feature set.

“Why Product Managers Wear Sneakers” was a reference to the amount of running around outside the building (with the founder) product managers will need to do in a startup. Except they won’t be called Product Managers. In a startup they will be part of the Customer Development team.

If you’ve seen my talks before you can skip forward to slide 19.

Listen to this post here: Download this Podcast here

Filed under: Corporate/Gov't Innovation, Customer Development | 23 Comments »

The Non-Dummies Guide to Customer Discovery

Posted on August 26, 2010 by steve blank

Customer Development is a stupidly simple idea. It’s one that you can describe in 30-seconds or less. But it took me 3 years and almost 300 pages of 10-point type to describe the concept in my book The Four Steps to the Epiphany. Unlike a traditional business book, The Four Steps is more akin to a reference manual for how to “engineer” a startup – from the initial search for a repeatable business model all the way through the management techniques to transition to a company. Entrepreneurs who use it effectively have dog-eared pages marked with sticky notes.

Enter Brant Cooper and Patrick Vlaskovits who looked at my text as the equivalent of War and Peace. They decided that what the world needed was a simple explanation of the key concepts of Customer Discovery – the first of the four steps of Customer Development. Their book The Entrepreneur’s Guide to Customer Development: A cheat sheet to the Four Steps to the Epiphany does just that. If you are interested in Customer Development, there’s now a quick and simple way to get up to speed.

This is a book you should have on your shelf.