Customer Development Talk Startup2Startup

Eric Ries of Lean Startup fame and the author of the Lessons Learned blog joined me at Startup2Startup for a joint Customer Development talk. Thanks to Dave McClure and Leonard Speiser for the opportunity to speak.

The Customer Development talk can be seen here74HGZA3MZ6SV

Part 1

Part 2

Part 3

The slides are here.

If you’ve never seen Eric’s Lean Startup presentation, take a few minutes to at least watch his part. It starts at ~40:30 in the video.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to FurlAdd to Newsvine

Preparing for Chaos – the Life of a Startup

I just finished reading Donovan Campbell’s eye-opening book, “Joker One“, about his harrowing combat tour in Iraq leading a Marine platoon. This book may be the Iraq war equivalent of “Dispatches” which defined Vietnam for my generation.  (Both reminded me why National Service would be a very good idea.)

Campbell describes how he tried to instill in his troops the proper combat mentality.

I’ve paraphrased his speech into the language of a startup.  It’s eerily similar.

Startups are inherently chaos. As a founder you need to prepare yourself to think creatively and independently, because more often than not, conditions on the ground will change so rapidly that the original well-thought-out business plan becomes irrelevant.

If you can’t manage chaos and uncertainty, if you can’t bias yourself for action and if you wait around for someone else to tell you what to do, then your investors and competitors will make your decisions for you and you will run out of money and your company will die.  74HGZA3MZ6SV

Therefore the best way to keep your company alive is to instill in every employee a decisive mindset that can quickly separate the crucial from the irrelevant, synthesize the output, and use this intelligence to create islands of order in the all-out chaos of a startup.

Every potential startup founder should think about their level of comfort operating in chaos and uncertainty.  It may not be for you.

“Speed and Tempo” – Fearless Decision Making for Startups

”If things seem under control, you are just not going fast enough.”

Mario Andretti

I was catching up over breakfast with a friend who’s now CEO of his own startup. One of the things he mentioned was that when it came to decision-making he still tended to think and act like an engineer. Each and every decision he made was carefully thought through and weighed. And he recognized it was making his startup feel and act like a big ponderous company. 74HGZA3MZ6SV

Speed = Execution Now

General George Patton said, “A good plan violently executed now is better than a perfect plan next week.” The same is true in your company. Most decisions in a startup must be made in the face of uncertainty. Since every situation is unique, there is no perfect solution to any engineering, customer or competitor problem, and you shouldn’t agonize over trying to find one. This doesn’t mean gambling the company’s fortunes on a whim. It means adopting plans with an acceptable degree of risk, and doing it quickly. (Make sure these are fact-based, not faith-based decisions.) In general, the company that consistently makes and implements decisions rapidly gains a tremendous, often decisive, competitive advantage.

Decision Making Heuristics for the Startup CEO

The heuristic I gave my friend was to think of decisions of having two states: those that are reversible and those that are irreversible. An example of a reversible decision could be adding a product feature, a new algorithm in the code, targeting a specific set of customers, etc. If the decision was a bad call you can unwind it in a reasonable period of time. An irreversible decision is firing an employee, launching your product, a five-year lease for an expensive new building, etc. These are usually difficult or impossible to reverse.

My advice was to start a policy of making reversible decisions before anyone left his office or before a meeting ended. In a startup it doesn’t matter if you’re 100% right 100% of the time. What matters is having forward momentum and a tight fact-based feedback loop (i.e. Customer Development) to help you quickly recognize and reverse any incorrect decisions. That’s why startups are agile. By the time a big company gets the committee to organize the subcommittee to pick a meeting date, your startup could have made 20 decisions, reversed five of them and implemented the fifteen that worked.

Tempo = Speed Consistently Over Time

Once you learn how to make decisions quickly you’re not done.  Startups that are agile have mastered one other trick – and that’s Tempo – the ability to make quick decisions consistently over extended periods of time.  Not just for the CEO or the exec staff, but for the entire company.  For a startup Speed and Tempo need to be an integral part of your corporate DNA.

