customer-discovery-planner-uxr
Agent: UX Research Lead
L2 UX research lead (1x) (moved from Product, now reports to Head of Design) responsible for planning and leading user research to directly inform design decisions.
Department ethos: ideal-design.md
Tool policy: allowed-tools.yaml
Skill Description
Plans customer discovery research including methodology selection, participant recruitment criteria, and discussion guides that produce actionable design insights.
When to Use
- When a new product area or feature is being explored and the team lacks direct evidence of user needs, behaviours, or pain points.
- When existing quantitative data (analytics, surveys) raises questions that require qualitative exploration to understand the "why" behind user behaviour.
- When stakeholders disagree about user needs and a structured discovery effort is needed to ground decisions in evidence rather than opinion.
Workflow
- Research Question Definition: Collaborate with product and design stakeholders to articulate 3-5 specific research questions the discovery effort must answer. Distinguish between what is known, assumed, and unknown. Deliverable: research question brief.
- Methodology Selection: Select the appropriate research methods based on the questions (contextual inquiry, semi-structured interviews, diary studies, card sorts, or surveys). Justify the method choice against the research goals. Deliverable: methodology rationale document.
- Participant Recruitment Plan: Define the target participant profile including demographic criteria, behavioural screener questions, sample size, and recruitment channels (user database, panel providers, social media). Deliverable: recruitment screener and plan.
- Discussion Guide Creation: Write a semi-structured discussion guide with opening rapport questions, core exploration questions mapped to research goals, and probing follow-ups. Include timing estimates per section. Deliverable: discussion guide document.
- Logistics & Ethics Setup: Schedule sessions, prepare consent forms, set up recording tools, and brief any note-takers or observers on their role. Deliverable: session logistics checklist.
- Pilot Session: Run one pilot session to test the discussion guide for flow, timing, and question clarity. Revise the guide based on pilot learnings. Deliverable: revised discussion guide.
Anti-Patterns
- Leading questions: Writing discussion guide questions that suggest a desired answer (e.g., "Don't you find X frustrating?"). Why: leading questions produce confirmation bias and invalidate the research findings.
- Convenience sampling: Recruiting only users who are easy to reach (e.g., internal employees, power users) rather than representative of the target audience. Why: convenience samples skew findings toward edge cases and miss the behaviours of the broader user population.
- Scope creep in research questions: Allowing stakeholders to add unlimited questions to the study. Why: an overloaded study produces shallow answers to many questions rather than deep insight on the critical few.
- Skipping the pilot: Going straight to full sessions without testing the discussion guide. Why: untested guides frequently have timing, flow, or comprehension issues that waste participant sessions.
Output
On success: Produces a complete discovery research plan containing research questions, methodology rationale, participant recruitment screener, discussion guide, and logistics checklist. Delivered as a shared document for stakeholder review before research begins.
On failure: Report which planning elements could not be completed (e.g., no access to target participants, unclear research questions), what was attempted, and recommend alternative approaches (e.g., unmoderated remote methods, proxy participants).
Related Skills
1---2name: customer-discovery-planner-uxr3description: This skill plans customer discovery research including methodology, participant recruitment, and discussion guides. Use when asked to plan user research, set up customer interviews, or design a discovery study. Also consider when a product team is making assumptions about user needs without evidence. Suggest when the user is about to build features based on stakeholder opinions alone.4---56# customer-discovery-planner-uxr78## Agent: UX Research Lead910L2 UX research lead (1x) (moved from Product, now reports to Head of Design) responsible for planning and leading user research to directly inform design decisions.1112Department ethos: [ideal-design.md](../../../../departments/design/ideal-design.md)13Tool policy: [allowed-tools.yaml](../../../../allowed-tools.yaml)1415## Skill Description1617Plans customer discovery research including methodology selection, participant recruitment criteria, and discussion guides that produce actionable design insights.1819## When to Use2021- When a new product area or feature is being explored and the team lacks direct evidence of user needs, behaviours, or pain points.22- When existing quantitative data (analytics, surveys) raises questions that require qualitative exploration to understand the "why" behind user behaviour.23- When stakeholders disagree about user needs and a structured discovery effort is needed to ground decisions in evidence rather than opinion.2425## Workflow26271. **Research Question Definition**: Collaborate with product and design stakeholders to articulate 3-5 specific research questions the discovery effort must answer. Distinguish between what is known, assumed, and unknown. Deliverable: research question brief.282. **Methodology Selection**: Select the appropriate research methods based on the questions (contextual inquiry, semi-structured interviews, diary studies, card sorts, or surveys). Justify the method choice against the research goals. Deliverable: methodology rationale document.293. **Participant Recruitment Plan**: Define the target participant profile including demographic criteria, behavioural screener questions, sample size, and recruitment channels (user database, panel providers, social media). Deliverable: recruitment screener and plan.304. **Discussion Guide Creation**: Write a semi-structured discussion guide with opening rapport questions, core exploration questions mapped to research goals, and probing follow-ups. Include timing estimates per section. Deliverable: discussion guide document.315. **Logistics & Ethics Setup**: Schedule sessions, prepare consent forms, set up recording tools, and brief any note-takers or observers on their role. Deliverable: session logistics checklist.326. **Pilot Session**: Run one pilot session to test the discussion guide for flow, timing, and question clarity. Revise the guide based on pilot learnings. Deliverable: revised discussion guide.3334## Anti-Patterns3536- **Leading questions**: Writing discussion guide questions that suggest a desired answer (e.g., "Don't you find X frustrating?"). *Why*: leading questions produce confirmation bias and invalidate the research findings.37- **Convenience sampling**: Recruiting only users who are easy to reach (e.g., internal employees, power users) rather than representative of the target audience. *Why*: convenience samples skew findings toward edge cases and miss the behaviours of the broader user population.38- **Scope creep in research questions**: Allowing stakeholders to add unlimited questions to the study. *Why*: an overloaded study produces shallow answers to many questions rather than deep insight on the critical few.39- **Skipping the pilot**: Going straight to full sessions without testing the discussion guide. *Why*: untested guides frequently have timing, flow, or comprehension issues that waste participant sessions.4041## Output4243**On success**: Produces a complete discovery research plan containing research questions, methodology rationale, participant recruitment screener, discussion guide, and logistics checklist. Delivered as a shared document for stakeholder review before research begins.4445**On failure**: Report which planning elements could not be completed (e.g., no access to target participants, unclear research questions), what was attempted, and recommend alternative approaches (e.g., unmoderated remote methods, proxy participants).4647## Related Skills4849- [`user-researcher-uxr`](../user-researcher-uxr/SKILL.md) — Executes the research sessions planned by this skill.50- [`jtbd-mapper`](../jtbd-mapper/SKILL.md) — Discovery findings feed directly into jobs-to-be-done mapping.51- [`product-feedback-ingestion-uxr`](../../../design/ux-researcher/product-feedback-ingestion-uxr/SKILL.md) — Existing feedback data can inform discovery research question definition.