MVPs ≠Experiments​Dear Reader,​ Don’t make the mistake of “Let’s test this assumption with an MVP.” I called out MVPs for being too expensive for shortening the lead time towards reducing uncertainty during Product Discovery back in 2017: ​As Casey Winters defined it, “An MVP is all about delivering value to users by building the smallest product you can to test a hypothesis. You ship to learn, which influences future product development.” While shipping to learn can be a crucial choice for further reducing uncertainty, there’s so much more you can do before building even the smallest version of a product. In contrast, you can use experiments to test assumptions without delivering value to customers. Think of usability testing of Figma prototypes or fake door tests. That doesn’t make these techniques better or worse than an MVP; they are just differently suited for different contexts. One of my favorite prompts to help product teams move out of Discovery motions and get into Discovery action is this: “If you only had one week to reduce uncertainty as much as possible, what would you do? And why aren’t you doing it now?” That doesn’t mean Discovery has to be done within a week, but it enforces a sense of urgency toward reducing uncertainty with the shortest possible lead time. Otherwise, Discovery work will continually expand to whatever time box you give. Consequently, aiming for an MVP as a Discovery artifact will carry overhead and dependencies since it requires actual code to be shipped to production. When to use Experiments to reduce uncertainty further
When to use an MVP to reduce uncertainty further
Did you enjoy this one or have feedback? Do reply. It's motivating. I'm not a robot; I read and respond to every subscriber email I get (just ask around). If this newsletter isn't for you anymore, you can unsubscribe here. Thank you for Practicing Product, ​Tim​ How to Dive Deeper into Product DiscoveryLearn how I helped companies like Deutsche Telekom and Forto hone their Product Discovery practices. I closely work with product organizations through workshops and coaching to introduce and adapt Product Discovery.
What did you think of this week's newsletter? As a Product Management Coach, I guide Product Teams to measure the progress of their evidence-informed decisions. I identify and share the patterns among better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery. |
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.
Product Practice #332 Why you don’t get Value from your Product Strategy READ ON HERBIG.CO PUBLISHED Sep 6, 2024 READING TIME 4 min & 26 sec Dear Reader, It’s tempting to focus the start of your strategy creation on a framework or by-the-book advice. Have you filled out the canvas? Cool! Does it meet all the "Good Strategy" criteria? Great—let’s move on. But that’s a pattern of Alibi Progress: prioritizing technical correctness over everyday value. Whenever Product Strategy feels like a tick...
Product Practice #331 What does it taketo talk to customers? READ ON HERBIG.CO PUBLISHED Aug 30, 2024 READING TIME 4 min & 29 sec Dear Reader, Together with my friends at Orbital (a company I advise), I recently ran a LinkedIn poll about user interview behaviors. My goal was to get a rough overview of how product teams approach preparing customer interactions. Here’s what I learned from the 320 total votes: Who schedules your customer interviews? Most (55%) of participants schedule interviews...
Product Practice #330 The Problem with 0-1 Metrics READ ON HERBIG.CO PUBLISHED Aug 23, 2024 READING TIME 3 min & 51 sec Dear Reader, Scaling Product Discovery requires more than just having teams talk to more users. In fact, just having teams interview more users without structure and some baseline education might do more harm than good. Here’s what I took away from training over 30 product trios at The StepStone Group: #1 Educate Cross-functional, wherever possible It doesn’t make sense to...