Mastering Assumptions: Unlocking Success in Product Development Through Hypothesis-Driven Strategies

Published on
3 minute read

In our ever-evolving landscape of product development, one of the most crucial skills we can cultivate is the ability to work with assumptions. It’s a topic that I’m particularly passionate about, and I’m excited to share insights from our new class focused on this very subject.

Understanding Assumptions in Product Development

First and foremost, we need to acknowledge that assumptions are an inherent part of our product development journey. It’s not just a single assumption we make; often, it’s a multitude of them. Recognising this is the first step towards more effective product management.

  • What assumptions are we making?
    • When discussing potential product futures
    • While creating product backlog items
    • Throughout the entire development process

Understanding the types of assumptions we make is vital, but it’s equally important to determine which of these need validation. Not every assumption carries the same weight; some are critical, while others may be less significant.

Prioritising Assumptions for Validation

In our class, we’ll delve into how to order these assumptions and decide which ones to validate first. This prioritisation is key to ensuring that our efforts are focused on the most impactful areas.

  • Key points to consider:
    • The significance of each assumption
    • The potential impact of validating or invalidating them
    • The resources available for testing

The Role of Hypotheses

Once we’ve identified our assumptions, the next step is to formulate hypotheses. This is where the real magic happens. We’ll explore how to create robust hypotheses and the methodologies for testing them effectively.

  • What we’ll cover:
    • Crafting hypotheses based on our assumptions
    • The importance of using the right data for verification
    • Navigating through a “tree” of hypotheses to test

It’s essential to understand that in product development, we will never achieve 100% confidence in our hypotheses. Instead, we need to define our desired level of confidence and align our testing strategies accordingly.

Experimentation and Analysis

A significant part of our learning will focus on designing experiments that help us test our hypotheses. We’ll discuss how to manage costs related to these experiments and ensure they align with our desired signal strength and confidence levels.

  • Outcomes of our experimentation:
    • Analysing results to inform decision-making
    • Learning from our experiments to refine our approach
    • Developing critical thinking skills that enhance our product development process

Avoiding Toxic Love for Ideas

One of the most valuable lessons I hope to impart is the importance of avoiding what I call “toxic love” for our ideas. It’s easy to become attached to our concepts based on customer feedback or our own biases. However, by adopting a more analytical mindset, we can make more informed decisions that lead to successful product outcomes.

  • What to expect:
    • A new perspective on product development
    • Strategies for effective decision-making
    • Insights into what to do—and what not to do

In conclusion, this class is designed to equip you with the tools and mindset necessary for navigating the complexities of product development. By focusing on assumptions, hypotheses, and experimentation, we can foster a culture of learning and adaptability that ultimately leads to better products and satisfied customers. I look forward to embarking on this journey with you and exploring the exciting world of hypothesis-driven development together.

In our new class, we will learn how to work with assumptions. So first, a very important point: we actually introduce assumption to our product development dictionary. One of the very important points we will learn is this moment of realisation: oh, we have made assumptions, and not one, not two, but many.

So what kind of assumptions are we making when developing products, when discussing potential product futures, when creating product backlog items? This is a very important aspect, but we are not only talking about this fact. Okay, the assumptions were made, but which of them need to be validated? Obviously, not every assumption requires validation. Some of them are more important, less important; there might be a crucial role in ordering our assumptions. So which should be validated first and why? We are going to cover that in this course.

Okay, so first point: assumptions realisation, ordering, and choosing which one to start. The second one, when we work with assumptions, the next important topic is about hypothesis. So we will learn how to create hypotheses and how to test them. In this class, we will pay a lot, a lot of attention to using the right data that will help you verify your hypothesis.

In fact, we may realise that our product development is actually navigating around some kind of tree of different hypotheses to test. We will also discuss the topic of the importance of desired signal or evidence strength on our product development process. So when we test assumptions, when we talk about hypothesis-driven development, it’s important to realise that there will never be 100% confidence. But what is your desired level of confidence? And based on that, how high do you want to be when it comes to confidence?

We will be talking about experiments that will help us test the hypothesis. So we will learn how to manage costs related to product development based on those experiments that we choose, and this will be aligned with desired signal strength and desired confidence level.

Another valuable outcome for us is learning how to analyse experiments, how to take what we got out of our experimentation journey, and how to use this data in the decision-making process. So we already talked that learning is important in this class. So think about it as a way of targeted learnings that will help in this decision-making and critical thinking.

Thanks to that, we want to avoid toxic love related to our ideas and to what customers told us. Instead, we will be equipped with a certain way of thinking. Maybe for some of us, it will be a new perspective on product development, and thanks to that perspective, we will be learning a lot about what to do, what not to do, and how to use those concepts to be effective in our product development.

Hypothesis Driven Development

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Epic Games Logo
Xceptor - Process and Data Automation Logo
Akaditi Logo

NIT A/S

Graham & Brown Logo
Workday Logo
Lockheed Martin Logo
Milliman Logo
Emerson Process Management Logo
Boeing Logo
Hubtel Ghana Logo
Higher Education Statistics Agency Logo
Boxit Document Solutions Logo
Capita Secure Information Solutions Ltd Logo
Philips Logo
Freadom Logo
Qualco Logo
Deliotte Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Washington Department of Enterprise Services Logo
Nottingham County Council Logo
Washington Department of Transport Logo
Ghana Police Service Logo
Alignment Healthcare Logo
Hubtel Ghana Logo
Higher Education Statistics Agency Logo
Microsoft Logo
Healthgrades Logo
Qualco Logo