profile

Product Practice Newsletter

🛠️ MVPs ≠ Experiments

Published about 1 month ago • 2 min read

MVPs ≠ Experiments

READ ON

HERBIG.CO

PUBLISHED

May 10, 2024

READING TIME

2 min & 42 sec

​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:

video preview

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

  • You’re building towards initial informed conviction by investigating problem and solution spaces.
  • You want to iterate in short cycles to observe and interpret new data points.
  • You don’t need to put value in customers' hands to test an assumption.

When to use an MVP to reduce uncertainty further

  • Your informed conviction about an idea’s desirability is high enough that it justifies the commitment of engineering resources.
  • When user interviews feel like Groundhog Day.
  • When you find yourself saying things like, "Once we talked to these users, we're done with Discovery."

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 Discovery

Learn 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.

Content I found Practical This Week

Product Leaders: Getting Teams Started with Product Discovery

As a leader, you need to coach your team to get better. Even if you don’t know their exact process and aren’t intimately familiar with the product itself, you can guide them. Start by scrutinizing their learnings. This prevents them from just going through the motions of Product Discovery. What have they learned that they didn’t know before they started? What changes will they make to the product as a result of customer feedback?

Should I Run an A/B Test? Blueprint

Champion Vs. Decision Maker: Whom to Target in B2B Customer Discovery?

The decision-maker is the individual who has the authority to decide whether a solution should be purchased and implemented within a company. This is typically a higher-level manager or in smaller companies the C-Suite. It's obvious why the decision-maker is important for the success of your product: Without her support, you can't succeed. The champion is the person who deeply understands the problems you want to solve with your product.

What did you think of this week's newsletter?

👎

Bad

🤷‍♂️

Meh

👍

Great

Who is Tim Herbig?

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.

Enjoy the newsletter? Please forward it. It only takes 2 clicks. Coming up with this one took 2 hours.

Product Practice Newsletter

Turn Product Theory into Pragmatic Application by Tim Herbig

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.

Read more from Product Practice Newsletter

Product Practice #325 I asked 5 CPOs what a Product is. Here‘s what they said. (Part 2) READ ON HERBIG.CO PUBLISHED Jun 7, 2024 READING TIME 4 min & 45 sec Dear Reader, This is the sequel to last week’s newsletter. You can catch-up by re-reading it here. What is a Product? Arne Kittler, Product Org Consultant & Fractional Leader, ex-CPO at Facelift It can make sense to differentiate the external from the internal perspective even though they ideally lead to the same result. Let me explain:...

6 days ago • 4 min read

Product Practice #324 I asked 5 CPOs what a Product is. Here‘s what they said. (Part 1) READ ON HERBIG.CO PUBLISHED May 31, 2024 READING TIME 4 min & 1 sec Dear Reader, Owning and improving product practices and effective team topologies requires a shared understanding of what you actually mean when you say the word “product.” These domains are not called Product xyz because they are done solely by Product Managers. They are called this way because they are in service of bringing products to...

13 days ago • 3 min read

Product Practice #323 What Should Strategy, OKRs, and Discovery Allow You To Do? READ ON HERBIG.CO PUBLISHED May 24, 2024 READING TIME 3 min & 54 sec Dear Reader, It’s tempting to focus the process of practicing Strategy, OKRs, and Discovery on technical correctness. Does the Objective not have a number? Cool! Do you interview one customer per week? Great - Let’s move on. But that’s a pattern of Alibi Progress: prioritizing technical correctness over everyday value. Whenever these ways of...

20 days ago • 4 min read
Share this post