Great startups have a tempo of 10x a large company.

Try it.

Listen to the blog post here
Download the podcast here

SuperMac War Story 6: Building The Killer Team – Mission, Intent and Values

If you don’t know where you’re going, how will you know when you get there?

At the same time we were educating the press, we began to educate our own marketing department about what exactly we were supposed to be doing inside the company. During the first few weeks I asked each of my department heads what they did for marketing and the company. When I asked our trade show manager she looked at me like I was the house idiot and said, “Steve, don’t you know that my job is to set up our trade show booth?” The other departments in marketing gave the same answers; the product-marketing department said their job was to write data sheets. But my favorite was when the public relations manager said, “we’re here to write press releases and answer the phone in case the press calls.”

If these sound like reasonable answers to you, and you are in a startup/small company, update your resume.

Titles are not your job
When I pressed my staff to explain why marketing did trade shows, or wrote press releases or penned data sheets, the best I could get was “why that’s our job.” It dawned on me that we had a department full of people who were confusing their titles with what contribution they were supposed to be making to the company. While their titles might be what their business cards said, titles were not their job – at least in any marketing department I was running.

Titles are not the same as what your job is. This is a big idea.

Department Mission Statements – What am I Supposed to Do Today
It wasn’t that we somehow had inherited dumb employees. What I was actually hearing was a failure of management. No one had sat the marketing department down and defined what our department Mission (with a capital “M”) was.

Most startups put together a corporate mission statement because the CEO remembered seeing one at their last job, or the investors said they needed one. Most companies spend an inordinate amount of time crafting a finely honed corporate mission statement for external consumption and then do nothing internally to actually make it happen. (And to this day I can’t remember if we even had a corporate mission statement.) What I’m about to describe here is quite different.

What was missing in SuperMac marketing was anything in writing that gave the marketing staff daily guidance on what they should be doing. The first reaction from my CEO was, “that’s why you’re running the department.” And yes, we could have built a top-down, command-and-control hierarchy. But what I wanted was an agile marketing team capable of operating independently without day-to-day direction.

So what we needed to do was to craft a Departmental Mission statement that told everyone why they come to work, what they need to do, and how they will know they have succeeded. And it was going to mention the two words that SuperMac marketing needed to live and breathe: revenue and profit.

Five Easy Pieces – The Marketing Mission
After a few months of talking to customers, talking to our channel and working with sales we defined the marketing Mission (our job) was to:
Help Sales deliver $25 million in sales with a 45% gross margin. To do that we will create end-user demand and drive it into the sales channel, educate the channel and customers about why our products are superior, and help Engineering understand customer needs and desires. We will accomplish this through demand-creation activities (advertising, PR, tradeshows, seminars, web sites, etc.), competitive analyses, channel and customer collateral (white papers, data sheets, product reviews), customer surveys, and market requirements documents.

This year, marketing need to provide sales with 40,000 active and accepted leads, company and product name recognition over 65% in our target market, and five positive product reviews per quarter. We will reach 35% market share in year one of sales with a headcount of twenty people, spending less than $4,000,000.

  • Generate end user demand (to match our revenue goals)
  • Drive that demand into our sales channels
  • Value price our products to achieve our revenue and margin goals (create high-value)
  • Educate our sales channel(s)
  • Help engineering understand customer needs

That was it. Two paragraphs, Five bullets. It didn’t take more.

Working to the Mission
Having the mission in place meant that our marketing team could see that what mattered was not what their business card said, but how much closer did their work move our department to completing the mission. Period.

It wasn’t an easy concept for everyone to understand.

Building the Team
My new Director of Marketing Communications turned the Marcom departments into a mission-focused organization. Her new tradeshow manager quickly came to understand that their job was not to set up booths. We hired union laborers to do that. A trade show was where our company went to create awareness and/or leads. And if you ran the tradeshow department you owned the responsibility of awareness and leads. The booth was incidental. I couldn’t care less if we had a booth or not if we could generate the same amount of leads and awareness by skydiving naked into a coffee cup.

