Product Discovery: Stop chasing requirements (MONDAY)
Stop chasing requirements and start executing evidence-based product discovery
Are you tired of executing pre-determined solutions or just facilitating an exchange of opinions?
Structuring and executing a Product Discovery can feel like a lonely task and uncovering customer behaviors worth changing and connecting them to what the business needs seems impossible.
Learn how to take the next step: to go from delivering features to stakeholders on a fixed budget and deadline to building products your customers will love.
After this workshop, you will feel confident about uncovering user needs and shaping a product users want to use. You will experience a new level of clarity when it comes to collecting evidence, turning it into ideas worth pursuing, and experimenting with what works.
Anders will reveal his playbook of cleverly thought out product-experiments, that will help you validate whether your product idea floats; if your potential customers want to pay for what you intend to offer - even before writing a single line of code.
What you will learn:
You don't necessarily need to write a single line of code (or involve the development team) to test your most critical assumptions. Product experiments represent clever and practical ways to test the problem, market, product, and willingness to pay.
Designers have developed a number of techniques to avoid being captured by oversimplified solutions. Taking the original problem as a suggestion and not a final statement, designers investigate the fundamental issue that needs to be addressed. Designthinking start with the problem and desired outcome rather than the solution.
A tool to categorize assumptions by certainty (known/unknown) and criticality (important/not important) with the purpose of creating an overview and prioritization of what should be planned for development and what requires further investigation through experiments.
Dual Track Scrum
Separates the effort to discover the best solution from the effort to deliver working software. It consists of two tracks of activity: discovery and delivery. The discovery backlog holds the experiment backlog for the assumptions that was categorized as inmportant and unknown during assumptions mapping.
Within the delivery branch, continuous delivery and integration are popular methods to minimize risk of delivery failure. When it comes to business objectives and customer needs, the process is centered around discovery and improvements in regard to business value.