Assumptions vs. Experiments vs. Hypotheses​Dear Reader,​ “Make sure you treat this as an experiment.” “Our working hypothesis is that people want this.” Are any of these familiar? Your team (or the entire organization) might regularly mix up the terms assumptions, experiments, and hypotheses, which can create confusion at best. Let’s clarify what each of these means. An Assumption is a statement about what we believe to be true about an idea. Stated in a format like “We believe…” Typically, your assumptions center around an idea’s feasibility, usability, viability, desirability, or ethicality. An Experiment is a technique we use to test the most critical but least proven assumptions to collect reliable evidence about whether a specific assumption is valid. Your experiment technique needs to match the nature of your assumption instead of dogmatically defaulting to A/B tests. A Hypothesis explicitly defines success for a given experiment and ties it back to the assumption. It describes the measurable change you expect through the chosen experiment technique. Which means it has to be falsifiable. By incorporating your initial assumption, you focus instead of chasing opportunistic ideas. There are countless formats, but a simple one is: Based on [evidence]. We believe [idea] will encourage [target audience] to [change behavior = outcome]. Our confidence in this solution increases when we see [metric change] during [experiment]. Your experiments (and metrics) might change or expand as you test the idea from different angles. Let’s assemble the pieces: We’re a European car marketplace looking to expand to the US and will use Private US Sellers of Vintage Premium Cars as a strategic wedge to break into this market. An AR-based car intake scanner is a feature idea that addresses the need for people to get their cars vetted without searching for in-person experts. The two most critical assumptions are “We believe car owners trust us to evaluate their cars digitally” and “We can automatically recognize 90% of a vintage car’s details through a digital smartphone scan.” One experiment to test the former is a Wizard of Oz MVP, which has human experts evaluate sent-in photos manually and deliver a prediction asynchronous back to the owners. Which has us arrive at this hypothesis: An AR scanner will encourage US vintage car owners to list their cars online without a physical inspection. Our confidence in this solution increases with an acceptance rate of 80% for our manually delivered photo-based evaluations.​ 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​ PS: I messed up last week's link, so here we go again. Do you Interview Users? Do you have “no shows”? Fill out this short survey to learn more about a free productized solution to that. 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 #367 3 Prompts to help TeamsGo from KPIs to OKRs READ ON HERBIG.CO PUBLISHED Jun 13, 2025 READING TIME 3 min & 56 sec Dear Reader, In theory, distinguishing KPIs from OKRs should be simple. KPIs are reactive metrics you monitor, but only act on when they exceed or drop below a certain threshold. Think revenue or conversion rate. Objectives and Key Results (OKRs) contain proactive metrics that help you measure your progress towards strategic priorities. Consider revenue from a...
Product Practice #366 Why bol.com made itsgoal-setting more pragmatic READ ON HERBIG.CO PUBLISHED Jun 6, 2025 READING TIME 5 min & 30 sec Dear Reader, This is the final part of my mini-series on how bol.com, one of Europe's largest e-commerce companies, shapes its fintech products. After exploring their product definition and discovery practices, let's look at how they've adapted traditional goal-setting frameworks to their reality. Particularly as a function that wears two hats, enabling...
Product Practice #365 How bol.com kills ideasbased on Discovery Insights READ ON HERBIG.CO PUBLISHED May 30, 2025 READING TIME 5 min & 18 sec Dear Reader, This is the second part of my mini-series on how bol.com, one of Europe’s largest e-commerce companies, shapes its fintech products. Last week, we looked at how they combine regulatory compliance with customer value. This week, we'll look at how they adapt discovery practices to their unique context, leading to killed ideas and adapted...