The same was true for PR. My new head of Public Relations quickly learned that my admin could answer calls from the press. The job of Public Relations at SuperMac wasn’t a passive “write a press release and wait for something to happen activity.” It wasn’t measured by how busy you were, it was measured by results. And the results weren’t the traditional PR metrics of number of articles or inches of ink. I couldn’t care less about those. I wanted our PR department to get close and personal with the press and use it to generate end user demand and then drive that demand into our sales channel. (The Potrero benchmark strategy was one component of this creating end user demand through PR.) We were constantly creating metrics to see the effects of different PR messages, channels and audiences on end-user purchases.

The same was true for the Product Marketing group. I hired a Director of Product Marketing who in his last company had ran its marketing and then went out into the field and became its national sales director. He got the job when I asked him how much of his own marketing material his sales team actually used in the field. When he said, “about ten percent,” I knew by the embarrassed look on his face I had found the right guy. And our Director of Technical Marketing was superb at understanding customer needs and communicating them to engineering.

Teaching Mission Intent – What’s Really Important
With a great team in place, the next step was recognizing that our Mission statement might change on the fly. “Hey, we just all bought into this Mission idea and now you’re telling us it can change?!”

We introduced the notion of Mission intent. What is the company goal behind the mission. In our case it was to sell $25 million in graphics boards with 45% gross margin. The idea of intention is that if employees understand the thinking behind the mission, they can work collaboratively to achieve it.

But we recognized that there would be time marketing would screw up, making the mission obsolete (i.e. we might fail to deliver 40,000 leads.) Think of intention as the answer to the adage, “When you are up to your neck in alligators it’s hard to remember you were supposed to drain the swamp.” For example; our mission said that the reason why marketing needed to deliver 40,000 leads and 35% market share, etc, was so that the company could sell $25 million in graphics boards at 45% gross margin.

What we taught everyone is that the intention is more enduring then the mission. (“Let’s see, the company is trying to sell $25 million in graphics boards with 45% gross margin. If marketing can’t deliver the 40,000 leads what else can we do for sales to still achieve our revenue and profitability?”) The mission was our goal, but based on circumstances it may change, but the Intent was immovable.

When faced with the time pressures of a startup, too many demands and too few people, we began to teach our staff to refer back to the five Mission goals and the Intent of the department. When stuff started piling up on their desks, they learned to ask themselves, “Is what I’m working on furthering these goals? If so, which one? If not, why am I doing it?”

They understood the mission intent was our corporate revenue and profit goals.

Core Values
Even after we had Mission and Intent down pat, one of the things that still drove me crazy was when we failed to deliver a project for sales on time or we missed a media deadline, everyone in my department had an excuse. (Since a large part of marketing was as a service organization to sales, our inability to deliver on time meant we weren’t holding up our end of the mission.) I realized that this was a broken part of our culture, but couldn’t figure out why. And one day it hit me that when deadlines slipped there were no consequences.

And with no consequences we acted as if schedules and commitments really didn’t matter. I heard a constant refrain of, “The channel sales brochure was late because the vendor got busy and they couldn’t meet the original deadline.” Or, “the January ad had to be moved into February because my graphic artist was sick but I didn’t tell you assuming it was OK.” Or, “we’re going to slip our product launch because the team thought they couldn’t get ready in time.” We had  a culture that had no accountability, and no consequences –  instead there were simply shrugged shoulders and a litany of excuses.

This had to change. I wanted a department that could be counted on delivering. One day I simply put up a sign on my door that said, “No excuses accepted.” And I let the department know what I meant was we were all going to be “accountable.”

What I didn’t mean was “deliver or else.” By accountable I meant, “we agreed on a delivery date, and between now and the delivery date it’s OK if you ask for help because you’re stuck, or something happened outside of your control. But do not walk into my office the day something was due and give me an excuse. It will cost you your job.” That kind of accountable.

