Return to Video

04-07 Minimum_Viable_Product

  • 0:00 - 0:03
    The interesting thing about the customer development process
  • 0:03 - 0:07
    ties back into agile engineering and agile development hand and glove.
  • 0:07 - 0:11
    Basically it's this notion of the minimum viable product.
  • 0:11 - 0:15
    Back in the old days what we used to do is specify
  • 0:15 - 0:18
    the entire feature set of the product
  • 0:18 - 0:20
    from beginning to end.
  • 0:20 - 0:22
    Now, this makes sense when you're in a large company
  • 0:22 - 0:25
    releasing version 2.0, 3.0 and 4.0
  • 0:25 - 0:28
    because you kind of have a feeling of who the customers are and what they need,
  • 0:28 - 0:31
    so a product manager can be pretty accurate about
  • 0:31 - 0:34
    I've been interacting with customers for the last year and a half,
  • 0:34 - 0:36
    and I think I know what they need.
  • 0:36 - 0:39
    But in a startup you're really kind of guessing,
  • 0:39 - 0:41
    and the odds are you're going to be guessing wrong,
  • 0:41 - 0:45
    so rather than waste a whole ton of time and money
  • 0:45 - 0:49
    why don't we actually get outside the building before we build something
  • 0:49 - 0:52
    and waste a lot of engineering time, and more importantly,
  • 0:52 - 0:56
    cash, because that's what puts startups out of business is running out of money.
  • 0:56 - 0:59
    We want to make sure that we actually listen to the people
  • 0:59 - 1:01
    who eventually will buy this product.
  • 1:01 - 1:05
    We want to make sure we satisfy their wants and needs.
  • 1:05 - 1:09
    Why don't we just figure out how to build the minimum viable product?
  • 1:09 - 1:12
    Build the minimum features in order to get feedback.
  • 1:12 - 1:16
    Now, feedback could take the form of input verbally,
  • 1:16 - 1:20
    or they gave you early orders, or they gave you anything that was valuable
  • 1:20 - 1:25
    in helping you come to closure on what should we be building in what order?
  • 1:25 - 1:28
    And by the way, an MVP could be something as simple on the Web
  • 1:28 - 1:30
    as a wireframe or a PowerPoint slide,
  • 1:30 - 1:34
    or for physical products it could be a physical mockup,
  • 1:34 - 1:37
    or it could be a working part of the system.
  • 1:37 - 1:41
    But as you get more feedback you could start adding more features.
  • 1:41 - 1:44
    One caveat is a comment I always get is
  • 1:44 - 1:46
    "Steve Jobs didn't build the iPhone by asking customers."
  • 1:46 - 1:50
    And we really doubt Henry Ford asked customers
  • 1:50 - 1:52
    do they want a car before one existed.
  • 1:52 - 1:54
    In fact, in his case if you would have asked people about what they wanted
  • 1:54 - 1:58
    they would have said a faster horse or one with 6 legs.
  • 1:58 - 2:01
    And so the immediate response is "Well, therefore for new products
  • 2:01 - 2:05
    you just don't get out of the building at all," and that's just a fallacy.
  • 2:05 - 2:08
    There is a type of startup in what we call a new market,
  • 2:08 - 2:12
    and we'll be describing new markets in the Customer Segments lecture.
  • 2:12 - 2:16
    But just understand that in new markets of course you don't get out
  • 2:16 - 2:18
    and ask people what features they need.
  • 2:18 - 2:22
    But you do want to understand how is their day in a life
  • 2:22 - 2:26
    different today versus the day after you give them your new product?
  • 2:26 - 2:28
    How does their world change?
  • 2:28 - 2:32
    And there's no possible way sitting locked in your conference room
  • 2:32 -
    or your office you would know that without talking to customers.
Cím:
04-07 Minimum_Viable_Product
Leírás:

04-07 Minimum_Viable_Product

more » « less
Video Language:
English
Team:
Udacity
Projekt:
EP245 - Lean Launchpad
Duration:
02:37
Udacity Robot edited Angol subtitles for 01x-07 Minimum Viable Product
Amara Bot hozzáadott egy fordítást

English subtitles

Incomplete

Felülvizsgálatok Compare revisions