Abstract: Early in the agile movement, large technology challenges were often given to alchemist like wizards we called "Architects". They were essential, and sometimes helpful, but also hard to find and sometimes a single point of failure. Experimentation taught many of us the finding a new wizard was not the answer. Instead, the answer was to break down large problems into smaller problems distributed to a collection of builders who collectively and collaboratively took ownership of the system and its architecture.
Today, we have the same opportunity in the product space. Many companies are finding success by what I would like to discuss as "dynamic product discovery". To explore this topic, we can talk about who is needed for product discovery, how often is product discovery helpful, how can we blend product discovery and product delivery into a fluid cadence where product leaders work in one of both tracks, or dynamically float between the two.
Please show up ready to challenge the status quo and explore our new options around product learning, product discovery and the essential need to scale product learning in large systems, especially in IT shops where product and service may be playing second fiddle to customers and interactions.
Learning Outcomes:
