Bridging the Gap: Codifying Product Discovery and Understanding Knowledge Dynamics

Bridging the Gap: Codifying Product Discovery and Understanding Knowledge Dynamics

In the realm of product development, two fundamental processes emerge: Discovery and Delivery. While Delivery focuses on the execution of building and shipping products, Discovery is about identifying what to build in the first place. The challenge many organizations face is the lack of a structured Discovery process. This article explores the critical need for codifying the product discovery process while also examining the nature of knowledge in different fields, ultimately linking these concepts to foster a culture of innovation.

A significant portion of the issue lies in the way organizations prioritize their performance metrics. Many companies inadvertently prioritize Delivery over Discovery, leading product managers (PMs) to skip crucial exploratory stages. This tendency is often reinforced by stakeholder assumptions that the necessary research has already been conducted. However, the truth is that without a systematic Discovery process, organizations risk investing resources into building features that may not address real user needs or market demands.

To combat this issue, organizations must embrace a mindset shift that emphasizes the importance of Discovery. This shift should be reflected in the company’s culture, encouraging PMs to allocate time and resources to explore problems thoroughly. To effectively codify Discovery within an organization, four pillars must be established: Training, Templates, Touchpoints, and Targets.

Training is essential for equipping PMs with the skills necessary to conduct effective Discovery. By fostering a learning environment, organizations can empower PMs to become adept at identifying and analyzing problems.

Templates play a crucial role in ensuring consistency in the Discovery process. Two vital templates that should be developed are the Problem Brief and Problem Definition. The Problem Brief serves as an initial exploration of the problem, outlining symptoms, business requirements, and the external landscape. This document helps PMs assess whether the problem is worth solving and what actions might be necessary to refine it.

Following the Problem Brief, the Problem Definition document clarifies the specific problem at hand, differentiating between customer and business issues. It should include data and insights that validate the problem's existence and highlight its significance. Additionally, the Problem Definition document should outline the constraints within which solutions must be developed, ensuring that the proposed solutions align with the organization’s broader goals and resources.

Touchpoints facilitate the review of insights and learnings, allowing PMs to share discoveries and gather feedback from their peers. This collaborative approach ensures that all product squads are aligned with the company’s strategic objectives and focused on solving the most pertinent problems.

Finally, organizations must establish Targets that incorporate Discovery into the expectations for PMs. This can include integrating Discovery-related goals into performance reviews, progression frameworks, and quarterly objectives. By embedding Discovery into the organizational fabric, companies can cultivate a culture that values innovation and experimentation.

While the codification of the Discovery process is critical, understanding the nature of knowledge itself also bears significance. Knowledge can be categorized as cumulative or cyclical, influencing how organizations approach problem-solving. In fields like finance, knowledge tends to be cumulative, with insights building on one another over time. Conversely, in behavioral fields—such as relationships, philosophy, or product development—knowledge may be more cyclical, often repeating patterns rather than advancing linearly.

This distinction is crucial for PMs as they navigate the complexities of product development. As physicist Richard Feynman pointed out, human behavior is inherently unpredictable, making it challenging to apply rigid formulas. Thus, a flexible approach that accommodates the cyclical nature of knowledge is essential for effective product Discovery.

In conclusion, codifying the product discovery process is vital for organizations seeking to innovate and meet user needs effectively. By establishing a structured framework that emphasizes Training, Templates, Touchpoints, and Targets, companies can create an environment that nurtures creativity and problem-solving.

Actionable Advice:

1. Implement Regular Training Sessions: Schedule workshops and training programs for PMs to enhance their Discovery skills, focusing on effective research techniques and stakeholder engagement.

2. Develop and Utilize Templates: Create standardized templates for Problem Briefs and Problem Definitions, ensuring all PMs have access to consistent tools that facilitate thorough analysis before moving to the Delivery phase.

3. Establish Cross-Functional Touchpoints: Organize regular meetings or forums where PMs can present their findings, share insights, and collaborate with other teams, fostering a culture of continuous learning and alignment with organizational goals.

By taking these steps, organizations can bridge the gap between Discovery and Delivery, ultimately driving successful product outcomes and fostering a culture of innovation.