By evaluating confidence, you get a much clearer picture about which ideas you need to further explore during Product Discovery. High impact, low confidence items are your first opportunities to evaluate. A roadmap is a plan of what activities a team plans to do and in what order they plan to do them. The roadmap should be updated on a rolling cycle-based cadence and aligned to the activities of Strategy and Goal iterations. OKRs stand for Objectives and Key Results, and usually refers to the business strategy tool/framework that can be used in order to measure and track progress towards specific objectives. Nonetheless, the Delivery and Discovery activities overlap and interact, with their respective peaks occurring at distinct periods in the product management lifecycle.
Unmet needs vary – it may be a market that is completely underserved or it might be met by an incumbent product (including yours), but filled with frustration. Therefore, check if the strategy is working as soon as you have released the new product or product version. Continue to do so by scheduling collaborative quarterly strategy reviews and carrying some strategy work every week, as I discuss in more detail in the article Continuous Strategizing. As shown, initiatives entering the pipeline undergo a screening process, which determines whether to incorporate them into the roadmap or reject them. To be included in the roadmap, all initiatives must meet the conditions to enter the “Ready for Discovery” buffer.
- But through deliberate product discovery, successful teams transform those raw seeds of ideas into beloved products rooted in real customer needs.
- By creating a reverse income statement and defining checkpoints and milestones, Discovery-Driven Planning helps improve resource allocation and decision-making.
- These insights can inform future expansions or the development of new products or services.
Transform your approach to goal setting and strategy execution with this essential read. The test was successful, so there was no need to consider alternative solutions or talk to the users again. Next, they prioritized opportunities that are important for the users, where their satisfaction with their ability to achieve a specific outcome was low. In this example, we started with the desired outcome of increasing customer engagement for a video streaming platform by 20%. Here, we explore the problem space to understand and define opportunities (problems, needs, desires) that, when solved, will drive the desired outcomes.
As shown, initiatives entering the pipeline undergo a screening process, which ultimately determines whether to incorporate them into the roadmap or reject them. To be included in the roadmap, all initiatives must meet the necessary conditions to enter the “Ready for Discovery” buffer. In case any of the previous steps fail, you’ll go back one step upstream and choose another option. The user story format can be helpful in thinking about product interactions from a user’s perspective. Use this template to display objectives and key results and gauge progress.
If you seek to develop truly impactful products, the path forward begins with enlightening discovery of non-obvious truths. By setting your overarching goal or higher-level goal at the WHY level, you then navigate to the WHO level by identifying customer segments, then the HOW level to identify objectives. The company size and product lifecycle stage significantly influence the Discovery process. Market Discovery looks at the effectiveness of go-to-market strategies, measuring success through market response, customer acquisition costs, and early adoption rates. In the realm of Discovery, every decision level is riddled with uncertainty, hence the emphasis on ‘discovery’.
Which, when solved right, will lead to your business metrics improving as well. A lack of clarity around WHY you should care about this Discovery scope can lead to issues like solutioning or falling for confirmation bias down the road. But even if you’re aware of the importance of alignment, not all alignment is created equal. This analogy translates well to the non-linear, but loosely-connected, individual phases of Product Discovery teams can choose from when navigating their path toward reducing uncertainty. Please keep in mind that the definition of Product Discovery collaborators will and should change throughout your Discovery. The degree to which each group is involved ultimately depends on your Discovery https://aboutchromebooks.com/product-discovery-methods-derribar-ventures-limited/ setup.
The problem space is the area of focus for a product, while the solution space is where potential solutions are explored. It is important to differentiate between the two, as spending too much time on ideation can be counterproductive. Product Discovery is a process that helps you focus on what matters in your product.
This approach helps you focus on the key drivers of success for the project, rather than getting bogged down in irrelevant details. By starting with the end goal in mind, you can ensure that every decision you make is aligned with that goal. The next step is to create a reverse income statement, which is essentially a budget for the project.
Product Strategy & Roadmap
Whether you’re looking for a way to improve a product that is already in use or you’re about to build something that aims to serve an unsolved need, identifying what your users want and need is critical. When articulating the Outcomes you want to drive, don’t fall for expressing what you, as the business, want your users to do. That’s a clear sign that you need more user insights and more research activities around a strategic Problem Space. Some companies “simply” set up permanently dedicated Product Discovery teams that end up handing over their insights and results to separate Delivery teams for execution.
Trial Preparation: A Beginner’s Guide
The outcomes will serve as guidance for defining release goals or sprint goals. You can use Impact Mapping to plan the release strategy for your new product in alignment with your OKRs. This process is not only helpful to ensure strategic alignment but also to craft meaningful release goals and sprint goals for your product delivery.
With the right executive sponsorship, structured approach, and cross-functional collaboration, enterprises can overcome inertia to nail product-market fit. Discovery takes time and investment up front, but ultimately saves resources and leads to better solutions long term. With strategic rollout planning, vigilant monitoring, and continual iterations, validated products successfully transition to market while delivering lasting value. This quantified, user-centered process ensures the product delivers tangible value from the start. Early access user insights build an outstanding V1 foundation for broader rollout success.
By determining the perceived value, potential pricing, and estimated costs, a business case or financial model can be developed to evaluate the idea’s potential success. Discovery-Driven Planning has its origins in the idea of “discovery-driven learning,” which was developed by McGrath in the late 1990s. The idea behind discovery-driven learning is that product development is often uncertain and unpredictable, and that companies need to adopt a learning-driven approach to manage this uncertainty. Another challenge during the “final” phase of a Product Discovery is to slice a concept into a prioritized list of backlog items and think about potential releases. The overall vision for your product or feature idea will guide you along the way, but it shouldn’t prevent you from shipping earlier iterations to learn from your users. The days of building and releasing a complex concept in one monolithic effort are over.
Roadmap design can directly impact the autonomy your team has for Product Discovery. This approach allows teams to lay the groundwork for success without rushing through the discovery and delivery process. Of course, it’s crucial to ensure that these OKRs are directly tied to actual strategic themes, rather than being used as a task list to keep the team busy. One of the challenges of using OKRs in product management is syncing the discovery and delivery processes with goal cycles. In other words, syncing product strategy definition and review cycles with product discovery and delivery cycles. Once you have several strategic themes, you’ll evaluate them using business discovery to gauge their potential and challenge.
It’s important to note that these levels are not strictly sequential and you may need to go back and forth between them as you validate your assumptions and adjust your strategy. In each of these stages, identifying and addressing the right risks is not just about avoiding pitfalls; it’s about strategically moving forward with confidence and clarity. To truly grasp Discovery, we must first clarify what we mean by ‘problem’ and ‘solution’. A ‘problem’ refers to any type of risk that needs addressing, while a ‘solution’ provides the strategy to mitigate that risk. Because it better captures the full scope of transforming a business need into a market-winning product.
Continuous Strategizing
Defining checkpoints and milestones is important for tracking progress and ensuring that the product development process stays on track. This helps to identify potential issues early on and make adjustments as needed. Creating a reverse income statement is another key principle of Discovery-Driven Planning.
User focus, focus, enthusiasm, and flexibility are the keys to successfully completing product research, which will lay the foundation for building the right product. In this guide, we summarize years of discovery and product strategy work to help you understand the product discovery process and the methods teams use to develop ideas that lead to innovative products. When teams embrace Product Discovery, it’s often due to the fatigue of being in the hamster wheel of building more features (that nobody needs and that don’t contribute to business goals).
Product discovery helps you move beyond assumptions and build on evidence so you can prioritize confidently, reduce risk, and create products that customers love. With the right process in place, teams can transform shallow ideas into successful products that customers love. Legacy technology, processes, and mindsets can make it tougher to experiment quickly.
It demands a deep understanding of the market, a strategic approach to business and product design, and a commitment to continuous improvement. By embracing Discovery as a comprehensive, organization-wide practice, teams can navigate uncertainty, mitigate risks, and pave the way for products that not only enter the market but dominate it. Before I proceed, let me point out that I am neither a product discovery expert in the sense discussed below nor do I fully endorse the specific approaches created by Marty and Teresa. My intention with this article is to show how product teams can use a product strategy to guide their discovery work and maximise the chances of creating successful products. The primary goal of a discovery strategy is to uncover insights that inform decision-making, preventing costly mistakes and increasing the likelihood of market success. It helps teams explore a problem space deeply, define user personas, and hypothesize potential solutions before investing heavily in building.
Finally, at the product level, you need to build the right thing by understanding the problem space and finding the best solution. This value proposition will then be validated through several experiments before building. Historically, companies invested in discovery before launching new products or adding major functionality. But today, discovery is increasingly seen as a continuous process that happens throughout the product lifecycle.
If you’re (too) focused on squeezing in that customer interview week after week, the chances are that you stop talking to the right users. In fact, the main idea behind this guide is to help you to make progress in YOUR environment and ADAPT what you’re learning to your everyday life. This is the act of interpreting the insights, or articulating the changes in behavior we seek to create in the form of Outcomes. Outcomes serve as the measurable proxies we can use to determine whether we have both solved a real user problem and contributed to overarching business priorities. An Impact Map can also act as a very effective input to the OKR definition of Product Teams, as it beautifully condenses insights and connects activities (or the lack thereof) to high-level company priorities. Here’s a comprehensive overview of how Impact Mapping connects to and differentiates from some other popular product frameworks.
Roadmap design can impact the autonomy your team has for Product Discovery. Of course, it’s imperative to ensure that these OKRs have a direct connection to actual strategic themes, rather than using them as a task list to keep the team busy. One challenge of using OKRs in product management is syncing the discovery and delivery processes with goal cycles. Product discovery has become increasingly popular in recent years as a way to determine the right solution.
While these processes are not strictly one after the other, it’s vital to begin with a solid strategy. Only then can you explore a business model based on market opportunities, leading to the creation of a product designed to seize those opportunities. How can you be sure that it’s the right outcome to pursue, that others are not more urgent or valuable? To put it differently, if the business goal is wrong, you are likely to determine the wrong opportunities and discover the wrong features and user experience. Now that we’ve looked at what discovery is, let’s look at why it’s important for your marketing strategy.
In Market Discovery, user feedback informs go-to-market strategies by identifying effective messaging, positioning, and channels that resonate with the target audience. Integrating user feedback into the Discovery process is crucial for ensuring the product meets market needs and expectations. Tailoring the Discovery process to the company’s size and product’s lifecycle stage ensures that efforts are effectively aligned with current needs and resources. Early-stage products require a heavy focus on Product and Market Discovery to validate the product-market fit, while mature products might concentrate on Growth Discovery to explore new markets or features. As companies grow, the Discovery process may become more structured, with dedicated teams for each Discovery phase and more emphasis on scaling and optimizing existing products. In startups, Discovery tends to be more agile and iterative, with a focus on quickly validating business and product hypotheses due to limited resources and the need for rapid market entry.
This involves creating a culture that encourages experimentation, failure, and continuous learning. It also involves creating systems and processes that support this culture, such as regular team retrospectives and knowledge sharing sessions. Discovery-Driven Planning differs from traditional planning methods in that it emphasizes experimentation and learning over prediction and planning. Traditional planning methods are based on assumptions and predictions about the future, whereas Discovery-Driven Planning is based on a continuous process of testing and learning.
