It's about Eric, who is the product owner of team. "One of the hard parts of being a product owner is taking ownership of someone else's idea and helping to make it successful, or proving that it isn't likely to be."
The rest of the chapter "learning faster" uses Eric as an example, but think about your own team, too.
- Discussing Your Opportunity (Your first story discussion is for framing the opportunity),
- Validate the Problem (validate that the problems you're solving really exist),
- Prototype to Learn (sketch and prototype so you can envision your solution),
- Watch Out for What People Way They Want (the real proof is when those people actually choose to use it every day. And it's going to take more than a prototype to learn that.
- Build to Learn
- Iterate Until Viable
- How to Do It the Wrong Way -- this is where the blog from Henrik Kniberg about Making Sense of the MVP is especially important.
There is a simple visual in the chapter, but the full blog is really great, and offers examples of the car (mentioned in the chapter), but in much more detail.
There are also examples of Spotify, the Music Player (really great if you remember back to the early days of Spotify, but certainly great to see how they started thinking of a "music player") and Lego (When they first started exploring the concept, they did paper prototypes and brought them to small kids. The kids’ first reaction was “hey, who are the bad guys? I can’t see who’s good and who’s bad!”) Oops. Back to more design iterations.
The blog ends with Improving on "MVP" - but what he really means is...
Read his blog, it's great, and I learning about it early will be helpful when you are working on your value proposition and prototypes.
Comments?
