Product Discovery Weekly Sync Template

The core product trio: PM, designer, and tech lead. Adding a user researcher is valuable if your team has one. Keep the group small (3-5 people) so the conversation stays focused. Stakeholders like Sales or Customer Success should not attend the weekly sync, but you should share a monthly summary of key findings with them. Use the [customer interview template](/templates/customer-interview-template) to structure the research that feeds into this meeting.

Sprint planning decides *what to build this sprint*. Discovery weekly decides *what to learn this week*. They are complementary rituals. Discovery feeds the backlog with validated opportunities. Sprint planning pulls from that backlog. Teams that only do sprint planning without discovery end up building features nobody asked for. Teams that only do discovery without shipping never validate their ideas in production.

That is a signal, not a problem. If the team has nothing new to share, the meeting should be short. Use the remaining time to plan research activities: schedule customer interviews, set up analytics dashboards, or design a prototype test. The goal is continuous learning, not filling a time slot. Over time, the rhythm creates accountability and discovery work becomes consistent. The [Product Analytics Handbook](/analytics-guide) can help you build the data infrastructure for ongoing insights.

Use the opportunity assessment table in the template. Score each opportunity on problem clarity (do we understand the problem well?), evidence strength (how many data points support it?), and feasibility (can we build a solution?). Focus on opportunities with high problem clarity and strong evidence first. Low-clarity, low-evidence ideas need more research before they deserve a spot on the roadmap. For quantitative scoring, the [RICE Calculator](/tools/rice-calculator) provides a structured scoring method.

Yes. A monthly discovery digest shared with stakeholders, leadership, and adjacent teams builds organizational confidence in your product decisions. Keep it concise: 3-5 key findings, what you learned, and what it means for the roadmap. This transparency reduces the "why are we building this?" questions that slow teams down. The [stakeholder update template](/templates/board-product-update-template) provides a format for sharing these insights at the leadership level. ---