According to the Professional Scrum Product Owner™ II guide, one of the keycompetencies of a Product Owner is to validate product assumptions and hypotheses using empirical evidence1. This means that instead of investing a lot of money and time into building a product based on unproven ideas, the Product Owner should conduct small experiments to test the viability, desirability, and feasibility of the product2. These experiments can take various forms, such as prototypes, mockups, surveys, interviews, landing pages, etc. The goal is to gather feedback from real or potential users and customers, and measure the outcomes against predefined success criteria3. Based on the results of the experiments, the Product Owner can then decide whether to persevere, pivot, or terminate the product idea4. This approach helps to reduce the risk of wasting resources on products that nobody wants or needs, and to focus on the most valuable and promising ideas.