How do product discovery roles help the product teams? But before that, let us have a quick overview of product discovery.
Product Discovery Overview
Product discovery is the process of unearthing unmet needs and making discoveries that benefit customers. It is an iterative process of ideation, prototyping, testing, and learning.
Product discovery helps in developing deep insights into what customers want. It also helps in understanding the product strategy. The product strategy is a set of decisions about what to build, how to build it, when to ship, and how much to charge for the product.
Product discovery is not a project or a phrase that you do at the start of your product life cycle. It is an ongoing process that takes place over time – it is an ongoing process that never ends.
The product discovery roles are part of this ongoing process. They help in focusing on specific aspects of the product strategy. They help in creating a structure for this process.
The Product Discovery Roles
There are three distinct but complementary product discovery roles: The Ideation Roles, The Probing Roles, and The Product Architectures Roles. Let us have a quick look at each of these roles.
The Ideation Roles
The ideation roles are responsible for creating new ideas for opportunities or solutions to problems/opportunities that your customers face. These roles are responsible for ideating new ideas about what product you should build next, how you should build it, who should build it, etc.
The Probing Roles
The probing roles are responsible for conducting research on products and activities, conducting fieldwork, talking to customers, and collecting data. These roles are responsible for probing your assumptions about the problems/opportunities that your customers face, new ideas about what product you should build next, how you should build it, who should build it, etc.
Planned experiments are conducted by the probing roles. The data collected is analyzed to validate or invalidate the hypotheses.
The Product Architectures Roles
The product architecture is a set of decisions about what to build, how to build it, when to ship, and how much to charge for the product.
These roles are responsible for creating this structure. They help in deciding what things need to be built and by whom. They help in deciding how these things should be built. Also, they help in deciding when these things should be built or shipped. Even in deciding what these things should cost.
Product Discovery Roles For The Product Teams
Let us look at each of these roles in more detail.
The Product Lead Role
The product lead is responsible for making decisions about what to build, how to build it, when to ship, and how much it should cost. He makes these decisions after validating the hypotheses through data analysis. The product lead may be the same person as the product owner or may be different.
The Product Architect Role
The product architect role is very similar to the product lead role. The only difference is that the product architect takes suggestions from other team members for making decisions about what to build, how to build it, when to ship, and how much it should cost. He takes these suggestions after validating the hypotheses through data analysis.
The Product Owner Role
The product owner’s role is responsible for creating and maintaining the product backlog. This role is responsible for prioritizing and ordering the stories in the product backlog using the MoSCoW method. The product owner’s role ensures that the stories in the product backlog are of high value to customers.
The User Experience (UX) Designer Role
The UX designer role is responsible for designing and creating user interfaces. This role is responsible for making sure that your interface makes sense to your customers.