27,99 €
Mehr erfahren.
- Herausgeber: John Wiley & Sons
- Kategorie: Fachliteratur
- Sprache: Englisch
More than 100,000 entrepreneurs rely on this book.
The National Science Foundation pays hundreds of startup teams each year to follow the process outlined in the book, and it's taught at Stanford, Berkeley, Columbia and more than 100 other leading universities worldwide. Why?
The Startup Owner's Manual guides you, step-by-step, as you put the Customer Development process to work. This method was created by renowned Silicon Valley startup expert Steve Blank, co-creator with Eric Ries of the "Lean Startup" movement and tested and refined by him for more than a decade. This 608-page how-to guide includes over 100 charts, graphs, and diagrams, plus 77 valuable checklists that guide you as you drive your company toward profitability. It will help you:
Avoid the 9 deadly sins that destroy startups' chances for success
Use the Customer Development method to bring your business idea to life
Incorporate the Business Model Canvas as the organizing principle for startup hypotheses
Identify your customers and determine how to "get, keep and grow" customers profitably
Compute how you'll drive your startup to repeatable, scalable profits.
The Startup Owner�s Manual was originally published by K&S Ranch Publishing Inc. and is now available from Wiley. The cover, design, and content are the same as the prior release and should not be considered a new or updated product.
Das E-Book können Sie in Legimi-Apps oder einer beliebigen App lesen, die das folgende Format unterstützen:
Seitenzahl: 695
Veröffentlichungsjahr: 2020
Ähnliche
The Startup Owner’s Manual™
The Step-by-Step Guide for Building a Great Company
Steve Blank and Bob Dorf
Copyright © 2020 by Steve Blank. All rights reserved.
The cover, design, and content are the same as the prior release and should not be considered a new or updated product.
Published by John Wiley & Sons, Inc., Hoboken, New Jersey.
Published simultaneously in Canada.
The Startup Owner’s Manual was originally published by K&S Ranch Publishing Inc., K&S Ranch Publishing Division in 2012.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the Web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.
For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.
Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material included with standard print versions of this book may not be included in e-books or in print-on-demand. If this book refers to media such as a CD or DVD that is not included in the version you purchased, you may download this material at http://booksupport.wiley.com. For more information about Wiley products, visit www.wiley.com.
ISBN 9781119690689 (Hardcover)ISBN 9781119690672 (ePDF)ISBN 9781119690726 (ePub)
CONTENTS
Cover
How to Read This Book
Preface
Who Is This Book For?
Introduction
A Repeatable Path
Why a Second Decade?
The Four Steps: A New Path
I Getting Started
Chapter 1: The Path to Disaster: A Startup Is Not a Small Version of a Big Company
The Traditional New-Product Introduction Model
The 9 Deadly Sins of the New Product Introduction Model
Chapter 2: The Path to the Epiphany: The Customer Development Model
An Introduction to Customer Development
“The Search for a Business Model:” Steps, Iteration and Pivots
A Customer Development Bonus: Minimum Waste of Cash and Time
The Customer Development Manifesto
Summary: The Customer Development Process
Chapter 3: An Introduction to Customer Discovery
The Customer Discovery Philosophy
Chapter 4: Customer Discovery, Phase One: State Your Business Model Hypotheses
Market Size Hypothesis (Physical and Web/Mobile)
Value Proposition 1: “Low Fidelity” MVP Hypothesis (Web/Mobile)
Customer Segments: Who/Problem Hypothesis (Physical)
Customer Segments: Source/Wiring Hypothesis (Web/Mobile)
Channels Hypothesis (Physical)
Channels Hypothesis (Web/Mobile)
Value Proposition 2: Market-Type and Competitive Hypothesis
Customer Relationships Hypothesis (Web/Mobile)
Key Resources Hypothesis (Physical and Web/Mobile)
Partners Hypothesis (Physical)
Traffic Partners Hypothesis (Web/Mobile)
Revenue and Pricing Hypothesis
Chapter 5: Customer Discovery, Phase Two: “Get Out of the Building” to Test the Problem: “Do People Care?”
Design Tests and Pass/Fail Experiments
Prepare for Customer Contacts (Physical)
Build Your Low Fidelity MVP (Web/Mobile)
Test Understanding of the Problem and Assess Its Importance (Physical)
Avoid the Big-Company Meeting Trap
Low Fidelity MVP Problem Test (Web/Mobile)
Missteps to Avoid when Testing the Low Fidelity MVP:
Gain Customer Understanding
Capture Market Knowledge (Physical)
Traffic/Competitive Analysis (Web/Mobile)
Chapter 6: Customer Discovery, Phase Three: “Get Out of the Building” and Test the Product Solution
Update the Business Model and Team (a Pivot-or-Proceed Point)
Create the Product “Solution” Presentation (Physical)
High Fidelity MVP Test (Web/Mobile)
Test the Product Solution with the Customer (Physical)
Measure Customer Behavior (Web/Mobile)
Update the Business Model Again
Identify First Advisory Board Members
Chapter 7: Customer Discovery, Phase Four: Verify the Business Model and Pivot or Proceed
Have We Found a Product/Market Fit?
Do We Know Who Our Customers Are and How to Reach Them?
Can We Make Money and Grow the Company?
Pivot or Proceed?
Chapter 8: Introduction to Customer Validation
An Epiphany at E.piphany
The Customer Validation Philosophy
Overview of the Customer Validation Process
Chapter 9: Customer Validation, Phase One: "Get Ready to Sell"
Get Ready to Sell: Craft Positioning Statement
Get Ready to Sell: Sales and Marketing Materials (Physical)
Physical Sales Collateral and Materials
Collateral Needs to Be Tuned to the Audience
Online Tools for Physical Channel Marketers
Get Ready to Sell: Acquire/Activate Customers Plan (Web/Mobile)
The “Acquire” Plan and Tools
Acquire Plan Tools
The Activation Plan and Tools
Non-home page acquisition tools
Managing the Activate Plan
Get Ready to Sell: Hire a Sales Closer (Physical)
Get Ready to Sell: Build a High Fidelity MVP (Web/Mobile)
Get Ready to Sell: Sales Channel Roadmap (Physical)
Get Ready to Sell: Build a Metrics Toolset (Web/Mobile)
Get Ready to Sell: Develop the Sales Roadmap (Physical)
Get Ready to Sell: Hire a Data Analytics Chief (Web/Mobile)
Get Ready to Sell: Formalize the Advisory Board (All Channels)
Chapter 10: Customer Validation, Phase Two: Get Out of the Building and Sell!
Get Out of the Building: Find Earlyvangelists (Physical)
Get Out of the Building: Prepare Optimization Plans/Tools (Web/Mobile)
Get Out of the Building and Test Sell (Physical)
Get Out of the Building: Optimize Getting More Customers (Web/Mobile)
Get Out of the Building: Refine the Sales Roadmap (Physical)
Get Out of the Building: Optimize “Keep” and “Grow” (Web/Mobile)
Get Out of the Building: Test Sell Channel Partners (Physical)
Get Out of the Building: Test Sell Traffic Partners (Web/Mobile)
Chapter 11: Customer Validation, Phase Three: Product Developing and Company Positioning
No PR Agency
The Positioning Audit
Develop Positioning: Product Positioning
The Product Positioning Brief
Develop Positioning: Match Positioning to Market Type
For an Existing Market
For a New Market
For a Clone Market
For Re-Segmenting a Market
Develop Positioning: Company Positioning
Develop Positioning: Validate Positioning
Chapter 12: Customer Validation, Phase Four: The Toughest Question of All:
Pivot or Proceed?
Pivot or Proceed: Assemble Data Findings
Pivot or Proceed: Validate Your Business Model
Pivot or Proceed: Validate the Financial Model
Metrics that Matter
Metrics that Matter: Example 2
If These Were Your Numbers, What’s a Founder to Do?
Metrics that Matter: Example 3
Pivot or Proceed:
Re
-Validate the Business Model
The Toughest Startup Question: Pivot or Proceed?
The Startup Owner’s Manual “Site” Map
Appendix A: Checklists
Appendix B: Glossary
Appendix C: How to Build a Web Startup: A Simple Overview
Acknowledgements
About the Authors
Index
End User License Agreement
List of Tables
Chapter 4
Table 4.1
Table 4.2
Table 4.3
Table 4.3a
Table 4.3b
Table 4.3c
Table 4.4
Table 4.4a
Table 4.4b
Table 4.4c
Table 4.5
Chapter 4
Table 9.1
Table 9.2
Table 9.3
Table 9.4
Table 9.5
Chapter 10
Table 10.1
Table 10.2
Chapter 11
Table 11.2
Table 11.2
Chapter 12
Table 12.1
Table 12.2
Table 12.3
List of Illustrations
Who Is This Book For?
Figure i.0 Scalable Startup
Introduction
Figure i.1 Physical Products Sold Through a Physical Channel
Figure i.2 Software Products Sold Through Physical Channels
Figure i.3 Physical Products in Web/Mobile Channels
Figure i.4 Software Products In Web/Mobile Channels
Chapter 1
Figure 1.1 New Product Introduction Diagram
Figure 1.2 The Product Development “Waterfall” Model
Chapter 2
Figure 2.1 Customer Development Process
Figure 2.2 Business Model Canvas
Figure 2.3 The Customer Development Insight Cycle
Chapter 3
Figure 3.1 Earlyvangelist Characteristics
Figure 3.2 Developing the Minimum Viable Product for a Web/Mobile Product
Figure 3.3 Business Model Canvas
Figure 3.4 Sample Business Model Canvas-Initial Hypotheses
Figure 3.5 Using the Business Model Canvas as a Weekly Scorecard
Figure 3.6 Customer Discovery: Overview of the Process
Chapter 4
Figure 4.1 TAM, SAM and Target Market
Figure 4.2 Customer Types
Figure 4.3 Customer Archetype
Figure 4.4 A Sample Organizational/Influence Map
Figure 4.5 A Guide to Using Customer/Archetypes to Drive Strategy
Figure 4.6 A Guide to Using A Day-in-the-Life to Drive Strategy
Figure 4.7 Consumer Web Influence Map
Figure 4.8 Physical Distribution Channel Choices
Figure 4.9 Web/Mobile Distribution Channel Choices
Figure 4.10 Example of a Market Map
Figure 4.11 The “Get, Keep, Grow” Funnel in Physical Channels
Figure 4.12 The “Get Customers” Funnel for Physical Goods
Figure 4.13 Earned and Paid Media Feeding the “Get Customers” Funnel
Figure 4.14 Sample Customer Relationship “Tactics to Test” Hypothesis with Return on Invest...
Figure 4.15 The “Keep Customers” Funnel
Figure 4.16 The “Grow Customers” Funnel
Figure 4.17 The “Get, Keep and Grow” Customers Funnel in Web/Mobile
Figure 4.18 The “Get Customers” Funnel in Web/Mobile Channels
Figure 4.19 Acquisition and Activation in Web/Mobile Channels
Figure 4.20 The “Keep Customers” Funnel in Web/Mobile Channels
Figure 4.21 The “Grow Customers” Funnel in Web/Mobile Channels
Figure 4.22 Revenue Sources
Figure 4.23 Final Draft of a Business Model Hypothesis
Chapter 5
Figure 5.1 Business Model/Hypotheses/Tests
Figure 5.2 Hypothesis/Design Experiment/Test/Insight
Figure 5.3 Global Maximum versus Local Maximum Response Rates
Figure 5.4 Customer Problem Presentation
Figure 5.5 Sample Customer Discovery Scorecard
Figure 5.6 Understanding Customer Interactions
Chapter 6
Figure 6.1 Sample Customer Discovery Report Card
Chapter 7
Figure 7.1 Is This Business Worth Doing?
Figure 7.2 Sample Financial Analysis
Chapter 8
Figure 8.1 Customer Validation: Overview of the Process
Chapter 9
Figure 9.1 Phase 1 – Get Ready to Sell
Figure 9.2 Product Positioning Statement
Figure 9.3 Product Positioning Statement Example
Figure 9.4 The “Get Customers” Funnel in Physical Channels
Figure 9.5 The “Get Customers” Funnel in Web/Mobile Channels
Figure 9.6 A Sample Acquire Plan and Timetable
Figure 9.7 The “Get Customers” Activation Activities in Web/Mobile Channels
Figure 9.8 The landing page is where activation most often begins.
Figure 9.9 Example of a Simple Activation Funnel
Figure 9.10 Direct e-book Publishing Food Chain
Figure 9.11 Book Publishing Physical Channel Food Chain
Figure 9.12 Channel Responsibility Map
Figure 9.13 Channel Discounts
Figure 9.14 Channel Financial Relationships
Figure 9.15 Channel Diagram for a Complex Multi-Sided Market
Figure 9.16 Metrics to Measure, in the “Get Customers” Funnel Web/Mobile Channels
Figure 9.16b “Grow Customer” Referrals happen through “Viral loops.”
Figure 9.17 Example of a Simple Dashboard
Figure 9.18 Support/Approval Matrix
Figure 9.19 Example of an Influence Map
Figure 9.20 Example of an Access Map
Chapter 10
Figure 10.1 Steps for “Get Out of the Building and Sell” by Channel
Figure 10.2 The “Get Customers” Funnel in Physical Channels
Figure 10.3 Sample A/B Tests Compare Changing Home Page Results
Figure 10.4 Usability Tests happen in Starbucks or test facilities
Figure 10.5 Example of Heat Mapping
Figure 10.6 Example of Eye Tracking
Figure 10.7 The “Get Customers” Funnel in Web/Mobile Channels
Figure 10.8 Typical Influence Map in a Company Organized by Function
Figure 10.9 Core Strategy
Figure 10.10 Example of an Access Strategy Map
Figure 10.11 Example of a Sales Roadmap
Figure 10.12 The “Keep Customers” Funnel in Web/Mobile Channels
Figure 10.13 Cohort Analysis of a Sales Funnel
Figure 10.14 “Grow Customers” Activation Activities in Web/Mobile Channels
Chapter 11
Figure 11.1 Example of an External Audit Questionnaire
Figure 11.1 Example of Product Positioning
Chapter 12
Figure 12.1 Review Business Model Hypotheses
Figure 12.2 Business Model Checklist
Figure 12.3 Revenue Growth in New and Existing Markets
Figure 12.4 Revenue Growth in a Resegmented Market
Guide
Cover
Table of Contents
Chapter
Pages
iii
iv
vii
viii
ix
x
xi
xii
xiii
xiv
xv
xvi
xvii
xviii
xix
xx
xxi
xxii
xxiii
xxiv
xxv
xxvi
xxvii
xxviii
xxix
xxxi
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
549
550
551
552
553
554
555
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
573
574
How to Read This Book
CLEARLY, THE STARTUP OWNER’S MANUAL IS not a novel. This book is a step-by-step how-to guide that details a process for building a successful, profitable, scalable startup. It has more in common with a car repair manual than it does with your favorite page-turner. Don’t attempt to read this book in a single sitting or long weekend. It will be your companion—and, we hope, your very best friend—for the six to 30 months or more that it often takes to begin building a successful, scalable startup business.
Organization
This book is organized in four distinct sections. The first, Getting Started, describes the Customer Development methodology and ends with the “Customer Development Manifesto,” a series of 14 guiding principles for startups deploying the Customer Development process.
Don’t read too much at a time.
The next section, Step One, “Customer Discovery," turns the founders’ vision into a business model canvas and then into a series of hypotheses. Those hypotheses are turned into experiments, and tested with customers to see if your understanding of the customer problem and proposed solution mesh.
Step Two, “Customer Validation," expands the scope of the business model testing to see if you can get enough orders or users to prove that you have a repeatable and scalable business model.
The fourth key section, found in Appendix A, is a series of Checklists that help you track your progress at every stage of the Customer Development process. Use the checklists at the end of each step (yes, there’s one for each) to make sure you have completed all the key tasks outlined in that step. Photocopy them, scan them, and circulate them to team members. But most important, use them to be sure you have completed each step—before you move on to the next.
Web/Mobile vs. Physical Channels
This book recognizes that Customer Development operates at different speeds for web/mobile startups versus products sold through physical distribution channels. The process to “Get/Keep/Grow” customers—the core job of any business—is different, and web products are built and obtain feedback faster. Recognizing this, we offer parallel tracks through the book: one focused on physical goods and channels, and one focused on web/mobile products and channels. Often, the book addresses them separately. When it does, we begin with the physical channel, then follow with web/mobile.
In each phase of customer discovery and validation, you’ll see diagrams like this to help you understand where you are in the process:
The upper row indicates the recommended steps for physical channel startups. The lower row depicts steps for web/mobile startups. When the steps are nearly identical, the boxes merge.
When we’re discussing web and mobile channels, products, strategies or tactics, you’ll see theat the start of those discussions, always in this typeface, alongside the text that shows you’ve “changed channels.”
It’s worth reading both versions of a step before turning to the one explaining “your” business type. When information in one channel is essential for startups in the other, we’ll tell you so—and tell you what to read. Web/mobile startup founders should skim the physical section before they read and begin implementing the web/mobile processes in each section.
Paths Through This Book
Read the glossary in the back of the book first.
Customer Development has a language all its own.
Before you dive into the details,
read the Customer Development Manifesto
on page 31-49.
If you are familiar with Customer Development
, skim Chapters 1-3, then start with Chapter 4, “the business model hypotheses.”
If you want to
align co-founders, initial employees, investors and advisors around the Customer Development philosophy
, have them read Chapters 1 and 2.
If you want a high-speed overview and little more
, there are two approaches:
skim the checklists at the back of the book, which will give you a sense of all the tasks you must complete to implement Customer Development; or
flip through the book, looking for “jumbo quotes” like this:
This book is not a novel… It’s a reference manual.
These quotes highlight the 100 or so “big ideas” found throughout the book and offer a “CliffsNotes” or “Twitter” sense of the nearly 600 pages of text.
If you want a detailed checklist of the things founders need to get right
, start with Chapter 4, “the business model hypothesis,” and use the checklists in Appendix A page 469.
If your startup is well under way
, you might want to start at Chapter 7, “Pivot or Proceed,” to gauge your progress. Then you can jump to Chapter 12, “Metrics that Matter,” to see if you’re ready to scale.
To
develop and test a web/mobile minimum viable product
(MVP), read: Design Tests (page 191), Build Your Low Fidelity MVP (page 200), Low Fidelity MVP Problem Test (page 211), and Optimize Getting More Customers (page 380).
To
develop and test a physical minimum viable product
(MVP), read: Customer Contacts (page 195), Problem Understanding (page 203), Customer Understanding (page 218), and The Sales Roadmap (page 344).
To focus on
web/mobile marketing
(how to “get,” “keep” and “grow” customers), read:
Hypotheses: Customer Source/Wiring (page 93), Channels (page 104), and Customer Relationships (page 144).
Build Your Low Fidelity MVP (page 200), Low Fidelity MVP Problem Test (page 211), Traffic/Competitive Analysis (page 225), High Fidelity MVP Test (page 237), and Measure Customer Behavior (page 245).
Get Ready to Sell: Craft Positioning Statement (page 293), Acquire/Activate Customers Plan (page 304), Create a High Fidelity MVP (page 330), Build a Metrics Tool Set (page 338), and Hire a Data Analytics Chief (page 350).
Get Out of the Building: Prepare Optimization Plans/Tools (page 362), Optimize Getting More Customers (page 380), Optimize “Keep” and “Grow” (page 396), Test Sell Traffic Partners (page 409).
To focus on
physical channel sales and marketing
(how to “get”, “keep” and “grow” customers), read:
Hypotheses: Customer Segments Who/Problem (page 85), Channels (page 98), Customer Relationships (page 144), and Revenue Stream Pricing (page 180).
Prepare for Customer Contacts (page 195), Problem Understanding (page 203), Market Knowledge (page 222), Create Product Presentation (page 235), and Test Solution with Customer (page 239).
Get Out of the Building: Create Sales and Collateral Materials (page 296), Hire Sales Closer (page 329), Sales Channel Roadmap (page 332), and Develop the Sales Roadmap (page 344).
Educators who want to
teach Customer Development
or the experiential
Lean LaunchPad
class should read:
Our website,
www.steveblank.com
, with links to our syllabi used at Stanford, Berkeley and the National Science Foundation.
Before the class meets, have the students read:
—
The Customer Development Manifesto
in Chapter 2
—
An Introduction to Customer Development
in Chapter 2
Each week’s lectures are organized around each of the individual hypotheses in Phase 1, pages 69-188.
For the
Lean LaunchPad
class, have students read:
—Get Out of the Building and Test the Problem in Chapter 5, pages 189-226.
—Get Out of the Building and Test the Product Solution in Chapter 6, pages 227-256.
All classes should read:
—Pivot or Proceed, in Chapter 7, pages 270-273.
—Metrics that Matter, in Chapter 12, pages 438-459.
A Few Helpful Tips
We see a direct correlation between the entrepreneurs’ success and the degree to which their copy is dog-eared, beat up and tattered. USE the book, don’t just read it!
We see a direct correlation between the entrepreneurs’ success and the degree to which their copy is dog-eared, beat up and tattered.
Use the checklists. There are more than 40 at the back of the book—one for every step.
Don’t read too much at a time. This is a reference manual. It’s exhausting when read as a book. Take “small bites” of a few sections at a time, at most. Dog-ear it and use Post-it notes to mark your place, and keep the book close at hand so you can refer to it often.
Scan ahead. It gives you context for what you are currently doing. If you’re starting work on Chapter 4, for example, quickly scan Chapter 5 first so you understand how what you’re doing now supports what comes next.
For a helpful online tool to monitor your team’s progress in the Customer Development process, visit
http://www.zoomstra.com/foundersworkbook/
Entrepreneurship is not a cookbook or a checklist. At the end of the day, founders are artists. Don’t expect everything to work like the book. It’s impossible for this book to address every entrepreneurial decision and every type of startup. You’re outside the building not only looking for facts, but for insight and inspiration. Not every piece of advice fits every situation you’ll encounter. And not every piece of advice will always work. That’s what entrepreneurs are for.
Preface
IN 1602, THE DUTCH EAST INDIA COMPANY, generally regarded as the first “modern company,” issued the first stock certificates. In the intervening 300 years, companies managed to start, build and grow without formally trained executives. By the 20th century, the complexity of modern corporations demanded a cadre of executives trained to administer large companies. In 1908, Harvard awarded the first master of business administration (MBA) degree to fill the need to bring professional education standards to big business. The MBA curriculum standardized and codified the essential elements an operating executive in a modern company needed to know: cost accounting, strategy, finance, product management, engineering, personnel management and operations.
Formal management tools are about 100 years old.
Fast-forward to the mid-20th century. The pairing of venture capital and startup entrepreneurship emerged in its modern form, and the startup industry they fostered has been exploding ever since. Yet for the past 50 years, finding the successful formula for repeatable startup success has remained a black art. Founders have continually struggled with and adapted the “big business” tools, rules and processes taught in business schools and suggested by their investors. Investors have been shocked when startups failed to execute “the plan,” never admitting to the entrepreneurs that no startup executes to its business plan. Today, after half a century of practice, we know unequivocally that the traditional MBA curriculum for running large companies like IBM, GM and Boeing does not work in startups. In fact, it’s toxic.
With the benefit of hindsight, entrepreneurs now understand the problem, namely that startups are not simply smaller versions of large companies. Companies execute business models where customers, their problems, and necessary product features are all “knowns.” In sharp contrast, startups operate in “search” mode, seeking a repeatable and profitable business model. The search for a business model requires dramatically different rules, roadmaps, skill sets, and tools in order to minimize risk and optimize chances for success.
By the beginning of the 21st century, entrepreneurs, led by web and mobile startups, began to seek and develop their own management tools. Now, a decade later, a radically different set of startup tools has emerged, distinct from those used in large companies but as comprehensive as the traditional “MBA Handbook.” The result is the emerging “science of entrepreneurial management.” My first book, The Four Steps to the Epiphany, was one of its first texts. It recognized that the classic books about large-company management were ill-suited for early-stage ventures. It offered a reexamination of the existing product-introduction process and delineated a radically different method that brings customers and their needs headfirst into the process long before the launch.
We are building the first management tools specifically for startups.
At the time I wrote it, the book was my proposed methodology for getting startups right. But just as it was published, agile engineering became the preferred product-development method. This iterative and incremental method created a need and a demand for a parallel process to provide rapid and continual customer feedback. The Customer Development process I articulated in The Four Steps fit that need perfectly.
Over the past decade, thousands of scientists, engineers and MBAs in my classes at Stanford’s engineering school and U.C. Berkeley’s Haas School of Business—plus those sponsored by the National Science Foundation—have discussed, deployed, assessed and enhanced the Customer Development process. It has since been implemented by tens of thousands of entrepreneurs, engineers, and investors worldwide.
While the fundamental, powerful “Four Steps” remain at its core, this book is far more than a second edition. Nearly every step in the process, and in fact the entire approach, have been enhanced and refined based on a decade of Customer Development experience.
Customer development is paired with agile product development.
Even more gratifying: now, a decade later, multiple books and authors, are filling shelves in the newly created section for the strategy and science of entrepreneurship. Some of the other areas in this emerging field of entrepreneurial management are:
agile development, an incremental and interactive approach to engineering that enables product or service development to iterate and pivot to customer and market feedback
business model design, which replaces static business plans with a nine-box map of the key elements that make up a company
creativity and innovation tools for creating and fostering winning ideas
the Lean Startup, an intersection of customer and agile development
lean user interface design to improve web/mobile interfaces and conversion rates
venture and entrepreneurial finance, to attract and manage funds that fuel the innovation
No one book, including this one, offers a complete roadmap or all the answers for entrepreneurs. Yet together, the texts in the entrepreneurial management science library offer entrepreneurs guidance where none existed before. Startups, driven by potential markets measured in billions of people, will use this body of knowledge to test, refine and scale their ideas far faster and more affordably than ever.
No one book, including this one, offers a complete roadmap…
My co-author Bob and I hope books like this one help speed the startup revolution and enhance its success—and yours.
Steve Blank
Pescadero, Calif., March 2012
Who Is This Book For?
THIS BOOK IS FOR ALL ENTREPRENEURS and uses the term startup literally hundreds of times. But what exactly is a startup? A startup is not a smaller version of a large company. A startup is a temporary organization in search of a scalable, repeatable, profitable business model. At the outset, the startup business model is a canvas covered with ideas and guesses, but it has no customers and minimal customer knowledge.
But we’ve only defined the words startup, entrepreneur, and innovation halfway. These words mean different things in Silicon Valley, on Main Street, and in Corporate America. While each type of startup is distinct, this book offers guidance for each one.
A startup is a temporary organization in search of a scalable, repeatable, profitable business model.
Small Business Entrepreneurship: In the United States, the majority of entrepreneurs and startups are found among 5.9 million small businesses that make up 99.7 percent of all U.S. companies and employ 50 percent of all nongovernment workers. These are often service-oriented businesses like drycleaners, gas stations and convenience stores, where entrepreneurs define success as paying the owners well and making a profit, and they seldom aspire to take over an industry or build a $100 million business.
Scalable startups are the work of traditional technology entrepreneurs. These entrepreneurs start a company believing their vision will change the world and result in a company with hundreds of millions if not billions of dollars in sales. The early days of a scalable startup are about the search for a repeatable and scalable business model. Scale requires external venture-capital investment in the tens of millions to fuel rapid expansion. Scalable startups tend to cluster in technology centers such as Silicon Valley, Shanghai, New York, Bangalore, and Israel and make up a small percentage of entrepreneurs, but their outsize return potential attracts almost all the risk capital (and press).
Figure i.0 Scalable Startup
“Buyable” startups are a new phenomenon. With the extremely low cost of developing web/mobile apps, startups can literally fund themselves on founders’ credit cards and raise small amounts of risk capital, usually less than $1 million. These startups (and their investors) are happy to be acquired for $5 million to $50 million, purchased by larger companies often to acquire the talent as much as the business itself.
Large Company Entrepreneurship: Large companies have finite life cycles. Most grow by offering new products that are variants of their core products (an approach known as sustaining innovation). They may also turn to disruptive innovation, attempting to introduce new products into new markets with new customers. Ironically, large companies’ size and culture make disruptive innovation (really an effort to launch a scalable startup inside a big company) extremely difficult to execute.
…large companies’ size and culture make disruptive innovation extremely difficult.
Social entrepreneurs build innovative nonprofits to change the world. Customer Development provides them a scorecard for assessing scalability, asset leverage, return on investment and growth metrics. These entrepreneurial ventures seek solutions rather than profits and happen on every continent in areas as diverse as water, agriculture, health, and microfinance.
While the Customer Development process helps scalable startups the most, each of these five startup types has entrepreneurship and innovation at its heart. And each improves its chances for finding the right path to success through the use of Customer Development.
Who Is This Book Not For?
There are cases where using the Customer Development methodology and this book is inappropriate.
Early-stage ventures fall into two types: those with customer/market risk and those with invention risk.
Markets with invention risk are those where it’s questionable whether the technology can ever be made to work, but if it does, customers will beat a path to the company’s door. (Think life sciences and cure for cancer.)
Markets with customer/market risk are those where the unknown is whether customers will adopt the product.
For companies building web-based products, product development may be difficult, but with enough time and iteration, Engineering will eventually converge on a solution and ship a functional product—it’s engineering, not invention. The real risk is in whether there is a customer and a market for the product as spec’ed. In these markets it’s all about customer/market risk.
There’s a whole other set of markets where the risk is truly invention. These are markets where it may take five or even 10 years to get a product out of the lab and into production (e.g., biotech). Whether it will eventually work, no one knows, but the payoff can be so large that investors will take the risk. In these markets it’s all about invention risk.
Startups solve customer and market risk by reading this book.
A third type of market has both invention and market risk. For example, complex new semiconductor architectures mean you may not know if the chip performs as well as you thought until you get first silicon. But then, because there might be entrenched competitors and your concept is radically new, you still need to invest in the Customer Development process to learn how to get design wins from companies that may be happy with their existing vendors.
Startups solve invention risk by using simulation tools (computational fluid dynamics, finite element analysis, etc.). Startups solve customer and market risk by reading this book. When the issues are customer acceptance and market adoption, this book shows the path.
Introduction
A legendary hero is usually the founder of something—the founder
of a new age, the founder of a new religion, the founder of a new city,
the founder of a new way of life. In order to found something new,
one has to leave the old and go on a quest of the seed idea, a germinal
idea that will have the potential of bringing forth that new thing.
— Joseph Campbell, The Hero with a Thousand Faces
JOSEPH CAMPBELL POPULARIZED THE NOTION of an archetypal “hero’s journey,” a pattern that recurs in the mythologies and religions of cultures around the world. From Moses and the burning bush to Luke Skywalker’s meeting Obi-wan Kenobi, the journey always begins with a hero who hears a calling to a quest. At the outset of the voyage, the path is unclear and no end is in sight. Each hero meets a unique set of obstacles, but Campbell’s keen insight was that the outline of these stories is always the same. There are not a thousand different heroes but one hero with a thousand faces.
The hero’s journey is an apt way to think of startups. All new companies and new products begin with a vision—a hope for what could be and a goal few others can see. It’s this bright and burning founder’s vision that differentiates an entrepreneur from a big-company CEO and separates startups from existing businesses.
Founding entrepreneurs are out to make their vision and business real. To succeed, they must abandon the status quo, recruit a team that shares their vision, and strike out together on what appears to be a new path, often shrouded in uncertainty, fear and doubt. Obstacles, hardships and potential disaster lie ahead, and their journey to success tests more than financial resources—it tests their stamina, agility, and courage.
Take a new path, often shrouded in uncertainty, fear, and doubt.
Every entrepreneur is certain his or her journey is unique. Each travels down the startup path without a roadmap and believes that no model or template could possibly apply. What makes some startups successful while others sell off the furniture often seems like luck. But it isn’t. As Campbell suggests, the outline is always the same. The path to startup success is well-traveled and well-understood. There is a true and repeatable path to success. This book charts that path.
A Repeatable Path
In the last quarter of the 20th century, startups thought they knew the correct path for the startup journey. They adopted a methodology for product development, launch, and life-cycle management almost identical to the processes taught in business schools for use in large companies. These processes provide detailed business plans, checkpoints and goals for every step toward getting a product out the door—sizing markets, estimating sales, developing marketing-requirements documents, prioritizing product features. Yet at the end of the day, even with all these processes, the embarrassing fact is that in companies large and small, established corporate giants as well as new startups, more than nine of 10 new products fail. It’s true in every product category—high-tech or low, online or off, consumer or business—well-funded or not.
Even after decades of similar failures, investors are always surprised when a new venture fails to execute its business “plan.” And still they continue to rely on the same product-introduction processes.
We now know what the problem is. Startups have been using tools appropriate for executing a known business. But startups are all about unknowns. To find the path to build a winning startup, entrepreneurs must try a new way:
Winners throw out the traditional product management and introduction processes they learned at existing companies. Instead, they combine agile engineering and Customer Development to iteratively build, test and search for a business model, turning unknowns into knowns.
Winners also recognize their startup “vision” as a series of untested hypotheses in need of “customer proof.” They relentlessly test for insights, and they course correct in days or weeks, not months or years, to preserve cash and eliminate time wasted on building features and products that customers don’t want.
Winners recognize their startup is a series of untested hypotheses.
Losers blindly execute a rigid product management and introduction methodology. They assume that the founder’s vision drives the business strategy and product development plans and that all they need to do is to raise funds for execution.
Founders, not employees, must search for a business model. The best way to search is for the founders themselves to get out of the building to gain a deep, personal, firsthand understanding of their potential customers’ needs before locking into a specific path and precise product specs. That’s the difference between winners and losers. It’s also the Customer Development process detailed in this book.
Why a Second Decade?
Startups have now been using Customer Development for a decade, since the initial publication of The Four Steps to the Epiphany. If this is your first contact with the Four Steps, welcome aboard. For the tens of thousands who’ve embraced that first version, The Startup Owner’s Manual offers a great deal more. The first version assumed startups were high-tech ventures in Silicon Valley selling products through a physical sales channel and aiming to be billion-dollar businesses. A lot has happened in 10 years, and this version embraces those changes. For example:
Bits: The Second Industrial Revolution
For thousands of years after the invention of the wheel, a product was a physical object one could touch, such as food, cars, planes, books, and household goods. These physical products reached customers via a physical sales channel: salespeople visiting customers, or customers visiting stores. Figure i.1 shows this intersection of physical products sold through a physical channel.
Figure i.1 Physical Products Sold Through a Physical Channel
One of the breakthroughs in commerce was the invention of products that were ideas or promises that didn’t exist in physical form, such as life and health insurance, stocks and bonds, and commodity futures.
In the 1970s, software began to be sold as a product unbundled from any particular computer. The ability to purchase bits was a new concept. By themselves the bits were useless, but when combined with a computer in the form of software applications, bits solved problems or amused people (word processing, balancing checkbooks, game play). These software applications and entertainment, all in the form of bits, were sold to consumers through specialized retail computer stores, a physical channel.
Figure i.2 Software Products Sold Through Physical Channels
Still other software applications were designed to solve problems companies had (database access, manufacturing automation, sales automation), and added the upper right box to Figure i.2, Software Products Sold Through Physical Channels.
As the Internet created a new form of sales channel, a new class of company emerged with the value proposition to sell physical products over the Internet. Amazon, Zappos, Dell, and a whole raft of other e-commerce companies filled a new niche: physical products sold via a web channel. This new sales channel created massive disruption in the existing world of physical distribution, as book and music retailers perhaps know best of all.
Figure i.3 Physical Products in Web/Mobile Channels
Over the past decade a new class of product has emerged, where BOTH the product and the channel are bits (see Figure i.4). Startups can now be built for thousands rather than millions of dollars and in weeks rather than years. As a result, the number of startups founded each year has exploded. New applications such as social networks that duplicate the socialization we once had face-to-face are being mediated via machine. Search engines that scour the web, such as Google and Bing, exist only in bits, in a web/mobile channel.
More important, entire industries that started by selling physical products in physical locations have begun their migration to bits sold over the Internet. Originally, people sold books, music, videos, movies, travel, and stocks and bonds either face-to-face or in storefronts. Those channels are either radically transformed or disappearing as physical products turn into bits.
Figure i.4 Software Products In Web/Mobile Channels
Speed, Time and Iterations: the “Second Industrial Revolution”
Regardless of the business, any enterprise focused on the bottom righthand box in figure i.1—Physical Goods Sold through a Physical Channel—has discovered over the past decade that the old rules and tools for physical businesses and channels no longer apply. They’ve learned that the closer a company gets to a web/mobile channel and a web/mobile product, the faster it can change, test and optimize both product and offer. They need a new process to quickly adapt to the new freedoms a web/mobile channel and product allow, and they’ve found it in Customer Development.
The Customer Development process gathers customer feedback about product, channel, price, and positioning, all of which can be modified and tested in near-real time, and uses it as immediate feedback to iterate and optimize. As a result, web/mobile channel startups can move forward at “Internet speed,” an impossibility with physical distribution channels and products.
A mere decade ago, getting feedback on the features of a video game required recruiting focus groups to come in and play the game while being observed through one-way mirrors. Today, companies like Zynga test and tune the features of their online games in days. Are sales slow because the game is too hard? You can adjust the scoring or other game variables and change the product itself quicker than you can say touchdown.
Customer Development is the process to organize the search for the business model.
Theoretically, when startups’ products and channels are bits, they can gather and act on information 100 times faster than companies delivering physical goods via physical sales channels (10 times the number of iterative learning cycles, each using only 10 percent of the cash.) In fact, companies like Facebook, Google, Groupon, and Zynga grew faster in a decade than most industrial corporations grew in the 20thcentury. That’s why we call it the Second Industrial Revolution.
The Four Steps: A New Path
The core of Customer Development is blissfully simple: Products developed by founders who get out in front of customers early and often, win. Products handed off to sales and marketing organizations that are only tangentially involved in the new-product development process will lose. There are no facts inside your building, so get the heck outside. Getting out of the building means acquiring a deep understanding of customer needs and combining that knowledge with incremental and iterative product development. The mix of Customer Development and Agile engineering dramatically increases the odds of new product and company success, while reducing the need for upfront cash and eliminating wasted time, energy, money and effort.
There are no facts inside your building, so get the heck outside.
Customer Development recognizes the startup’s mission as a relentless search to refine its vision and idea, and to make changes in every aspect of the business invalidated during the search process. An entrepreneur seeks to test a series of unproven hypotheses (guesses) about a startup’s business model: who the customers are, what the product features should be, and how this scales into a hugely successful company. Customer Development recognizes a startup is a temporary organization built to search for the answers to what makes a repeatable and scalable business model. Customer Development is the process to organize that search.
IGetting Started
Chapter 1:
The Path to Disaster:
A Startup Is Not a Small Version of a Big Company
Chapter 2:
The Path to the Epiphany:
The Customer Development Model
The Customer Development Manifesto
CHAPTER 1The Path to Disaster: A Startup Is Not a Small Version of a Big Company
The definition of insanity is doing the same thing over and over and expecting different results.
—Albert Einstein
WHILE THIS STORY IS OLD, ITS LESSONS are timeless. In the heyday of the dot-com bubble at the end of the 20th century, Webvan stood out as one of the most electrifying new startups, with an idea that would potentially touch every household in America. Raising one of the largest financial war chests ever seen (more than $800 million), the company aimed to revolutionize the $450 billion retail grocery business with online ordering and same-day door-to-door grocery delivery. Webvan believed this was one of the first “killer applications” for the Internet. Customers could just point, click, and order. Webvan’s CEO told Forbes magazine that Webvan would “set the rules for the largest consumer sector in the economy.”
Beyond amassing megabucks, the Webvan entrepreneurs seemed to do everything right. Backed by experienced venture-capital investors, the company raced to build vast automated warehouses and bought fleets of delivery trucks while building an easy-to-use website. Webvan hired a seasoned CEO from the consulting industry. What’s more, most initial customers actually liked the service. But barely 24 months after the initial public offering, Webvan was bankrupt and out of business. What happened?
…barely 24 months after the initial public offering, Webvan was bankrupt.
This was not a failure of execution. Webvan did everything its board and investors asked. In particular, the company fervently followed the traditional new-product introduction model commonly used by most new ventures and embraced the mantras of the time: “first mover advantage” and “get big fast.” Webvan’s failure to ask “where are the customers?” illuminates how this tried-and-true model led one of the best-funded startups of all time down the path to disaster.
The Traditional New-Product Introduction Model
In the 20th century, every company bringing a new product to market used some form of product management model (Figure 1.1). Emerging early in the century, this product-centric model described a process that evolved in manufacturing industries. The consumer packaged-goods industry adopted it in the 1950s, and it spread to the technology business in the last quarter of the century. There it became an integral part of the startup culture.
Figure 1.1 New Product Introduction Diagram
At first glance, the new-product introduction model outlined in the diagram at right appears to be helpful and benign. It illustrates the process of getting a new product into the hands of waiting customers. A new product moves from development to customer testing (alpha/beta test), and using feedback from this initial testing, the product engineers fix technical errors in the product until the product launch date and first customer ship.
The new-product introduction model is a good fit for an existing company where the customers are known, the product features can be spec’ed upfront, the market is well-defined, and the basis of competition is understood.
As for startups, a scant few fit these criteria. Few even know who their customers are. Yet many persist in using the new-product introduction model not only to manage product development but as a roadmap for finding customers and setting the timing for the startup’s sales, launch and revenue plans. Investors use the new-product introduction diagram to set and plan funding. All parties involved in the startup use a roadmap leading toward a very different location, yet they’re surprised to end up lost.
What’s wrong with the old model, and how did it contribute to the billion-dollar Webvan implosion?
Concept and Seed Stage
At the concept and seed stage, founders capture their passion and vision for the company, sometimes on the back of a napkin, and turn them into a set of key ideas, which becomes the outline for the business plan.
Next, issues surrounding the product are defined. What is the product or service concept? What are the product features and benefits? Can it be built? Is further technical research needed? Who will the customers be, and where will they be found? Statistical and market research and a few customer interviews fuel the evaluation and business plan.
This step also brings forth a first guess at how the product will ultimately reach the customer, including discussions of competitive differences, distribution channels, and costs. An initial positioning chart explains the company and its benefits to venture capitalists or corporate higher-ups. The business plan now gets market-size, competitive and financial sections, with an appendix containing Excel spreadsheets forecasting revenue and expenses. Creative writing, passion and shoe leather combine in the concept and seed phase in hopes of convincing an investor to fund the company or the new division.
Once a waterfall process starts, the proverbial train has left the station…
Webvan did all of this extremely well. Founded in December 1996, with a compelling story and a founder with a track record, Webvan raised $10 million from leading Silicon Valley venture capitalists in 1997. In the next two years, additional private rounds totaling an unbelievable $393 million followed before the company’s IPO.
Product Development
In stage two, product development, everyone stops talking and starts working. The respective departments go to their figurative corners as the company begins to specialize by function. Marketing refines the size of the market defined in the business plan and begins to target the first customers. In a well-organized startup (one with a fondness for process), the marketing folk might even run a focus group or two on the market they think they’re in and work with Product Management on a market requirements document (MRD) for engineering to specify the product’s final features and functions. Marketing starts to build a sales demo, writes sales materials (websites, presentations, data sheets), and hires a pragency. In this stage, or by alpha test, the company traditionally hires a VP of Sales.
Meanwhile, Engineering focuses on specifying and then building the product. The simple box labeled “Product Development” typically expands into a “waterfall” or “spiral” or incremental process of interlacing steps, all focused on minimizing development risk of a defined feature set (Figure 1.2). This process starts with the founder’s vision, which may be expanded into an MRD (and a product requirements document), and expands further into detailed engineering specifications. With those in hand, Engineering begins implementation fueled by cold pizza and long nights and weekends. Once a waterfall process starts, the proverbial train has left the station and the product is nearly impossible to revise. As a rule, the “train” can run almost nonstop for 18 or perhaps 24 months or more, uninterrupted by changes or new ideas no matter how good they might be for the business.
Figure 1.2 The Product Development “Waterfall” Model
In Webvan’s case, Engineering moved along two fronts: building the automated warehouses and designing the website. The automated warehouses were a technological marvel, with automated conveyors and carousels transporting food items off the shelves to workers who packed them for delivery. Webvan also designed its own inventory, warehouse, and route management systems and software to manage the entire customer order and delivery process. This software communicated with the Webvan website and issued order-fulfillment instructions to the distribution center. Once a delivery was scheduled, the system’s custom route-planning feature determined the most efficient route for delivering the goods to customers’ homes.
At the same time, planning began for a marketing and promotion program designed to strengthen the Webvan brand name, get customers to try the service in the first target market, build strong customer loyalty, and maximize repeat usage and purchases. The plan was to build Webvan’s brand name (down to stickering every cup holder in San Francisco’s AT&T Park) and customer loyalty through public relations programs, advertising campaigns and promotional activities. Spending for all these activities was part of the business plan.
Alpha/Beta Test
In stage three, the alpha/beta test, Engineering continues building along the classic waterfall development model, working toward the first customer ship date. And, by beta test time, working with a small group of outside users to test the product and ensure that it works as specified. Marketing develops a complete marketing communications plan, sets up the corporate website, provides Sales with a full complement of support materials, and starts the public relations bandwagon rolling. The pragency polishes the positioning and starts contacting the long-lead-time press and blogs, while Marketing starts the branding activities.
