Your SlideShare is downloading. ×
0
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Bus model and cust dev june 2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Bus model and cust dev june 2013

3,760

Published on

Published in: Education, Business
0 Comments
9 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,760
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
469
Comments
0
Likes
9
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. Business Models &Customer Developmentwww.steveblank.com@sgblankTeaching Points
  2. Objective• Review basics• Emphasis on how to teach it
  3. Student Assignments & ToolsIn-Class
  4. Student Assignments & ToolsBetween Class
  5. Student Assignments & Tools
  6. Teaching Team Responsibilities&ToolsIn-Class
  7. Teaching Team Responsibilities&ToolsBetween Class
  8. Teaching Team Responsibilities&Tools
  9. Business Model CanvasWhy?How?
  10. Why?This ClassTEACHING POINT
  11. The Search for a Path1602 - 1908
  12. © 2012 Steve Blank
  13. Business SchoolsTEACHING POINT
  14. The MBAthe Path to Business Execution
  15. Business Schools• Made the American Century• Embraced entrepreneurship– Myles Mace HBS 1947, Stanford 1953– But as an activity you execute• Now embracing searchTEACHING POINT
  16. Startups SearchCompanies Execute
  17. Why?Startups are Not Smaller Versions of aLarge CompanySearch versus ExecutionTEACHING POINT
  18. Startups versus existing companies• That startups begin with a series of unknowns (mostly)– They Search• That existing companies deal with execution of knowns(mostly)– They Execute• The insight is that management tools built to execute donot work in search• Early stage ventures need their own toolsTEACHING POINT
  19. What’s a Startup?
  20. Why?Why a definition of a startup?TEACHING POINT
  21. What’s A StartupA temporary organization designed to search for arepeatable and scalable business model• This is what the class is about• It’s a definition filled with action• Each word has meaning– Temporary– Search– Repeatable– Scalable– Business ModelTEACHING POINT
  22. What We Used to BelieveStrategy
  23. Start With an Operating Planand Financial Model
  24. What We Now KnowStrategy
  25. Planning comes before the plan
  26. Business Models
  27. Why?Business Model versus Business PlanTEACHING POINT
  28. Business Model versus Business Plan• We are not saying never to a business plan• We are saying, “not first”• Plans are static• Models are dynamic• Planning comes before the planTEACHING POINT
  29. What We Used to BelieveProcess
  30. Product Introduction ModelConcept/Seed RoundProductDev.Alpha/BetaTestLaunch/1st Ship
  31. Tradition – Hire MarketingConcept/Seed RoundProductDev.Alpha/BetaTestLaunch/1st Ship- Create MarcomMaterials- Create Positioning- Hire PR Agency- Early Buzz- Create Demand- Launch Event- “Branding”Marketing
  32. Tradition – Hire SalesConcept/Seed RoundProductDev.Alpha/BetaTestLaunch/1st Ship- Create MarcomMaterials- Create Positioning- Hire PR Agency- Early Buzz- Create Demand- Launch Event- “Branding”• Build SalesOrganizationMarketingSales • Hire Sales VP• Hire 1st Sales Staff
  33. Tradition – Hire Bus DevelopmentConcept ProductDev.Alpha/BetaTestLaunch/1st Ship- Create MarcomMaterials- Create Positioning- Hire PR Agency- Early Buzz- Create Demand- Launch Event- “Branding”• Hire Sales VP• Pick distributionChannel• Build Sales Channel /DistributionMarketingSales• Hire FirstBus Dev• Do deals for FCSBusinessDevelopment
  34. Tradition – Hire EngineeringConcept ProductDev.Alpha/BetaTestLaunch/1st Ship- Create MarcomMaterials- Create Positioning- Hire PR Agency- Early Buzz- Create Demand- Launch Event- “Branding”• Hire Sales VP• Pick distributionChannel• Build Sales Channel /DistributionMarketingSales• Hire FirstBus Dev• Do deals for FCSBusinessDevelopmentEngineering • Write MRD • Waterfall • Q/A •Tech Pubs
  35. Customer Problem: knownProduct Features: knownWaterfall / Product ManagementExecution on Two “Knowns”RequirementsDesignImplementationVerificationMaintenanceSource: Eric Rieshttp://startuplessonslearned.blogspot.com
  36. What We Now KnowProcess
  37. More startups fail froma lack of customers than from afailure of product development
  38. Customer Development
  39. Agile Development
  40. +
  41. Why?Customer & Agile Development versusProduct Launch and WaterfallTEACHING POINT
  42. Customer & Agile Development versusProduct Launch and Waterfall• Product Launch process assumes hypotheses are facts• Waterfall development assumes you know:– the customer problem– Entire solutionTEACHING POINT
  43. What We Used to BelieveOrganization
  44. Hire and Build aFunctional Organization
  45. What We Now KnowOrganization
  46. Founders run aCustomer Development TeamNo sales, marketing and businessdevelopment
  47. Why?Functional OrganizationsTEACHING POINT
  48. Functional Organizations• An easy trap for startups• Large companies have VP’s of Sales, Marketing &Business Development• I guess we should too• Titles are the same, functions are radically differentTEACHING POINT
  49. How?Business Model CanvasTEACHING POINT
  50. The Canvas in Class• Forces students to articulate all 9 parts of a businessmodel (static)• Used to keep score of customer development progress(dynamic)• Allows visualization of the entrepreneurial process• 9 boxes provides a convenient tempo for weekly classesDifferent from Osterwalders original intent - strategyTEACHING POINT
  51. What’s a Business Model?
  52. Value PropositionWhat Are You Building and For Who?
  53. Customer SegmentsWho Are They?Why Would They Buy?
  54. Multiple Customer SegmentsTEACHING POINT
  55. Multiple Customer Segments• Might have multiple segments of users• Might have users and payers• Might have 5 or 6 different customers– Medical devices have doctors, hospitals, patient, insurancecompany, FDA, etc.• For every customer segment you need:– Value proposition– Revenue model– And may have unique channels, cust relationships, etc.TEACHING POINT
  56. Product/Market FitValue Proposition + Customer SegmentTEACHING POINT
  57. Product/Market FitDoes the Value Proposition MVP matchthe Customer Segment Archetype?TEACHING POINT
  58. TEACHING POINTTHIS IS THE TOOL TO TEST PRODUCT/MARKET FIT
  59. ChannelsHow does your ProductGet to Customers?
  60. Customer RelationshipsHow do you Get, Keep and Grow Customers?
  61. We define Customer Relationshipsas Get, Keep and GrowDifferent and more actionable thanOsterwalderTEACHING POINT
  62. TEACHING POINT
  63. Revenue StreamsHow do you Make Money?
  64. Key ResourcesWhat are your most important Assets?
  65. Key PartnersWho are your Partners and Suppliers?
  66. Key ActivitiesWhat’s Most Important for the Business?
  67. Cost StructureWhat are the Costs and Expenses
  68. How?Business Model Canvas ComponentsTEACHING POINT
  69. Canvas Components• We overview all the 9 boxes in the first lecture• Subsequent classes detail each of canvas components• But that’s a sleight of hand• What we are really doing is getting the students to talk to100 customers in a quarter• The class is not about the lectures• It’s about the work the students do outside the buildingTEACHING POINT
  70. But,Realize They’re Hypotheses
  71. 9 GuessesGuess GuessGuessGuessGuessGuessGuessGuessGuess
  72. How?Customer DevelopmentTEACHING POINT
  73. Customer Development• While so far the class looked like an easy business modelcanvas class …• The class is actually all about Customer Development!• Drawing the canvas hypotheses are easy• Testing them is really, really hard• Just like a startupTEACHING POINT
  74. Customer DevelopmentTest the Problem, Then the Solution
  75. How?Test the problem, then the solutionTEACHING POINT
  76. Test the Problem then the Solution• Customer development is about hypothesis testing• It’s why scientists do great in this class• What are you testing? All the nice, neat assumptions inthe business model canvas• First, you test basic assumptions• Then, you test the solution itself• Customer discovery and validation is a fairly rigorousprocessTEACHING POINT
  77. Customer DevelopmentThe Minimum Viable Product
  78. How?Build the minimum viable productTEACHING POINT
  79. Build the minimum viable product• This is easy if you use Agile development• You build your product iteratively and incrementally• The goal is feedback, learning, insight, orders, etc. withthe minimum feature setTEACHING POINT
  80. Customer DevelopmentThe Pivot
  81. How?The PivotTEACHING POINT
  82. The Pivot• A core concept of Customer Development• In the past a failure to make “the plan” meant a failure ofan individual to execute• In the past we fixed problems and changed strategies byfiring executives• Now we first fire the plan• A pivot is a substantive change in one or more businessmodel canvas components• An iteration is a minor change in one or more businessmodel canvas componentsTEACHING POINT
  83. Customer DevelopmentDone By the Founders
  84. Customer DevelopmentCanvas to Keep Score
  85. How?Keeping Score with the CanvasTEACHING POINT
  86. Keeping Score with the Canvas• A core concept of the class• Weekly updates of the canvas allow the teaching team tovisually see customer development process• Visualize the canvas extending in the Z-axis• That axis represents the customer development processover timeTEACHING POINT
  87. Customer DevelopmentDetails
  88. Customer Development ishow you search for the model
  89. Customer DevelopmentPhysical vs. Web/MobileProducts and Channels

×