Comments (0)

By brantcooper, March 21, 2011 1:16 pm

At long last, here’s the video from Steve Blank’s presentation last month.

Steve Blank speaks to San Diego Tech Founders from Brant Cooper on Vimeo.

Contents:
00:00 My Intro
03:17 Why Accountants Don’t Run Startups
- Old constraints on startups
- Entrepreneurial explosion
- Startups vs Small Businesses vs Large Businesses
- IBM example of big company disruptive innovation
- What did my income statement say in month 1?
- “You’ve just washed ashore on an a deserted island with a knife in your mouth and a loincloth.”
- Searching for a business model, not a business plan
- Customer Development
58:26 Atoms or Bits (New Material)
- Physical vs Online products
- History of Lean
1:03:26 Sloan vs Durant
1:08:41 Q&A
1:29:50 My Conclusion

Be sure to come check out entrepreneur turned investor Mark Suster talk to San Diego Tech Founders March 31.

=> Startups RSVP here.

=> Investors, Service Providers, Professionals RSVP here.

Comments (5)

By brantcooper, March 15, 2011 12:45 pm

Steve Blank and Alex Osterwalder have combined their respective methodologies, Customer Development and Business Model Generation, into a powerful business model generation and testing framework.  There are several good sources for how these two mesh, including this Jan post on Osterwalder’s blog, here and most recently, in Blank’s SXSW presentation:

Blank’s Customer Development is critical, otherwise speculating what comprises your startup’s business model is just another academic exercise.  Arguably, one could easily waste as much time documenting assumptions on your business model canvas as documenting them inside a 40 page business plan.  The canvas exposes your hypotthesis and customer development tests them.  It’s a laudable ambition to document and test all of your business model canvas components.

But how much is necessary to get going?

All building blocks are not created equal.  I believe there’s a natural progression towards figuring out your business model and many blocks are directly dependent on prior blocks.  Is it worth the time to document 2nd or 3rd tier blocks before establishing the reality of 1st tier?  The answer, of course, depends on you and your business.  It doesn’t hurt to go as far as you can at the start, unless the activity inhibits you from getting started, i.e., “getting out of the building.”

To use a rather simplistic example, you might presume that your customer is an enterprise-sized business that requires a field sales force and partnerships with highly technical systems integrators.  What if your customer ends up being a medium-sized business that requires SaaS product distribution?  Early customer development might very well point you down the correct path from the outset.  Some business model components flow naturally from validated core hypotheses.

The real dilemma in my mind is, what do you test first? The key to getting started is to nail the validate of the core hypotheses: Customer, Problem, Solution.

Go to the #CustDev White Board

In our book, The Entrepreneur’s Guide to Customer Development, Patrick Vlaskovits and I developed a white board exercise to help think through business model risk in order to determine what to test first.  The key components are:

=> draw the ecosystem around your business as you imagine it, including partners, distributors, customers.

=> determine which are mission critical — in other words, can you get going without any?  Which are absolutely necessary?

=> state the value proposition for each mission critical participant — what determines whether or not they join the ecosystem?

=> list the minimum product functionality necessary to get entities to participate.

=> prioritize the risks (technical and market) based on the above.

Ultimately, what you trying to prioritize is: what’s the quickest way to fail your business model. The “value path” of testing your business model runs through testing the the core value proposition of each of your mission critical ecosystem entities.  Easiest to test means:  what you can test in the shortest time frame.

If building a landing page and driving traffic to it has the potential of killing your present business model hypotheses, then it’s a legitimate “intermediate MVP” and worth testing.  But be careful.  Are you sure you’re not testing your ability to drive some amount of traffic or your positioning?  If a 3rd party API doesn’t provide the hooks you need to develop a critical piece of technology and therefore your business model fails, maybe that’s what you test first.

Documenting the building blocks of your business model = good.  Using the #CustDev White Board exercise in conjunction helps you determine what to document and test first.

How do you determine what to test first?

Comments (3)

By brantcooper, February 23, 2011 6:58 pm

I haven’t weighed in on Customer Development thoughts for several hours, so it’s about time. Interesting series of tweets in the last several days got me thinking about the biases we bring to Lean Startup Customer Development practices. Unfortunately, but perhaps inevitable, the biases often result in finger pointing and not a little bit of self-congratulation. To an objective user, however, such instances seem to be rather obvious forest-tree issues, rather than the profound insights they hope to be.

Here’s a handy graphic illustrating source and bias:

If one looks closely, one can perhaps discern my bias. ; )

Let’s go through these.

1. Those with marketing backgrounds are comfortable speaking with customers in a manner determined by their specific role.  Product Managers talk about road map, collect feature requests and bounce ideas off customers, often in group settings (focus groups, advisory boards, etc.).  Product Marketers communicate features and benefits and elicit feedback, often through surveys.  Corporate marketers practice “branding” and spin.  Feedback goes to info@ email boxes, twitter tweets, and Facebook ‘Likes’ (or not).

