The user-centric nature of Product Discovery
At its core, Product Discovery is a strategic and iterative process aimed at uncovering user needs and translating them into successful SaaS solutions. It's not a one-time event, but rather a continuous cycle of exploration, learning, and refinement. Despite its age, the Double Diamond framework still provides a helpful model to understand this iterative nature:
Source: www.designcouncil.org.uk
Discover: This initial phase involves gathering insights through various methods like user research, competitor analysis, and market trend analysis. The goal is to understand the target audience's pain points, behaviors, and expectations.
Define: Based on the insights gathered, the Product Team works to define the core problem(s) your product will address and the target user personas.
Develop: This stage focuses on creating potential solutions through brainstorming, prototyping, and user testing. Here, Minimum Viable Products (MVPs) can be particularly valuable in validating ideas and gathering early user feedback.
Deliver: Once a solution is deemed viable, it's time to deliver it to the market and monitor its performance. Data analysis and user feedback during this stage inform further iterations within the discovery process.
This cyclical nature highlights the importance of ongoing user research and testing throughout the product development lifecycle. By continuously gathering feedback and iterating based on user needs, you ensure your SaaS product remains relevant and valuable to its users.
Recognizing true Product Discovery
Product Discovery has become a buzzy term in product development. However, simply going through the checklist doesn't guarantee success. Many companies fall prey to mistaking individual activities like user research for true product discovery, leading to wasted time and resources.
Here are some key indicators that your Product Discovery efforts are on the right track:
User-centric focus: The process revolves around understanding and addressing user needs, not internal agendas or top-down crafted feature roadmaps.
Data-driven decision-making: User research, competitor analysis, and techniques like A/B testing constantly provide data to inform product decisions.
Iterative approach: The discovery process is ongoing, with continuous learning and refinement based on user feedback. Simply put, a continuous repetition of the stages of the Double Diamond model.
Make sure you’re aware of the following, indicating that your Product Discovery practice risks failing:
Internal bias: Relying solely on internal assumptions - often advocated by people in powerful positions, like founders and CEOs - about user needs is a recipe for disaster. These assumptions may not reflect the actual reality of your target audience. True Product Discovery requires validating these assumptions through qualitative and quantitative user research techniques like interviews and surveys.
Neglecting feedback: Gathering user feedback is crucial, but it is only valuable if it is acted upon. Failing to integrate user insights into the development process makes product discovery utterly ineffective.
Feature factory: Getting caught up in building features without a clear understanding of the underlying user problems is a common misstep. True Product Discovery prioritizes solving user problems over simply adding feature after feature.
Product Discovery is a Team Sport
For product managers, it can be tempting to go it alone in the discovery phase. This might explain why product management traditionally led the process: a Product Manager explored, defined, and drafted a set of requirements, based on which a designer created a mockup. The engineer coded the solution, realizing only halfway that there was a feasibility issue resulting in the rewriting of requirements and reworking of design and code. Handing off work from one to another with only limited sharing of knowledge about the actual need, more than often leads to projects being delivered over budget, under scope, and late.
