Skip to main content
🔍0 Templates

Discovery & Research Templates

Free discovery and research templates for PMs. User feedback forms, customer interview scripts, A/B test plans, and persona templates.

Product discovery is about reducing risk before you commit engineering resources. These templates help you gather customer evidence, structure user interviews, plan experiments, and synthesize research findings into actionable insights.

Each template follows best practices from continuous discovery, jobs-to-be-done research, and experiment-driven development. You get a blank template for immediate use and a filled example showing what good looks like in practice.

For comprehensive discovery methodology, see the Product Discovery Handbook or try the NPS Calculator to benchmark your customer satisfaction.

Related Interactive Tools

NPS Calculator →A/B Test Calculator →Kano Model Analyzer →Read the Handbook →

Templates coming soon for this category.

Browse all templates →

Frequently Asked Questions

How many user interviews should I conduct?+
For most discovery research, 5 to 8 interviews per customer segment reveal the majority of patterns. If you are still hearing new themes after 8 interviews, expand your sample. Quality matters more than quantity: one deep 45-minute interview beats five shallow 10-minute chats.
What is the difference between user feedback and user research?+
User feedback is reactive. Customers tell you what they think about what exists. User research is proactive. You observe and ask questions to understand problems, motivations, and workflows before building anything. Both are valuable; templates exist for each.
When should I run an A/B test vs. a qualitative study?+
Run an A/B test when you have enough traffic to reach statistical significance (typically 1,000+ users per variant) and a clear metric to optimize. Use qualitative research when you need to understand why users behave a certain way, or when you are exploring a new problem space.
Do I need a user persona for every product?+
A persona is useful when your team does not have shared clarity about who the customer is. If your team already talks to customers weekly and can describe their top pain points from memory, a formal persona document adds less value. Start with one primary persona and add more only when you serve meaningfully different audiences.

Explore More Templates

Browse all discovery & research resources or explore other template categories.

Browse All TemplatesRoadmap Templates