What insights/ data should I gather to share with the Product team when we meet to do quarterly roadmap planning?

It's hard to give a very specific answer without more context on the company. I’d first observe the types of perspectives are often represented in roadmap mapping conversations. For example: is your company often relying on recent lost deals to drive the roadmap, it’s likely too myopic in the way it’s thinking about the roadmap. At the same time, if your product team is only looking at larger industry trends, there isn’t enough concreteness in the insights that corresponds to why your company sh ...Read More

The best information to be shared with the product team is a combination of customer feedback, win/loss analysis, competitive information, and market dynamics. By sharing customer feedback, you can help the product team put things in perspective as to why customers need a certain feature or what is the job they are trying to get done. Win/loss analysis is a great way to show the product team why we win and why we lose certain deals, and what specific product features may help us in those situati ...Read More

Never go into roadmap planning empty handed! Great product development takes time and these planning cycles set teams off to work. Whether it’s a 2-week sprint or a 2 quarter cycle, you want to make sure that work is directed in the most valuable direction for the business and your customers. And that it gives you what you need to deliver a compelling story to customers. Product teams may use different frameworks such as RICE scoring, Kano modeling, there are many others. So, be ready with relev ...Read More

When meeting with the product team to plan out the roadmap, it's important to come prepared with data to back up your requests. Often times, customer feedback data is well-received but if you are working on more blue sky features where you want to lead from the front then you'll also need to look beyond your existing customers. In my experience some of the best insights come from the following sources: Customer feedback like enhancement requests, product issues, customer satisfaction surveys, NP ...Read More

First, don’t just come with data — come with a point of view built on that data. Product teams don’t need a report; they need perspective. Show up ready to answer “What’s changing in the market, what does it mean for us, and where should we focus next?” The most relevant data will vary by business model and what you have access to, but the goal is always the same: to help Product make more confident prioritization and trade-off decisions. Below are the most valuable categories of insight for PMM ...Read More

I pull from all your usual sources—sales calls, customer feedback, competitive intel, market research—but the key is synthesizing it into a clear story, not just dumping data. Win/loss data: What features are making us win or lose deals? Are there patterns in what prospects keep asking for? Customer conversations: What are your best customers struggling with? What workarounds are they building because the product doesn't do something? Competitive intel: What are competitors launching? Where are ...Read More