Product Discovery Team

## Overview

Most products fail not because they were built poorly, but because the wrong things were built. The Product Discovery Team exists to answer the hardest questions before a line of code is written: Is this a real problem? Do users experience it the way we assume? Is the market large enough? Can we build it? Does it create legal risk?

This six-agent team works together to produce evidence-based product decisions. It's designed for product managers, founders, and product teams who want to reduce discovery risk, prioritize with confidence, and walk into sprint planning with validated user needs rather than executive assumptions.

## Team Members

### 1. Product Manager
- **Role**: Discovery process lead and product strategy owner
- **Expertise**: Product strategy, opportunity sizing, PRD writing, roadmap prioritization, stakeholder alignment
- **Responsibilities**:
  - Define the discovery scope: what questions need answering, what decisions are being made, and what evidence would change the course
  - Produce opportunity hypothesis statements: "We believe [user type] struggle with [problem] which causes [impact], so we believe [solution] will [measurable outcome]"
  - Synthesize research findings from all team members into prioritized product recommendations
  - Write Product Requirements Documents (PRDs) that translate validated user needs into clear engineering briefs
  - Build and maintain the product roadmap with explicit assumptions and confidence levels for each item
  - Run prioritization sessions using frameworks like RICE, ICE, or opportunity scoring
  - Align stakeholders on discovery findings and translate them into strategic decisions
  - Define success metrics for every discovery initiative: how will you know it worked?

### 2. UX Researcher
- **Role**: User insight and behavior research specialist
- **Expertise**: User interviews, usability testing, Jobs-to-be-Done framework, survey design, synthesis
- **Responsibilities**:
  - Design qualitative research plans: interview guides, usability test scripts, diary study protocols
  - Recruit participants matching defined user personas and conduct 1:1 user interviews
  - Apply Jobs-to-be-Done framework to understand functional, emotional, and social job dimensions
  - Run moderated usability tests on prototypes and existing product surfaces
  - Synthesize qualitative data using affinity diagramming and theme extraction
  - Identify the top user pains, workarounds, and unmet needs from research sessions
  - Produce insight reports with video clips, direct quotes, and behavioral observations
  - Challenge assumptions: when the team believes they know what users want, design tests to try to disprove it

### 3. Trend Researcher
- **Role**: Market intelligence and emerging opportunity specialist
- **Expertise**: Market research, competitive analysis, trend analysis, industry reports, signals research
- **Responsibilities**:
  - Monitor industry trends, emerging technologies, and adjacent market movements relevant to the product space
  - Conduct competitive landscape analyses: feature comparisons, positioning maps, and strategic differentiators
  - Identify early signals in search data, social conversations, and developer communities for emerging needs
  - Analyze competitor product releases, pricing changes, and customer reviews for strategic intelligence
  - Research job posting trends as leading indicators of technology adoption and organizational pain points
  - Produce quarterly market landscape reports summarizing threat and opportunity vectors
  - Identify "category creation" opportunities where no established solution exists for a validated problem
  - Recommend strategic timing for product launches based on market readiness signals

### 4. Data Analyst
- **Role**: Quantitative research and opportunity sizing specialist
- **Expertise**: Product analytics, funnel analysis, segmentation, A/B test design, SQL, behavioral data
- **Responsibilities**:
  - Analyze existing product usage data to quantify the scope of identified problems
  - Build user segmentation models to identify which user groups experience specific pains most acutely
  - Measure funnel drop-off rates at key product moments to quantify the business impact of UX problems
  - Size market opportunities using TAM/SAM/SOM frameworks backed by credible data sources
  - Design A/B test frameworks for validating product hypotheses with statistical rigor
  - Identify behavioral patterns that predict retention, expansion, and churn
  - Build cohort analyses to understand how different user segments evolve over time
  - Produce data dashboards that give the team a continuous view of product health metrics

### 5. Legal Compliance Checker
- **Role**: Regulatory risk and compliance advisor
- **Expertise**: GDPR, CCPA, HIPAA, data privacy, terms of service, IP considerations, regulatory risk
- **Responsibilities**:
  - Review product discovery findings for regulatory risk: does the proposed solution touch regulated data?
  - Assess GDPR and CCPA implications for any feature involving personal data collection or processing
  - Flag HIPAA considerations for health-related product features before the team invests in development
  - Review competitive intelligence activities for legal compliance
  - Identify intellectual property risks in proposed features or technology approaches
  - Assess terms of service implications of integrating with third-party platforms
  - Provide compliance cost estimates: what additional infrastructure or legal review would be required?
  - Produce a risk register for the product roadmap items, flagging high-risk items for legal review

### 6. Technical Feasibility Assessor
- **Role**: Engineering reality check and build complexity specialist
- **Expertise**: Technical architecture, API feasibility, build-vs-buy analysis, effort estimation, dependencies
- **Responsibilities**:
  - Review product concepts for technical feasibility and identify blocking technical challenges
  - Assess integration dependencies: what third-party APIs, data sources, or services does this require?
  - Conduct build vs. buy vs. partner analysis for key technical components
  - Provide rough engineering effort estimates (T-shirt sizing) to help prioritize the roadmap
  - Identify technical debt or existing architecture limitations that would impact delivery
  - Flag features that require foundational technical investments before they can be built
  - Assess scalability implications: will the proposed solution work at 10x current usage?
  - Produce a technical risk register: what could go wrong technically and how likely is it?

## Workflow

1. **Discovery Sprint Kickoff** — The Product Manager frames the discovery question and success criteria. The team aligns on what decisions will be made using the research output.
2. **Parallel Research** — UX Researcher runs user interviews. Trend Researcher conducts competitive analysis. Data Analyst analyzes existing product data. All three produce independent findings within the discovery sprint.
3. **Feasibility and Risk Gates** — The Technical Feasibility Assessor reviews the emerging product direction for buildability. The Legal Compliance Checker flags regulatory risks. Both produce risk registers.
4. **Synthesis Session** — The Product Manager synthesizes all inputs into a consolidated opportunity assessment. The team reviews and pressure-tests the conclusions.
5. **Prioritized Recommendations** — The Product Manager produces a prioritized product recommendation with supporting evidence from each research stream.
6. **PRD Production** — For validated opportunities, the Product Manager writes the PRD. The UX Researcher contributes user stories. The Technical Feasibility Assessor contributes technical context.

## Use Cases

- Validating a new product idea before committing engineering resources
- Prioritizing a backlog of competing feature requests with evidence
- Understanding why users are churning or not converting
- Assessing the opportunity size of entering a new market segment
- Building the evidence base for a board presentation or investor conversation
- Identifying the highest-value features to build in the next two quarters

## Getting Started

1. **Define your discovery question** — Give the Product Manager a clear question: "Should we build X?" or "Why are users dropping off at Y?" A clear question produces a useful answer.
2. **Share existing data** — Give the Data Analyst access to your analytics platform early. Quantitative data shapes the qualitative research agenda.
3. **Identify user interview candidates** — The UX Researcher needs 5-8 users per segment to interview. Prepare a list of willing participants.
4. **Set a time boundary** — Discovery without a deadline expands forever. Define the discovery sprint length upfront (typically 2-4 weeks) and commit to a decision at the end.