In this episode, I share with you practical tips that help you to deal with upcoming feature ideas during product discovery so you don’t talk about the solution space too early.

In this episode, I share how to not let Confirmation Bias destroy your Product Discovery efforts.

In this episode, I will talk about why you should engage the engineers on your team in Product Discovery - And how you can do it.

One of the core messages I constantly repeat when talking about Adaptable Product Discovery is the amount of time product teams should spend on understanding the problem space compared to thinking about solutions during it. One framework that is often mentioned in that context is a Design Sprint (DS). So, let's take a closer look at how a Design Sprint and the broader activity of Product Discovery (can) play together.

When we talk about building and validating products, we talk about a broad range of aspects to consider. Can we build it? Can people use it? Do people want it? The problem here is that testing a prototype in the lab only tells you one part of the story. And while it’s worth arguing that telling 50% of a story is better than not to start talking at all, you have to put it into the right context.

Treating Product Discovery as a continuous practice instead of a one-off effort is important to establish the habit of acting customer-centric as a Product Team. However, the act of continuously digging through data for „new“ insights, trying to get in touch with users every week, and running experiments at a too frequent rate can bear some pitfalls. In this episode, I will share a summary of my personal experiences of continuous Product Discovery efforts.

A Minimum Viable Product (or MVP) is probably one of the most over-used (and misused) terms in product management. So, today, I want to talk about the main misconceptions of MVPs and what you can do to prevent them.

In this episode, I will discuss the biggest red flag, for recognizing whether you’re doing actual Product Discovery, or just polishing pre-determines feature ideas

Just like me, you're probably guilty of using Impact, Outcome, and Output interchangeably at least one point of your career. But what if there's more meaning to these teams and how can they change the way product teams make decisions? That's exactly what we'll discuss in today's episode.

This episode is all about the problems maintaining an Idea Backlog brings with it for Product Teams. And what you should do instead, to avoid talking about solutions too early and too often.