And, “since I won’t accept those kind of excuses, you are no longer authorized to accept them from your staff or vendors either.” The goal wasn’t inflexible dates and deadlines, it was no surprises and collective problem solving.  After that, we  spent a lot more time working together to solve problems and remove obstacles in getting things done on-time.

Over time, accountability, execution, honesty and integrity became the cornerstones of our communication with each other, other departments and vendors.

  • We wouldn’t give excuses for failures, just facts and requests for help
  • We wouldn’t accept excuses for failures, just facts, and offer help
  • Relentless execution
  • Individual honesty and integrity

That was it. Four bullets. It defined our culture.

Why Do It
By the end of the first year our team had jelled. It was a department willing to exercise initiative, had the judgment to act wisely, and an eagerness to accept responsibility.

I remember at the end of a hard week my direct reports came into my office just to talk about the weeks little victories. And there was a moment as they shared their stories, that they all began to realize that our company (one that had just come off of life support) was beginning to kick the rear of our better-funded and bigger competitors.

We all marveled in the moment.

What did I learn so far?

  • Push independent execution of tasks down to the lowest possible level
  • Give everyone a shared Mission Statement: why they come to work, what they need to do, and how they will know they have succeeded.
  • Share Mission Intent for the big picture for the Mission Statement
  • Build a team comfortable with independent Mission execution
  • Agree on Core Values to define your culture

The “Good” Student

I saw an article in the New York Times about Google’s hiring practices that reminded me of the differences between great big successful technology companies and small scrappy startups.

Marissa Mayer, Google on hiring

I love Google.I think its one of the smartest companies out there. And it hires very smart people from the best schools. And if you meet their criteria of a “good student”, you ought to go to work there.Or Microsoft or IBM. 74HGZA3MZ6SV

Nothing makes me happier then to see my students getting great grades (and as they can tell you I make them very work hard for them.)

But what I remind them is that great grades and successful founders/technology entrepreneurs have at best a zero correlation (and anecdotal evidence suggests that the correlation may actually be negative.)

BTW, by the standards mentioned in the Times article, the following people would never have been interviewed or hired at Google.

College Dropouts-Bill Gates, Steve Jobs, Larry Ellison

College Dropouts – Bill Gates, Steve Jobs, Larry Ellison

These guys realized that customers don’t ask for your transcript.

There’s a big difference between being an employee at a great technology company and having the guts to start one.  You don’t get grades for having resiliency, curiosity, agility, resourcefulness, pattern recognition and tenacity.

You just get successful.

There’s a Pattern Here

After my eighth and likely final startup, E.piphany, sitting in a ski cabin, it became clear that there is a better a way to manage startups. Joseph Campbell’s insight of the repeatable patterns in mythology is equally applicable to building a successful startup. All startups (whether a new division inside a larger corporation or in the canonical garage) follow similar patterns—a series of steps which, when followed, can eliminate a lot of the early wandering in the dark. Looking back on startups that have thrived reflect this pattern again and again and again.

So what is it that makes some startups successful and leaves others selling off their furniture? Simply this: startups are not small versions of large companies.  Yet the processes that early-stage companies were using were identical to that of large corporations. In hindsight it appeared clear that startups that survive the first few tough years do not follow the traditional product-centric launch model espoused by product managers or the venture capital community. Through trial and error, hiring and firing, successful startups all invented a parallel process to product development. In particular, the winners invent and live by a process of customer learning and discovery. It’s a process that doesn’t exist in large companies with existing customers and markets.  But it is life and death for a new venture.

I call this process “Customer Development,” a sibling to “Product Development,” and each and every startup that succeeds recapitulates it, knowingly or not.

The “Customer Development” model is a paradox because it is followed by successful startups, yet articulated by no one.  Its basic propositions are the antithesis of common wisdom yet they are followed by those who succeed.

It is the path that is hidden in plain sight.

Listen to the podcast here

Download the podcast here

