Product Discovery & Validation

Design a complete product discovery and validation process for a new SaaS feature or product:

Feature/Product Concept: [DESCRIBE THE IDEA]
Target User: [PRIMARY USER PERSONA]
Problem Hypothesis: [THE PROBLEM YOU BELIEVE EXISTS]
Current Solution: [HOW USERS SOLVE THIS TODAY]
Business Objective: [WHAT BUSINESS OUTCOME THIS SERVES]
Timeline for Discovery: [WEEKS AVAILABLE]
Discovery Team: [WHO IS INVOLVED]
Budget for Research: [AVAILABLE BUDGET]

Develop the discovery process across these six sections:

Section 1 - Problem Space Research and Framing:
Conduct thorough research to validate that the problem exists, matters enough to solve, and represents a viable business opportunity. Design a customer interview study with a minimum of fifteen interviews targeting users who fit the persona, using open-ended questions that explore their current workflow, pain points, and attempted solutions without leading them toward your hypothesis. Create the interview guide with specific questions that probe the frequency and severity of the problem, the emotional frustration it causes, the time and money currently wasted on workarounds, and what an ideal solution would look like from their perspective. Build a secondary research plan that examines market reports, competitor analysis, online community discussions, support ticket analysis, and sales conversation mining to triangulate customer interview findings with broader market data. Create a problem statement canvas that synthesizes research findings into a clear, specific problem statement including who experiences the problem, what the problem is, when and where it occurs, why it matters, and how big the affected audience is. Establish the go or no-go criteria for the problem validation phase specifying the evidence threshold required to confirm the problem is worth solving, including minimum interview count confirming the pain, estimated market size, and alignment with business strategy.

Section 2 - Opportunity Assessment and Sizing:
Quantify the opportunity to ensure the validated problem represents a worthwhile investment. Calculate the total addressable market by estimating the number of potential users who experience this problem and their willingness to pay for a solution. Assess the serviceable addressable market by filtering for users reachable through your existing channels, compatible with your product, and within your target segments. Estimate the revenue potential using conservative, moderate, and optimistic scenarios for market penetration within the first twelve months. Evaluate the competitive landscape to understand how many solutions already exist, where they fall short, and what differentiation opportunity remains. Conduct a strategic fit assessment evaluating how this opportunity aligns with the product vision, leverages existing technology and distribution, and contributes to competitive moats. Create a cost-benefit analysis comparing the estimated development investment against the projected revenue, retention improvement, or strategic value. Build a risk assessment identifying the key uncertainties that could undermine the opportunity including technology feasibility, market timing, competitive response, and adoption barriers. Define the investment threshold criteria that determine whether the opportunity warrants proceeding to solution design based on the market size, strategic alignment, and risk profile.

Section 3 - Solution Ideation and Concept Development:
Generate and evaluate multiple solution approaches before converging on a design direction. Facilitate a structured ideation process using design thinking methods including How Might We framing, crazy eights sketching, and dot voting to generate a breadth of solution concepts from the team. Create evaluation criteria for comparing solution concepts including how well each addresses the validated problem, technical feasibility within the team's capabilities, time to deliver a minimum viable version, scalability to serve the full target market, and alignment with existing product architecture. Select two to three promising concepts for further development and create concept descriptions that articulate the user experience, key capabilities, and differentiation for each. Build lightweight prototypes for each concept ranging from paper sketches to clickable wireframes depending on the fidelity needed to gather meaningful feedback. Design a concept testing plan that puts prototypes in front of target users and evaluates their reaction, collecting data on comprehension, perceived value, preference between alternatives, and willingness to pay. Create a solution hypothesis document that captures the chosen direction along with the assumptions that must hold true for the solution to succeed, forming the basis for the validation phase.

Section 4 - Prototype Development and User Testing:
Build and test prototypes of increasing fidelity to validate the solution approach before committing full engineering resources. Define the prototyping strategy progressing from low-fidelity wireframes that test information architecture and workflow logic, through mid-fidelity interactive prototypes that test interaction patterns and feature comprehension, to high-fidelity prototypes that test visual design and emotional response. Create a usability testing plan specifying the number of participants per round, the recruitment criteria, the test tasks, the observation methodology, and the success metrics. Design the test script for moderated usability sessions including the introduction, warm-up questions, task scenarios, probing questions, and post-test debrief. Build a usability findings synthesis framework that categorizes issues by severity, frequency, and impact to prioritize design iterations. Establish the iteration cadence for the prototype phase where findings from each round of testing inform design changes that are validated in the next round. Create a Wizard of Oz or concierge MVP approach for testing complex functionality that would be expensive to build, simulating the product experience through manual behind-the-scenes effort. Define the prototype validation criteria that must be met before advancing to engineering including minimum task completion rate, System Usability Scale score, and qualitative confidence from users.

Section 5 - Demand Validation and Business Model Testing:
Test whether validated user interest translates into actual market demand and viable business model assumptions. Design a landing page test that describes the proposed solution and measures interest through email signups, waitlist registrations, or letter of intent submissions. Create a painted door test within the existing product that presents the new capability as if it exists and measures how many users attempt to access it. Build a pre-sale or beta commitment campaign for B2B products that asks target customers to commit to a paid pilot, testing whether the perceived value translates into actual purchase behavior. Design a pricing validation experiment using methods such as the Van Westendorp price sensitivity meter, conjoint analysis, or direct willingness to pay questions embedded in the prototype testing sessions. Create a channel validation test that evaluates whether the target users can be efficiently reached through existing distribution channels or whether new acquisition approaches are needed. Build a unit economics model using the validated demand, pricing, and acquisition cost data to project whether the opportunity will generate positive ROI within an acceptable timeframe. Define the demand validation go or no-go criteria including minimum conversion rates, willingness to pay thresholds, and unit economics benchmarks that justify proceeding to full development.

Section 6 - Discovery Documentation and Handoff:
Create the comprehensive documentation that transfers discovery learning to the teams responsible for building, marketing, and selling the validated product. Build a discovery summary document that concisely captures the problem statement, opportunity sizing, solution direction, validation evidence, and key risks for executive review and approval. Create the product brief that translates discovery findings into development-ready specifications including the target persona, jobs to be done, functional requirements, design direction, and success metrics. Design a stakeholder presentation that tells the story of the discovery process from initial hypothesis through evidence gathering to validated conclusion, building organizational confidence in the investment decision. Build an assumption tracker that documents every assumption made during discovery, its current validation status, and the plan for continued validation during development and launch. Create a risk register that identifies the remaining uncertainties and defines how each will be monitored during development with clear criteria for when to pause and reassess. Establish a continuous discovery process that extends beyond the initial research phase, embedding ongoing user research, data analysis, and assumption testing into the development sprints. Define the discovery retrospective process where the team evaluates the effectiveness of the discovery approach, identifies what worked and what should be improved, and updates the organizational discovery playbook for future initiatives.