How do you determine how much of your roadmap should be focused on existing customers vs prospects?
16 Answers
Boxford Capital Managing Partner | Formerly Barracuda, SilverSky, Digital Guardian, OpenPages, Cybertrust • 2y
This question is impossible to answer in the abstract. It depends entirely on where you are in the technology adoption lifecycle. If you haven't read "Crossing the Chasm"...
2287 Views
Splunk Director, Product Management • 3y
Great question! This is something most product teams wrestle with when only looking at the roadmap from a features perspective to balance what to build for existing vs pr...
4223 Views
Cortex VP of Product | Formerly Splunk, Deloitte • 3y
In a perfect world, you want at least 80% of your roadmap to be applicable to both! But, we don't live in a perfect world, do we? Some startups focus on a small number ...
657 Views
IBM Product Management • 4y
I typically start from what are the annual business targets set by the company to answer this question. Oftentimes, the sales organization, CEO, and professional services...
726 Views
Notable Head of Product • 2y
When prioritizing your roadmap, focus on the initiatives that will have the biggest impact on your strategy and goals.If you have a retention problem, focus on improving ...
2539 Views
Airbase VP Product | Formerly Skype, Microsoft, Blink and Pipedrive • 4y
The answer lies in the breakdown of how the organisation intends to hit it's goals. See this answer for context - https://sharebird.com/h/product-management/q/how-do-you-...
1212 Views
Splunk Director of Product Management • 3y
Who to focus on often depends on the maturity of the product. At the beginning stages of the product, we focus heavily on prospective users. When the product is mature, w...
704 Views
Green Dot Principal Product Manager | Formerly Narvar, Stamps, Accenture • 3y
In general, a product roadmap should be shaped by product strategy, vision, and goals rather than prioritizing initiatives or features based on whether they benefit exist...
791 Views
Typeform Chief Product Officer • 3y
I find that this type of division can be misleading. In many industries, there is little difference between what an existing customer would want vs what a prospect would ...
595 Views
Asana Former Head of Product Operations | Formerly Adobe • 1y
It depends on your company’s stage, but a healthy roadmap usually balances both existing customers and prospects. Earlier-stage companies should prioritize features that ...
830 Views
Meta Senior Director of Product Management • 2y
I think it depends on whether the product has a market fit or not. If it's pre market fit, then we'd want to lean towards prospects to ideally find a core group of sticky...
2273 Views
HubSpot Group Product Manager • 2y
Most roadmaps indeed focus on both. The balance of prioritizing prospects versus existing customers will depend on the business objectives your product roadmap is designe...
811 Views
BILL Director, Product Management (Data, AI, DevEx, Identity) | Formerly Twitter/X • 1y
This is a difficult question and generally depends on the guidance which comes from upper management and business. If the company is focussed heavily on growth, and your ...
443 Views
Square Product Lead, Payments • 2y
This is an interesting question, but it's rarely a decision an individual product manager makes. Even if you're the only PM in your company, there will be PMMs, business ...
2596 Views
strongDM Sr. Director, Product Management • 2y
The short answer is it depends. There is no magic formula that you can apply to determine what percentage of your roadmap you should dedicate to existing customer needs v...
395 Views
Chainguard Senior Director of Product Management • 1y
To answer this properly, it's critical to know what your product or product line's goals are. What is the lifecycle phase of the product? Is it in its initial growth ramp...
525 Views
Related Questions
How do you get autonomy for prioritizing your roadmap when your sales process is very sales heavy, and sales leadership wants to dictate priorities?What are some of the lenses your look through or principles you apply when prioritizing a roadmap? How are they weighted relative to each other? Which stakeholders have input into your roadmap, and how to balance giving them influence vs control?Who are all the stakeholders that can provide input to a product roadmap? What are the stage gates to help decide if something should land in the roadmap?How do you handle exec input in the roadmap, and convey a point of view while also accommodating?