Out of the Ashes – Something Isn’t Quite Right

“Customer Development” was born four years earlier and 200 miles away on Sandhill Road.  I was between my 7th and 8th and final startup; licking my wounds from Rocket Science, the company I had cratered as my first and last attempt as a startup CEO. I was consulting for the two venture capital firms who between them put $12 million into my last failed startup. (My mother kept asking if they were going to make me pay the money back. When I told her they not only didn’t want it back, but were trying to see if they could give me more for my next company, she paused for a long while and then said in a very Russian accent, “Only in America are the streets paved with gold.”  It was a long way from Ellis Island.) Both venture firms sought my advice for their portfolio companies. Surprisingly, I enjoyed seeing other startups from an outsider’s perspective. To everyone’s delight (and my surprise,) I usually could quickly see what needed to be fixed. At about the same time, two newer companies asked me to join their boards.  Between the board work and the consulting, I enjoyed my first-ever corporate “out-of-body experience.”

No longer personally involved, I became a dispassionate observer. From this new vantage point I began to detect something deeper than I had ever seen before: there seemed to be a pattern in the midst of the chaos. Arguments that I had heard at my own startups seem to be repeated at others. The same issues arose time and again: big company management styles versus entrepreneurs wanting to shoot from the hip, founders versus professional managers, engineering versus marketing, marketing versus sales, missed schedule issues, sales missing the plan, running out of money, raising new money. I began to gain an appreciation of how world-class venture capitalists develop pattern recognition for these common types of problems. “Oh yes, company X, they’re having problem 343. Here are the six likely ways that it will resolve, with these probabilities.” No one was actually quite that good, but some VCs had “golden guts” for these kinds of operating issues.

Yet something in the back of my mind bothered me. If great venture capitalists could recognize and sometimes predict the types of problems that were occurring, didn’t that mean that the problems were structural rather than endemic? Wasn’t something fundamentally wrong with the way everyone organizes and manages startups? Wasn’t it possible that the problems in every startup were somehow self-inflicted and could be ameliorated with a different structure? Yet when I talked to my venture capital friends, they said, “Well, that’s just how startups work. We’ve managed startups like this forever; there is no other way to manage them.”

Download the podcast here

The Product Development Model

I realized that traditional ways to think about startups – have an idea, raise some money, do product development, go through an alpha test, beta test and first customer ship was the canonical model of how entrepreneurs thought about early stage ventures.

product-dev-diagram-b751

This product development diagram had become part of the DNA of Silicon Valley.  So much so that after I started teaching I’d ask, “Can anybody recognize this model of startups?”  And when everyone raised their hands I used to joke, “Even the waiters in San Francisco could draw this model.”  But in 2002 a student with a pained look on his face raised his hand and said, “Well, we’re now waiters in San Francisco because we used to be CEO’s of dot-com companies.”  So I no longer make that joke.

When I looked at the diagram in that ski cabin I realized there was a fundamental question I couldn’t answer: if all startups follow that model, why is it that some companies are opening bottles of champagne at their IPO and others who almost followed the same rules are selling off their furniture?  What was the difference here?  Were all startups the same? Were startups failing because of product failures or was there some other failure mode?  Is there any way to predict success or failure?  And even more importantly, was there any way to reduce risk in early stage ventures?

That day, alone in the cabin I knew I had to find the answer.

Download the podcast here

Retirement and Redemption

In 1999 I retired and began to reflect about my career and what had happened in the previous 21 years and eight startups in Silicon Valley.  Alone in a ski cabin with the snow coming down outside, and my wife and daughters out on the slopes all day, I started collecting my thoughts by writing a series of “lessons learned” stories that I had hoped would become my memoirs.

Eighty some pages later I realized that a) I had some great war stories as a good marketeer and failed CEO, b) I’d have to pay my wife and kids to read them, c) the three of them were probably the entire total available market, and d) when I looked at what I had done and what other entrepreneurs had done at their startups, that there was a pattern.

Download the podcast here