A visual representation of the final product idea allows users to interact with the product as if it were real, without the need for actual development. Moreover, a clickable prototype can be used to test different user scenarios, such as user flows and user journeys. This can help the team to understand how users will interact with the product and what steps they will take to accomplish their goals. To thrive in this dynamic landscape, top organizations understand that the improvement of their products is fundamental and constant. New technologies and trends are always emerging, so evaluating and refining digital products must be an ongoing process. Put simply, continuous product discovery involves collecting product learnings as we communicate with customers throughout the entire development cycle, and on a continuous basis.
We have long argued that there have always been at least two major ways to develop product. Product organizations need to come to terms with the fact that the product invention process is fundamentally a creative process. Please note that doing so will share data with third-party providers. You might argue that every experiment (if set up correctly) generates some kind of insight and COULD help the team succeed, but this often feels like sandbagging. Maybe you are aware of the particular Motivations and Problems an Actor experiences in a given situation. But what about other Problems that prevent the Actor from achieving the same Motivation?
To correctly identify challenges, you must understand the underlying user needs you want to solve with your product. At this stage, product teams rely heavily on quantitative and qualitative research to find answers. Some useful tools and techniques to use include user research, focus groups, observation, customer interviews, data analytics, competitive research, empathy mapping, and more. This led to a lot of very expensive failures, as products often made it to full release before their creators realized that people just didn’t need them.
You could create a basic landing page where people could start the “personality test.” From there, you could lead them to a survey tool like Typeform. The answers from the survey could get pushed into whatever tool you’d like to use through a connection established by Zapier. Assuming you won’t show your prototype to thousands of users, why not create the final “assessment” using predefined text blocks that match the incoming survey feedback? Combine it with a free, but professional-looking, email tool like MailChimp and your prototype is ready for testing.
The aforementioned research leads to the creation of a clear and specific problem statement. This statement outlines the details of the user challenge the team will try to solve. Listen to continuous discovery expert, Teresa Torres’s episode on Insights Unlocked here. And if you’re ready to try out a visual bug tracking and feedback solution, Usersnap offers a free trial. Ask Sol anything about digital products, AI, engineering, or growth, and get answers drawn from years of Net Solutions thinking and experience.
For this reason, it’s vital to approach product discovery with a mindset that’s open to all possibilities. You might start the process with a really cool idea for a product in the back of your mind, only to find out that your users don’t need a new product after all. Maybe a few specific improvements to your existing product are enough. This kind of realization is all part of the ‘discovery’—it’s what makes product discovery both useful and interesting. Alongside discovery as an initial exploratory stage, continuous product discovery, is a tool, mindset, and way of working that embraces the drive for customer feedback and makes it habitual.
The process involved in building your prototype must involve constant diverging and converging. Your team meets to discuss the next steps, then separate to execute their tasks and meet up again to review learnings, progress, and potential adoptions. You must understand the problem, the target audience, and if your product provides a solution your target audience tries to solve. These factors explain the significance of this phase in your product discovery life cycle. It helps to bridge the gap between having a concept and realizing it. The data on this is unambiguous, and the pattern is visible in every major study of software project failure.
You can also scroll down for a summary table that you can use for quick reference. Translate technical functionality into messaging that resonates with your audience. Rollout requires coordinated delivery efforts across the organization. Each group has its own methods and tools, yet all of this work must stay aligned with the original plan. In my mind, it feels like the “problem” would just be a re-wording of the “opportunity.” Initial Product Discovery comes into play when creating a new product.
Product Discovery Tools
It’s ok to temporarily focus more on Delivery or Discovery at a given point in time. But make sure that a Product Team has the skills and freedom to work on both aspects on their own time. At its core, Product Discovery is the evidence-informed process of reducing uncertainty as you find problems worth solving and solutions worth building. It emerges through a series of nonlinear activities, conducted as a cross-functional team.
Teams don’t need a universal catalog of how much each signal is worth, but a shared understanding of what they value, ie. Just like Research, testing assumptions is not simply about ticking off boxes of showing a design prototype to customers or priding yourself on how many A/B tests are running on production. Instead, prioritizing assumptions and running experiments is about making sure that you collect the best information possible to evaluate a given solution based on actionable evidence. Putting sticky notes full of ideas into the hands of your users probably won’t help you to understand their reactions.
You need to stay organized and have the flexibility to make changes both while planning the project ahead and during the consequent development phases. Therefore, it is wise to use one of the software development models like Waterfall, Lean development, or Agile frameworks, including Scrum, Kanban, and Feature-Driven Development. Therefore, you must select and pinpoint only that minimal set of features that’ll meet user needs and help the product stand out. At least, that’s what makes the most sense at the very start, as you can test your hypotheses and make changes to the features or add more of them after the MVP is released. What happens when you rush things or choose the rough-and-ready manner?
As an industry, they have to come to terms with this element of uncertainty (and this risk is priced into their products). Your company gets all excited about a product idea, and as product manager you are asked to define it. You are told that the engineers will be finished with their current project in 4 weeks, so that means take all the time you need, as long as you are ready in 4 weeks. Learn the principles and strategies that go into effective Product Discovery processes. And more importantly, discover how to use the Adaptable Product Discovery approach to make the processes work for your company and reality—right away and step by step.
The Importance Of The Product Discovery Process In Building Successful Products
Yet many teams learn they’ve made a false assumption about what users really need once their new feature goes live – only to go underutilized. And any business that operates in such a way won’t be around for long. You may need to take some steps back during your validation stage or after it. Whether you are only picking newer ideas from your ideation stage to test, or you are returning to the initial phase of research, going back can be painful. Still, it makes more sense than going forward without anything tangible.
The project discovery phase allows for mitigating many risks connected with the further development process and product launch. Vueling’s e-commerce team implemented a product discovery process to bridge the gap between business operations and technology teams. The process helped the Spanish low-cost airline identify market needs and rapidly adapt products, leading to increased agility and business growth. Product discovery is an ongoing and iterative process that continues throughout the product development lifecycle. Through product discovery, the team can be confident that the product aligns with user needs, market demand, and organizational objectives. Product discovery focuses on understanding and addressing user needs.
Product discovery describes the upfront research and development process that retailers partake in when they’re launching a new product. Continuous product discovery is an iterative process that spans the entire product life cycle. Product discovery is the process of researching user behavior and analyzing the market to assess the viability of products. The practice revolves around the idea that customer needs should inspire your product vision. Product discovery encourages teams to solve user problems by exploring innovative solutions. This can lead them to develop creative, unique, and competitive products.
- A Product Discovery Coach helps teams structure research, validate ideas, and align with business priorities.
- But it makes sense to involve more than one person in the project discovery phase so that you get diverse opinions from multiple professionals and various perspectives.
- The theory advocates for answering key questions about value, usability, feasibility, and strategic alignment to ensure the right product is built for the right customer.
- Making OKRs a truly useful practice for Product Teams that goes beyond pretty, but generic KPIs and task-lists requires going beyond the common “by-the-book” advice.
Again, of course it’s important to continuously seek interactions with your customers. But blindly following a given cadence also won’t guarantee “success” in Product Discovery and doesn’t always give you the insights you need in order to make progress. For example, when you’re exposed to the problems of one user per week, it can be tempting to jump on what you have just heard immediately. But just because a user problem exists does not mean that you need to solve it. 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. The idea of talking to one user every week is a great catchy prompt for companies that want or need to shift their overall attitude toward their customers.
Product discovery lets you validate how viable your product is early in the process. You can avoid investing too much time, effort, and resources into a product that ultimately won’t sell. A diverse product discovery team can aid this continuous improvement by ensuring cross-functional collaboration and evolving participation to enhance insights, alignment, and decision-making.
Mentioning what comes after the discovery phase in a project, in most cases, the teams proceed with development tasks. The developers start coding and piecing together the solution based on the provided designs, test the solution, fix any bugs, and release it. Giving a basic discovery process definition for tech projects, it is an early stage of product development that deals with preparation, research, and detailed planning. Creating a full design of the product is a step that isn’t always included as part of the discovery phase of a software project. It implies modeling the entire look of the project in terms of UX/UI, based on which the developers will then create code. At times, this stage of the discovery phase may also include surveying potential customers or holding interviews with them regarding their product expectations.
In general, Product Teams are always in some Product Discovery mode. This is because if you’re set up as a truly customer-centric organization, you want to expose as many team members as possible to user feedback as often as possible. That will ultimately lead continuously to new insights in the user’s needs. To clearly define problems, many product teams employ journey mapping, dive into the Five Whys or other similar techniques, or conduct a SWOT analysis. There is always uncertainty when it comes to making product decisions.
This phase is crucial for aligning the team’s vision with user expectations and market realities. Product discovery is the process of researching to understand your users’ problems and needs, then validating your solutions before beginning development. By working closely with real users in this stage, your final product is more likely to solve user challenges.
Ask These Questions Before You Start The Continuous Product Discovery Process
Product discovery is all about identifying the right problems to solve and validating ideas before building. Product delivery is the process of executing those ideas – developing, launching, and maintaining the solution. To get the most value from your product discovery process, understanding the common pitfalls to avoid is key. The main objective is to gather insights that will inform the product development process. This phase is all about exploration and validation, ensuring the team is on the right track before moving forward. Before building the right product, you need to understand the problem you’re solving and for whom.
A discovery is needed anytime there are many unknowns that stop a team from moving forward. Moving forward on only assumptions can be risky, as the team may end up solving a problem that doesn’t really matter — wasting time, money, and effort. Well-done discoveries ensure that any solutions proposed later are desirable to users, viable for the organization, and feasible with the available technology. Giving a rough estimate, a quality discovery process can be carried out within two business weeks. However, Derribar Ventures Limited resources this depends on each individual case and on who handles discovery.
Initially, the client assumed that the integration of these features would be enough to achieve the desired goal. Design Thinking encourages organizations to make user-centric products by finding data about users’ needs and producing creative ideas to solve them. You need to make direct contact with the end-users, validate the ideas, and even help in prototyping to discover a useful product.
If the issue is extreme, you may need to go right back to the Empathize stage. Or, if it’s a minor issue and you’re able to define it precisely, you can go back to the Ideate stage instead. On the other hand, if your idea fails in the validation test, you may have to take steps back to the research phase to find what went wrong. Prepare the first organized version of the collected information and start sketching the ideas.
We also audit the competitive landscape, not to copy it, but to understand the baseline user expectations that your product will be measured against. We look at what existing tools get right, where they fall short, and where there is genuine opportunity to differentiate. Usually, it takes from 11 to 21 working days to complete the discovery stage.
Returning to the online mortgage application example, the mortgage application process (which is a customer journey) is a core factor in product success and the conversion level. It’s important to analyze why users don’t complete the journey of your product and exactly what is blocking them – whether it’s an inadequate UX/UI or the reluctance of these users to buy. The Jobs-to-be-Done framework focuses on understanding the underlying motivations and goals that drive customers to use a product or seek a solution.
Product managers are responsible for coordinating the releases and launches that bring a new product experience to market once it is ready. Regardless of your release cadence, you need to consider all of the cross-functional activities needed to support the release — from marketing and promotions to customer support. One of the best ways to ensure this product knowledge is accessible and updated is to publish wikis within a knowledge base site. Roadmaps serve as a communication tool for internal and external groups. And getting buy-in and anchoring the team around a shared vision requires everyone to know their role in the product’s success. Keep in mind that your product roadmap is different from your release plans (they detail phases of work, release dates, and dependencies).
The time you spend on each stage might vary depending on your exact methodology or overall product strategy, but not the stages themselves. During the discovery phase, you build a foundation for your product, which will impact its future success. The product discovery process helps validate your product vision and make informed decisions before you invest time, money, and resources in product design and development. When a project is launched, product discovery helps the product team to collaborate, create a shared understanding and define the product vision and discuss project goals. Therefore, it is essential to involve all stakeholders in the process and make all of their perspectives valuable when designing the product.
Ideally, the product discovery team will involve the customer in some form throughout the decision-making process. Or, as part of an agile approach, we can make it an iterative process of what we call continuous discovery. Or we can go through this with an existing product to improve it, and then we talk about product rediscovery. Although the stages are presented in order, the process is rarely linear.