2. UX Designers are quick to tell you they invented Customer Development only called it something different.  And frankly, they’re right to a degree.  When it comes to product design.  Or parts of product design.  Anyway, UX Designers are good at observing user behavior and interacting with them in a particular (not peculiar) way to determine if the product is “working.”  This is instrumental to today’s products.  (Not always the case, as I’ll argue in another post.)

3. Engineers, in their lifetime quest to never have to actually speak to a live animal of the “Customer” species, utilizes analytics tools and product instrumentation to produce reams of data on user behavior, i.e., actual user interaction with the product.  Instrumentation is instrumental, too.

4. Penultimately and leastly, are the investors, branders, Madison-Ave marketers, turn-key salespeople, high-tech gadflies and backseat pundits who declare that Vision is the only thing that matters.  All you have to do is be like Apple and Ikea, get it?  Do I have to spell it out for you?  All you have to do is be just like A-P-P-L-E.  There now, go to it.

5. Finally, what is the Customer Development bias?  Customer Development needs all the practices above, but none of them help you understand the problem, the pain, the passion. That’s the final leg or better yet, the first leg of Customer Development.  Empathy.  Whatever walk for mankind you need to do to walk a mile in your customers’ shoes; whatever interview technique, lunch buying, drink toting, teatotaling, karaoke yodeling you must participate in to gain an understanding such that you feel empathy.

Now, then, can’t we all just get along?

Please excuse the hyperbole and generalities and the tongue-in-cheek.  Recuse yourself as you see fit.  Feel free to post vitriol in comments. : )

Comments (7)

By brantcooper, February 14, 2011 1:59 pm

Back in December 2009 when Patrick Vlaskovits and I first contemplated our Customer Development book, I was noodling around with a graphic to illustrate the integrate Dave McClure’s Pirate Metrics with Customer Development activities. I posted the graphic in a blog post which garnered lots of attention, including an important comment from Dave himself:

btw, note that AARRR isn’t exactly sequential… in fact, i’d emphasize Activation & Retention *first*, then go after Acquisition & Referral, then optimize for Revenue

Recently, I have caught a couple of my Customer Development clients optimizing the metrics in the “wrong” order, so Dave’s comment bears repeating and perhaps some expounding upon.

The Pirate Says “AARRR”

The anagram is ordered by user experience:

A – Acquisition – User is directed to your site;

A – Activation – User signs up or is otherwise engaged;

R – Retention – User keeps coming back, i.e., is engaged over time;

R – Referral – User invites others;

R – Revenue – User pays or is otherwise monetized;

This is not, however, the order in which you should optimize your product while building your business.  The order (and truly, the metrics themselves) are dependent upon your business model.

For B2C Free, Say RRAAR

Retention – Nail engagement so that users want to or must come back;

Referral – Your business model requires massive user growth, so your product must require referrals to work or must be so cool it just happens;

Activation – Once your users are here to stay and inviting others, optimize their conversion funnel.

Acquisition – Now you’re ready to blow up acquisition.  (Good time to get investment funding.)

Revenue – Millions of users?  Time to monetize.

For B2C or B2B Freemium, Cheer RRRAA!

Retention – Nail engagement so that users want to or must come back;

Revenue – If your business model requires users or businesses to pay, you need to figure out what they’ll pay for before you blow-up anything;

Referral – Since you’re likely not a true network-effects business, you optimize referral after revenue.  Optimizing referral is actually part retention, part funnel optimization.  Users are so happy they will refer others to your site or provide you testimonials or speak to the press, etc.  Not much sense in blowing up your acquisition, however, until you have that level of passion.

Activation – This refers to Blank’s “Sales and Marketing roadmap.”  Here you understand and optimize your sales funnel.

Acquisition – OK, now you can hire that PR firm.

For Enterprise B2B, Cheer an alternative RRRAA!

R – Revenue – If you’re selling to businesses the number one thing you need to prove is that someone cares enough about what you’re providing to give you money for it.

R – Referral – As above, referral in this context means that your customers are willing to sing your praises publicly.

A – Activation – In this context, activation is understanding your sales and marketing roadmap.

A – Acquisition – After you nail your sales and marketing roadmap, you’re ready to feed the top of the funnel.

R – Retention – In enterprise B2B, you often don’t have a subscription model, but may be charging annually for maintenance and support.

Note that you will always need to do some level of “acquisition” in order to figure out and optimize the other stuff.  But the point is that you’re not concentrating on or optimizing acquisition at the start.  Exact order of AARRR is debatable from one business to another, so use above as guidelines only.